Story maps for GitHub Projects

Your GitHub becomes
a user story map.

GitHub is good at tracking issues. It is not good at showing you what to build next, or in what order. Fervio opens the same issues as a story map — move a card, and the issue itself changes.

No sign-in for the demo · Free to start · No credit card · We never read your code

Before Fervio
#101 Keyword searchopen
#121 Add to cartopen
#141 Shipment trackingopen
#131 Credit card checkoutopen
#102 Filter resultsopen
#111 Side-by-side compareopen
#133 Guest checkoutopen
#123 Save cart for lateropen
#151 Star ratingsopen
After Fervio — the same issues, now a plan
Find a product
Place an order
Receive & review
Search Compare Add to cart Pay Track delivery
1.0 Launch Aug 31 · 4/7
Keyword search #101
Save favorites #112
Add to cart #121
Credit card checkout #131
Shipment tracking #141
Filter results #102
Guest checkout #133
1.1 Improvements Sep 30 · 0/7
Side-by-side compare #111
Save cart for later #123
Star ratings #151
What you get

Everything the map needs. Nothing it doesn't.

Your issue list is flat. Your product isn't.

Build the story map

Arrange your issues into journeys and steps, and see the whole product on one screen.

Plan releases, not lists

Slice the map into releases, straight from your GitHub milestones. Export to Markdown or CSV anytime.

Drag a card, update the source

The issue moves with the card — milestone, cycle, custom fields and all. No copy-paste, no drift.

Share without a sign-in

A read-only link opens without an account of any kind. Editing access is never shared.

What changes

From tracking issues to deciding what to build next.

What the issue list tells you
  • What is still open
  • Who it belongs to
  • When it closed
What the same issues tell you on a map
  • Where the user flow is thin
  • What this release actually delivers
  • Which card to pick up next
Getting started

From sign-in to your first map, in three steps.

1

Sign in with GitHub

All you need is one GitHub Project. Fervio can create one during setup.

2

Pick what to map

Two single-select fields on the Project, Journey and Step. Your issues are left exactly as they are.

3

Lay out the cards

Move a card into a different release row and the real issue changes with it. Only the ordering is kept by Fervio.

Security & privacy

We never read your code. Your issues stay in GitHub.

  • Fervio never calls an API that reads your source code
  • Your issues stay in GitHub. No standing copy travels with us
  • Access tokens never reach the browser — they stay on the server
  • All we keep is your card layout and your sign-in record
  • No analytics scripts, no ad pixels, no passive trackers

GitHub's consent screen still shows a broader permission. The permissions page explains why, and the privacy page lists everything Fervio stores.

Pricing

Pro is $12/month, whatever the team size.

Add editors and the price stays where it is.

Reading a map, or opening a share link, is free on any plan. Pricing applies only to the people building maps.

Most planning tools charge per person. At $8 a seat, a team of four is $32/month. Fervio stays $12/month however many people edit.

Free

$0

For anyone with a GitHub Project. Every feature is included. No credit card, no trial clock.

  • 1 map you can edit
  • Connect every Project you can see
  • 3 people can edit, you included
  • Unlimited viewers and share links
Start for free

Pro

$12/month, any team size

For when one map is not enough, or a fourth person needs to edit. Not open for sale yet.

  • Unlimited maps
  • Unlimited editors
  • Unlimited viewers and share links
Coming soon

Why Fervio exists

GitHub is strong at tracking issues. It is weaker when you want to think about the user flow and the releases at the same time.

Another tool would solve that — and leave me keeping two trackers in sync.

So I built Fervio.

Feedback and requests — [email protected]

Questions

Does Fervio read my code?
No. There is no call anywhere in Fervio's code that fetches source. GitHub's consent screen will still say “full control of private repositories,” because GitHub offers no issues-only permission. 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 does a share link stay open?
Ninety days from the moment you create it. After that, you can issue a new one.
What can Fervio read from?
GitHub Projects (v2), personal and organization alike. Fervio asks for organization access only when you open an organization Project. If your team plans in Linear instead, that is 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, labels and Project fields — everything stays valid data in GitHub that you can keep using without us.