← All articles
  • Zenhub
  • GitHub
  • Scrum

Zenhub alternatives: first decide where your issues should live

GitHub Projects, Linear, Shortcut, Jira and Scrumpy, sorted by how far each takes your plan from GitHub, with real prices for a 12-person team.

10 min readJeroen van Dijk
Zenhub alternatives: first decide where your issues should live

The usual moment is the third repository. Someone splits the API out of the monolith, Zenhub's free plan stops at two connected repositories, and a tool that has cost nothing for a year asks for a card. Zenhub Teams is $4.99 per user per month billed yearly, which is not much, so the honest question is rarely "can we afford it". It is "now that we are choosing anyway, is this still where we want the plan to live?"

That is the question this post is built around, because it sorts the alternatives better than any feature grid. Zenhub sits on top of GitHub issues. Every tool that could replace it makes a different choice about those issues: keep them, sync them, or leave them behind and link to the code instead. The short version: stay inside GitHub with GitHub Projects, sync with Linear, or move the plan into Shortcut or Jira and link it to your branches, or into Scrumpy and keep it beside your code. And for some teams, the right answer is to stay on Zenhub and pay the $4.99.

Where should your issues live after Zenhub?

Before comparing anything, look at who actually writes your issues.

If outside people file them, open source contributors or customers on a public repository, your GitHub issues are not just a backlog. They are a front door. Moving the plan somewhere else means keeping two lists, the public one and the real one, and someone has to carry things between them. That is the strongest argument for staying close to GitHub.

If your issues are written by your own team and nobody outside ever looks at them, GitHub is mostly where they happen to be stored. The front door is the pull request, not the issue. You can move the plan without losing anything people outside the team rely on.

Plenty of small product teams are the second kind and assume they are the first. Check before you pick, because it decides which half of the list below you should be reading.

GitHub Projects: stay inside GitHub, give up the numbers

GitHub Projects is the obvious move, because you already have it. It is included on every GitHub plan, works directly on your issues, and has an iteration field for planning week by week, breaks included. Its Insights tab ships a default Burn up chart, and you can build historical charts that total a field such as an estimate over time. Nothing migrates, because nothing moves.

What you give up is the reporting Zenhub was sold on. There is no velocity trend across iterations, so nobody gets to say "we land about eighteen points a sprint" without building it by hand. We covered where GitHub Projects runs out for a scrum team in detail, and that gap has not closed.

The other cost lands on the people around the team. GitHub's own documentation is plain about it: only people with access to a private repository can view project items from it. So the product owner and the client who want to watch need repository access, which on GitHub Team is a $4 a month seat each.

Pick it if your team estimates loosely or not at all, and everyone who needs the board is already in the GitHub organization.

Linear: sync your GitHub issues instead of living in them

Linear is the only tool on this list that can keep GitHub issues and its own issues in step. Its GitHub Issues sync runs one way from several repositories into a team, or two ways for a single repository, and copies title, description, status, assignee, labels, sub-issues, comments and priority across. Two catches from their docs: only one repository per team can sync two ways at a time, and only issues created after you switch it on are synced, so the existing backlog goes through a separate import. Pull requests move linked issues to In Progress when they open and Done when they merge, by default.

For a team with one public repository and a lot of internal work, that is a genuinely neat answer to the front-door problem. Linear's free plan allows 2 teams and 250 issues, and Basic is $10 per user per month billed yearly. Guests only arrive on Business.

The catch is not technical. Linear runs cycles, not sprints, and unfinished work rolls into the next cycle unless you set it up otherwise. If what you liked about Zenhub was sprint reports and velocity, you are trading them for a different philosophy of work. We have a whole post on Linear alternatives for teams that want sprints, and a straight comparison of Scrumpy and Linear if you are weighing the two.

Shortcut: real sprints, branch automation, cheap watchers

Shortcut keeps its own stories and links them to GitHub through branches, commits and pull requests. Put the story ID in a branch name and the branch attaches itself; then you choose which workflow state a story moves to when a branch is pushed, a pull request opens or a branch merges. It plans in Iterations, which are sprints under another name.

The free plan covers 10 users and already includes Iterations and the GitHub integration. Team is listed at $8.50 per user per month. On paid plans Shortcut has an Observer role that is free, up to five observers per paid seat, which is the most generous watcher deal here apart from ours.

Of everything on this list, Shortcut is the closest to "Zenhub's sprints, without Zenhub's dependency on GitHub". If your team is under eleven people, look at it first. I mean that.

Jira vs Zenhub: when the heavier tool is the right move

Jira comes up in this search because some teams leave Zenhub for more process, not less. The GitHub for Jira app shows branches, commits and pull requests on Jira work items, on the board and in releases, as long as your team puts the issue key in branch names, commit messages or pull request titles. Jira is free for up to 10 users.

