An open-source alternative to Miro
A canvas with frames, connectors and thirty-two shape kinds, plus the tracker and the pages the board feeds into. Run it on your own Postgres.
| Feature | Tuval | Miro |
|---|---|---|
| Licence | AGPL-3.0. Source on GitHub, no separate edition and no feature flags. | Proprietary, delivered as a hosted service. |
| Self-hosting | Your own Postgres and any S3-compatible bucket. One setting marks the install self-hosted and the seat, storage and API limits stop applying. | Not offered. |
| Price | Free for up to 3 people with 1 GB of files. Hosted plan ₺249 per member per month, VAT included, about $7. | Per-user subscription. We do not print a figure we cannot keep current; see their pricing page. |
| What goes on the canvas | Sticky notes, text, thirty-two shape kinds, connectors with more than one label, pen and highlighter, images, PDF import up to thirty pages, tables with merged cells, code blocks, embeds, mind maps, comment pins, presentation mode, minimap. | A comparable set of objects, plus diagramming and presentation features Tuval has not built. |
| Templates | Eight board templates and four database kits. | A large first-party gallery plus a public community library. Far more than eight. |
| Real-time editing | Yjs CRDT over Supabase Realtime, on private channels checked by the same row-level policies as the board. Live cursors and follow mode are written and have never been run through a two-person session. | Multiplayer editing in production use for years. |
| Mobile and tablet | None. Desktop browser only, by decision rather than backlog. | Native iOS and Android apps. |
| Board version history | Snapshots inside the board document, automatic every ten minutes, last twenty kept. | Version history on paid plans, with longer retention. |
| Getting a board in | Imports a Miro board through their REST API with a token you supply that stays in your shell. Also images, PDFs and a Markdown brief. | Not applicable. |
| Getting work out | PNG of any selection, one JSON backup of the whole workspace that restores, and a one-click brief that turns the board into markdown with a mermaid flow for an AI agent. | Image and PDF export and a documented REST API. |
| Integrations | REST API, webhooks and an MCP server for coding agents. No app directory and no built-in Slack, Jira or Figma connectors. | A large app marketplace and first-party integrations with the tools most teams already run. |
| Access control | Enforced in Postgres row-level security: editor and viewer roles, access by email domain, public read-only links, per-page roles. No SAML SSO and no SCIM. | Enterprise identity controls including SAML SSO and SCIM provisioning. |
Checked 1 August 2026. Miro is a trademark of its owner; Tuval is not affiliated with, endorsed by or sponsored by them.
Why you might not
Because a decade-old product will not fall over in front of your client, and ours has never been through a two-person session.
What we do better
Three things. The canvas is not a separate product: select a sticky, turn it into an issue, and the card stays exactly where the thought was while the issue appears in the cycle. The board exports as a brief an agent can act on rather than a picture, and an MCP server lets Claude Code or Cursor read the workspace directly. And you can run the whole thing yourself under AGPL-3.0, on your own Postgres and your own bucket, with nothing held back.
What Miro does better
Almost everything to do with maturity. Their multiplayer has been carrying workshops for years; ours is written and unproven with two people in the room. They have native mobile and tablet apps; we have decided not to build a phone layout at all. They have thousands of templates and an app marketplace; we have eight templates and a REST API. They have a support organisation, published security certifications and enterprise identity provisioning; we have an issue tracker and one maintainer.
Who should not switch
Anyone whose whiteboard is client-facing and unrehearsed. Anyone whose team joins from phones or tablets. Anyone who needs SAML SSO, SCIM or a signed support agreement to get software approved. Anyone whose workflow depends on the template gallery or on connectors to Jira, Slack or Figma. And anyone who cannot spare a person to run a Postgres database and a bucket.