For open-source projects
Open source
Design in the open, on an open-source core: contributors join from a browser link, files stay exportable, and the code that opens them is public — anyone can inspect, run and extend it.
- Three editors collaborate free — viewers are unlimited
- The core that opens your files is open source — read it, run it, embed it
- CLI export fits docs builds and CI pipelines
The open half of the stack
Design in the open, finally
Open-source projects review code in public with real diffs — and then discuss logo and UI proposals as PNG attachments in issue threads. Tuvi gives design work the same daylight: one shared document for the project's visual assets, a public view link in the README, and comments pinned to the exact frame under discussion. A maintainer's design decision becomes something the community can see forming, not an image that appears fully grown.
The collaboration mechanics mirror the contribution model the community already knows: propose in a branch, discuss in context, merge with review. Two contributors exploring icon directions are not overwriting each other — the project gets alternatives and a visible decision.
A core you can inspect and embed
The unusual part of Tuvi for an open-source audience is under the canvas: the core that opens and draws design files is open source, and it also ships as a command-line tool and an embeddable library. A project can render its design file to PNG in CI for docs and previews, or build its own tooling on the same code the editor uses.
That openness is a guarantee of a kind no feature list provides: the format your assets live in is readable by code anyone can inspect and run. Files that open in a browser today will still be readable by a library tomorrow, whatever happens to any single product.
Contributors welcome, seats not required
Open-source budgets round to zero, and the plan structure respects that: a Starter team covers three editors for free, viewers are unlimited on every plan, and each contributor's personal drafts cost nothing forever. The person who shows up once a year to refresh the social preview image does not need a seat, a license or anyone's approval — just the link.
And since a growing share of contributions now arrive through AI agents, MCP matters here too: an assistant helping with the project's site or docs can read the design's real structure and generate code from it, instead of reverse-engineering screenshots out of the repository.
Frequently asked questions
Is Tuvi itself open source?
The core is: the code that opens and renders .fig files is developed in the open, and you can read it, build it and embed it today. The hosted collaboration product is built on top of that open core.
Can we use the core in our own project?
Yes — it ships as a command-line tool and an embeddable library. Open .fig files, render documents and export PNG inside your own tools or CI, on the same open code the editor runs.
What does it cost a project with no budget?
Zero is a workable answer: personal drafts are free forever, a Starter team gives three editors 1 project and 10 files at $0, and view links let the entire community follow along without accounts or seats.
How do design contributions get reviewed?
Like code: a contributor branches the file, works freely, and the change comes back through a merge with review. Comments sit on the canvas in context, so the discussion and the decision both leave a trace.