If what pushed you off Zenhub was needing approval steps, several teams rolled up into one portfolio, or a marketplace of integrations, Jira will do it, and nothing smaller on this list will. If what pushed you off was cost or GitHub lock-in, Jira solves the lock-in and makes almost everything else heavier. Our list of Jira alternatives for small scrum teams exists for the teams who went that way and regretted it, and the Jira comparison page puts its bill next to ours.

Scrumpy: a standalone sprint board that sits beside your code

Scrumpy is ours, so weigh this section accordingly.

It is a standalone board, not a layer on GitHub. It does not connect to a code host, so a mixed or migrating shop is not left out. Developers reach it from their AI assistant instead: through Scrumpy's MCP server, Claude can start a story, get a branch name for it, and open the pull request with the GitHub access it already has. Sprints, story points, velocity and a burn-up chart are built in. View-only people join free, as many as you like, without a GitHub account. Pricing is one plan: $9 per editor per month, or $7.50 billed annually, with a 7-day trial that does not ask for a card.

Now the parts that matter for someone coming from Zenhub. Scrumpy does not move a card when a pull request merges. It does not watch your repository, so the board moves when a person, or their assistant, moves it. Linear and Shortcut both automate that, and if your team relies on it, that is a real loss. There is no Zenhub importer either: Scrumpy reads Jira and Linear CSV exports, so a Zenhub backlog comes over through the REST API or by hand. For a team with a few hundred open issues, the honest advice is to bring the next two sprints across and leave the long tail in GitHub. The side-by-side with Zenhub has the rest.

What twelve people actually pay

Here is the arithmetic that changed my mind while writing this. Take eight developers and four people who only watch: a product owner, a designer, a founder and a client.

On Zenhub Teams, Zenhub's own guest documentation says guests use a seat, so that is twelve seats at $4.99 billed yearly, about $60 a month. On Scrumpy, eight editors at $7.50 billed annually is also $60 a month, or $72 monthly. I expected the free viewers to win this comparison on price. They do not. Zenhub is not an expensive tool, and anyone telling you it is has not done the sum.

Tool 8 developers + 4 watchers, per month
Zenhub Teams about $60 billed yearly, every guest a seat
Scrumpy $60 billed annually, $72 monthly, watchers free
Shortcut Team $68, four free Observers
GitHub Projects included, plus $4 per watcher on GitHub Team if the repos are private
Linear Basic $120 billed yearly, no guests on Basic
Jira past the 10-user free plan, so a paid tier for all twelve

Shortcut lands at $68 because its observers ride free on paid seats. Linear costs twice what the others do at this shape, mostly because Basic has no guest role. If your team is twelve developers and no watchers, every free-viewer argument, ours included, disappears and the table looks different again.

When Zenhub is still the right call

Stay if your issues are a public front door and you want sprint reporting on exactly those issues, with no sync to babysit. Nothing else here does that as directly. Stay if you are under 50 people, on one or two repositories and under 250 issues, because then Zenhub's free plan carries more people than any other free plan on this list. And stay if the only thing that changed is the third repository: $4.99 a seat to keep your sprint reports past two repositories is a fair price.

Leave if you need a code host other than GitHub, if people outside engineering need more than a view, or if you have started to feel that your roadmap is welded to one platform. That last one is a feeling worth taking seriously before your backlog is twice its current size.

Whichever way you lean, run one real sprint in the tool you are considering before you move the backlog. Pick the two weeks, bring only what is in them, and see whether anyone misses GitHub. If you want that sprint to be on a board that sits beside your code rather than on top of it, start one in Scrumpy and connect it to your AI assistant.

Frequently asked questions

What are the best Zenhub alternatives?

For a small team on GitHub, the realistic Zenhub alternatives are GitHub Projects, Linear, Shortcut, Jira and Scrumpy. GitHub Projects keeps everything inside GitHub for no extra cost but has no velocity reporting. Linear can sync GitHub issues both ways for one repository, Shortcut and Jira link branches and pull requests to their own stories, and Scrumpy is a standalone sprint board that works next to any git host, with free view-only seats.

Is there a free alternative to Zenhub?

Yes, several. GitHub Projects is included with every GitHub plan, Shortcut's free plan covers 10 users and includes Iterations, Jira is free for up to 10 users, and Linear's free plan allows 2 teams and 250 issues. Zenhub's own free plan is also generous on people, up to 50 users, but caps you at 2 repositories and 250 issues.

Does a Zenhub guest cost a seat?

Yes. Zenhub's July 2026 documentation for the organization Guest role says guests are licensed members of the organization and use a seat. Guests are capped at viewing the workspaces they are added to, so a stakeholder who only watches still counts toward your Zenhub bill.

Can I keep using GitHub issues if I leave Zenhub?

It depends on the tool you move to. GitHub Projects works directly on your GitHub issues. Linear can sync new GitHub issues both ways for one repository per team, or one way from several. Shortcut and Jira keep their own stories and link them to your branches or pull requests instead, and Scrumpy keeps its own stories next to your code without connecting to it, so GitHub stops being the place the plan lives.

Keep reading