Story maps for GitHub Issues
Your GitHub issues become
a user story map.
A list of GitHub issues tells you what is open. It does not tell you what to build next, or where each one sits on the path your users take. Fervio lays the same issues out as a story map — move a card, and the issue itself changes.
No sign-in for the demo.
Lay the issues out, plan the releases, send the link.
Build the story map
Arrange your issues into journeys and steps, and see the whole product on one screen.
Plan by release
Slice the map into releases, straight from your GitHub milestones. Export to Markdown or CSV anytime.
Drag a card, change the issue
Move a card and the issue in GitHub changes with it — its labels and its milestone. Nothing to update twice.
Share without a sign-in
A read-only link opens without an account of any kind. Editing access is never shared.
From sign-in to your first map, in three steps.
Sign in with GitHub
All you need is a repository with issues in it. There is nothing to set up first.
Pick your repositories
Choose one or more, and their open issues land on a single map. Nothing is changed until you move a card.
Lay out the cards
Journeys and steps become labels, release rows become milestones. Fervio keeps only the order.
Fervio cannot read your code.
- Code access is never granted — GitHub itself will not hand it over
- Issues are never copied into Fervio — Fervio reads GitHub every time you open a map
- Access tokens never reach the browser
- Fervio stores map settings and layout, the member list, and your sign-in and contact details
- Publishing a share link stores a snapshot of that moment, and nothing else
- No analytics scripts, no ad pixels, no passive trackers
Pro is $12/month, whatever the team size.
Free
$0
For anyone with a GitHub repository. Every feature is included. No credit card, no trial clock.
- 1 map you can edit
- Connect as many repositories as you like
- 3 people can edit, you included
- Unlimited viewers and share links
Pro
$12/month, any team size
For when one map is not enough, or a fourth person needs to edit. Not available yet.
- Unlimited maps
- Unlimited editors
- Unlimited viewers and share links
Questions
- Does Fervio read my code?
- It cannot. Fervio is a GitHub App, and the permissions it asks for are declared on the app itself — issues, repository names, organization membership and email addresses, and no access to file contents or to pull requests. You can read that list on GitHub before you grant anything. The permissions page covers it in full.
- Do the people I share with need an account?
- No. Read-only share links open without any sign-in, so you can send a map to anyone.
- How long do share links last?
- Ninety days from the moment you create one. After that, issue a new one.
- What can Fervio read from?
- The repositories you pick when you install it, personal and organization alike. Repositories you leave out stay invisible to Fervio. Linear teams use a separate product, at linear.fervio.co.
- What happens if I go over the free limit?
- Nothing is deleted. The maps beyond the limit become read-only, and you choose which ones stay editable — you can change that choice at any time. Everyone can still read them, and share links keep working.
- What happens to my issues if I stop using Fervio?
- Nothing. Fervio writes plain issues, milestones and labels — everything stays valid data in GitHub that you can keep using without us.