Project Management Agile Software

Agile project management tools all show you the same screenshot: a board with columns, cards moving left to right, a burndown chart in the corner. The differences that matter show up three months in, when the team wants to change how work flows and finds out whether the tool bends or the team does.

We sell source code you clone and run yourself, so there is nothing here to sign up for and no hosted board product. Most teams searching for project management agile software should use Jira, Linear, or one of the free tiers below, and this page is more useful if it starts there rather than pretending otherwise.

What follows is what actually separates these tools, then the narrow case where teams end up building their own.

Agile is a set of practices, and the tool only touches some of them

Scrum and Kanban ask for different things from software, which is why a tool that feels right to one team feels obstructive to the next.

The practical question when comparing products is not which methodology they claim to support. It is what happens when you want both, because most teams end up somewhere in between: sprints for planning conversations with people outside the team, and continuous flow for the work itself.

What to check before you commit a team to one

Four things are worth testing during a trial, and none of them appear on a feature grid.

The free tiers are genuinely usable for small teams. Jira, Linear, GitHub Projects, and Trello all carry a team of a handful of people at no cost, and the seat maths only turns interesting somewhere north of twenty people. Those are other companies' products and their pricing is theirs to change, so check it rather than trusting a page like this one.

Why teams end up building anyway

Almost nobody should build a board. The teams that do usually are not building a board at all.

The second branch is a real and common shape. Agencies, consultancies, and software vendors all end up wanting a client-facing view of work in progress, and the tools in this category are built for internal teams rather than for being resold.

What you would start from here

There is no agile board in this stack, no sprints, no story points, and no burndown chart. What exists is one level below that.

The projects pack ships projects, tasks, and assignment, which is the data layer a board renders rather than the board itself. The starter gives you accounts, organizations, membership roles, and invitations, which is what "my client sees only their own delivery" is made of. Underneath is a Hono backend with Prisma and Kysely on Postgres, an admin app for support questions, and Stripe billing if you are selling the result rather than using it internally.

The parts you would write: sprint or iteration boundaries if you want Scrum, the estimate field and whatever you choose to measure, the drag-and-drop board itself on top of the task model, and the flow metrics. That last one is worth doing late, because the metric a team actually uses is rarely the one they said they wanted at the start.

If you are tracking your own team's work, close this and open a free tier. If you are building the client-facing version, the packs and screens below are the part that is not the board, which is most of it.