A story map that leads your backlog.
CardBoard is a user story mapping tool that syncs with Jira, Azure DevOps, Linear, Shortcut, and Trello without tying the map's layout to your backlog. Compared with StoriesOnBoard, an AI agent's changes arrive as proposals a person accepts, status syncs both ways, guests can edit for free, and there's a free plan. StoriesOnBoard fits better if you want map releases synced with your tracker or run Jira Server or TFS on-premises.
Two good story mappers, two different bets.
StoriesOnBoard is a dedicated story mapping tool with a long track record, and it's a solid one. Its bet is that the map should mirror the backlog. Bind the levels to your epics and features, sync the releases, and let the tracker own status.
CardBoard, built in 2012 by David Hussman alongside Jeff Patton, bets the other way. The map is where the team decides what matters to the user, so it has to be free to disagree with the backlog until the team agrees. The fields sync both ways. The layout never does.
CardBoard vs StoriesOnBoard, row by row.
| CardBoard | StoriesOnBoard | |
|---|---|---|
| Tracker sync | ||
| Trackers | Jira, Azure DevOps, Linear, Shortcut, Trello. Cloud only. | Jira Cloud and Server, Azure DevOps and TFS, Trello, GitHub, Pivotal Tracker |
| Status | Both ways | Editable only in Jira or Azure DevOps, then shown on the map |
| Title, description, estimate | Both ways | Both ways |
| Acceptance criteria | Both ways with Azure DevOps | Not listed among synced fields |
| Assignee | Both ways with Azure DevOps and Jira | Not listed among synced fields |
| Who places a card | You. Tracker changes never move a card. | Map levels can be bound to epics and features, and releases synced with the tracker |
| The map | ||
| Map types | Story maps plus more than twenty others: opportunity solution trees, process maps, canvases | Story maps, plus roadmaps and idea boards on the product management plans |
| Grouping | Named groups of cards anywhere on the map, with no card moved | Tags, personas, and filters |
| Live collaboration | Always-on live cursors, visible selections, follow a teammate | Online avatars, which card each person is viewing, follow a presenter |
| Version history | Activity feed per board and card. No restore. | Card history with compare |
| Search | Within a board | Across story maps |
| AI agents | ||
| MCP server | Every plan | Standard plan and up |
| Agent edits to cards | Arrive on the board as proposals. Nothing changes until a member accepts. | Create, update, and move cards through MCP tools |
| Who answers for the change | The member who accepts it. The accept is recorded under their name, with the agent credited as proposer. | Not described in their MCP docs. Their Claude walkthrough reviews the plan in chat, then the agent writes the cards. |
| Built-in AI | Bring the agent you already use | Built-in generation with a monthly token allowance |
| Plans and people | ||
| Free plan | Yes, three boards | No. 14-day trial. |
| Tracker sync starts at | Pro, $10 a month billed annually | Standard, $9.60 per user a month billed annually |
| Guests | Free, and can edit the map | Free viewers who can comment but not edit |
| SSO and audit log | SAML SSO on Enterprise. Audit log on Team and up. 2FA on every plan. | SAML SSO and audit log on Pro |
StoriesOnBoard facts from its own site and help center, checked September 28, 2026: Pricing, Jira sync, Azure DevOps sync, Azure DevOps hierarchy, User roles, Online users, MCP server, Claude walkthrough. CardBoard facts from our docs and pricing.
Four differences you'll notice in the first week.
A person signs for every agent change
Both tools have an MCP server, so Claude can work on a map. In CardBoard an agent's card, edit, move, or delete shows up on the board as a proposal with its reason attached. A member accepts or dismisses each one, and the accepted card is theirs. Nothing on the map is there because an agent decided it alone.
Status moves from either side
In StoriesOnBoard, a linked card's status can only be changed in the tracker. Their docs call it a safeguard for teams mid-execution. In CardBoard, a product manager can mark a story done during a review and Jira or Azure DevOps hears about it, with the change recorded under that person's own tracker account.
The map can disagree with the backlog
StoriesOnBoard can bind the map's levels to epics and features and sync its releases with the tracker, so the map stays a faithful picture of the backlog. CardBoard syncs the fields and leaves the layout alone. You can move a story to a later slice while you argue about scope, and nobody's sprint changes until you decide.
Guests edit, and it's free to start
A workshop is where a story map earns its keep, and the people in the room are often not on your plan. CardBoard guests can edit on every plan, including the free one. StoriesOnBoard viewers are free too, but they can only comment, and there's no free plan past the trial.
On Azure DevOps, acceptance criteria sync too. CardBoard and StoriesOnBoard with Azure DevOps goes field by field. On Jira, see story mapping with Jira.
The agent drafts. A person takes responsibility.
Hand either tool a requirements doc and Claude can turn it into a story map over MCP. StoriesOnBoard's own walkthrough does it well. Claude lays out the goals, steps, and releases in the chat, waits, the author changes two things, and then Claude writes the cards. That review is real. It's also one person's call, made once in a chat. The cards then go onto the map as the agent wrote them.
CardBoard moves the review onto the board, where it stays for as long as the map does. Every change an agent makes arrives as a proposal: a new card, an edit to a description or acceptance criteria, a move to another slice, a delete, a connection. Everyone on the board sees it, with the agent's reason attached. A member accepts or dismisses each one, and the accepted card is recorded as that member's work, with the agent credited as the one who proposed it.
That matters most on the map your team builds from. When a story is wrong, there is a person who put it there, and you can ask them why. An agent can draft a hundred cards in a minute. It can't be accountable for any of them.
- Point Claude at CardBoard. Connect over MCP from Claude, Cursor, or any client that speaks it. Free on every plan.
- Give it the doc. Ask for the backbone, the stories under it, and a first release slice. They land on the board as ghosts.
- Decide on the board. Accept the batch, or go card by card. Dismiss what's wrong.
How the tools work and which clients connect: CardBoard for agents. Starting from a diagram your AI already drew? Mermaid into a typed map.
Stay with StoriesOnBoard if:
- You want the map's releases synced with Jira releases or Azure DevOps iterations.
- You run Jira Server, Team Foundation Server, or another tracker on-premises. CardBoard connects to cloud trackers only.
- You sync with GitHub Issues. CardBoard doesn't.
- You need to restore an earlier version of a card, or search across every map.
- You want AI that writes stories and acceptance criteria inside the tool, without bringing your own agent.
Frequently asked questions
- What's the best StoriesOnBoard alternative?
- It depends on why you're leaving. If you want status to sync both ways, a map whose layout isn't tied to your backlog, free guests who can edit, or a free plan, CardBoard is built for that. If you want a whiteboard with a pen, look at Miro. If you want one flat price for unlimited users, look at Avion. The full field is on our comparison of story mapping tools.
- Is CardBoard free?
- Yes. The free plan includes three boards, and guests are always free. Syncing with Jira, Azure DevOps, Linear, Shortcut, or Trello needs a paid plan, from $10 a month billed annually.
- Does StoriesOnBoard sync status both ways with Jira?
- No. Its Jira and Azure DevOps help articles say linked cards' statuses are editable only from the tracker, and changes there show up on the map. CardBoard syncs status both ways with every tracker it supports.
- Can I move from StoriesOnBoard to CardBoard?
- If your StoriesOnBoard map syncs with Jira or Azure DevOps, the tracker already holds the work. Connect a CardBoard board to the same project and import the work items. With Azure DevOps, the first layout follows your Epic, Feature, and User Story tree. For anything that isn't in a tracker, CardBoard imports cards from CSV.
- Can AI build a story map from a requirements document?
- Yes, in both tools, through an MCP server and an agent like Claude. The difference is what happens to the result. In StoriesOnBoard the agent writes cards to the map. In CardBoard the cards arrive as proposals, and a member accepts each one, so every card on the map has a person who answers for it.
- Does CardBoard have AI?
- CardBoard works with the agent you already use, like Claude or Cursor, through its MCP server on every plan. Agent changes to cards arrive as proposals a member accepts. It doesn't have built-in generation with a token allowance the way StoriesOnBoard does.
Comparing more than two? See the best user story mapping tools. Moving a backlog over? Start with connecting your tracker or CSV import.
Try it on the map you already have.
Connect the same Jira or Azure DevOps project, import the backlog, and see if the map reads better when you own the layout. Free to start. Tracker sync from $10 a month.