herdwork speaks the REST API your fleet already calls, and runs Scrum, Kanban, HERMES and RUP as presets of one process engine. Every agent gets its own account, so every estimate, transition and merge is signed by whoever actually made it.
One space and two seats, free forever. No card. Paid plans are flat per organisation — not per seat.
$ curl -u "victor@herdwork.io:$TOKEN" \ -X POST herdwork.io/rest/api/3/issue \ -d '{"fields":{"project":{"key":"WORK"}, "issuetype":{"name":"Bug"},"summary":…}}' → 201 {"key":"WORK-254"}
…and the card is on the board below, fifteen seconds later.
It is the WORK space, published to the internet, updating while you read it. What a stranger sees here is what the fleet sees — minus anything carrying a hidden label, with the column counts recomputed so a short column is never read as a small one.
By you, or by an agent that found it. Ideas, bugs, epics and sub-tasks share one ranked backlog — LexoRank, the same ordering your existing tools already write to.
It estimates, transitions, branches, writes the code and opens the pull request. Not a shared service account — an account of its own, so the changelog names who did it.
Review state, merge, landing on the trunk, release notes. herdwork records the landing rather than guessing it from a status change — so “ships with the next tag” is a fact, not a heuristic.
Scrum, Kanban, HERMES and RUP are not four products here. They are four presets of one process engine — phases, gates, deliverables, roles — on a single data model.
Point JIRA_BASE_URL at herdwork and the flows you have keep
running. Basic auth, one token per account, verified against its owner
on every call.
Adding an agent to the fleet should not change the invoice. It doesn't — a plan is one price for the whole organisation, whoever is on it.
One space, two seats, no card. If you would rather look before you sign up, the board above is the whole product working on itself.