zeroheight review

zeroheight is a managed workspace for documenting and maintaining a design system. It brings design files, component references, tokens, code, and written guidance into a documentation site that teams can edit without building the whole thing in code. The product connects to Figma, Storybook, and code repositories; its tools also cover token syncing, approvals, access, and adoption insights. zeroheight says its MCP integration gives AI agents access to design-system context.

That makes it different from treating Storybook as the whole documentation platform. In one Reddit discussion, a Storybook Docs creator described Storybook as developer-friendly documentation with the repository as the versioned source of truth, while zeroheight was described as a more CMS-like layer connecting design and code. Those approaches can complement each other, but they put editing and ownership in different places. Choose based on who needs to maintain the docs and where your team wants its source of truth to live.

The main advantage is joining design references and written guidance in one managed site. Teams can sync Figma designs and variables, bring in Storybook components and repository code, then use no-code editing and customizable templates to document how components should be used. That is useful when designers, developers, and other contributors need to work on the same system without every doc change becoming a code task.

Token tools add a practical workflow: zeroheight says teams can sync tokens across Figma files, compare brands and modes, and push changes to code. It also offers change approvals, outdated-content markers, and controls for contributions. Adoption insights are aimed at answering whether people use the docs and whether components reach code, rather than just counting published pages. Its MCP integration gives AI agents design-system context.

The free plan includes one editor, one styleguide, one token set, 500 MCP Standard Search calls per month, and seven days of page history. Starter costs $59 per editor monthly or $588 per editor annually, equivalent to $49 per month, according to the pricing page. It allows up to five editors, two styleguides, three token sets, and 30 days of page history.

The cost is harder to justify when most people only read the docs. Starter is charged per editor, with a minimum first purchase of one editor; the annual price is $588 for that editor, while monthly billing is $59. The free tier is narrow: one editor, one styleguide, one token set, and only seven days of page history. Enterprise pricing is custom, so teams needing its 5+ editors and reviewers, 5+ styleguides, 10 token sets, SSO, or trusted IP range cannot compare that cost from the published figures. The pricing page also lists a 14-day trial.

Zeroheight is not automatically the right home for teams that want code to own the documentation. A Reddit discussion notes that Storybook Docs supports MDX and keeps documentation versioned with the repository, though it involves more manual code editing. Another thread raised concern about paying for zeroheight when the audience was mainly viewers. A separate team seeking self-hosting said zeroheight’s password-protected option did not meet its business requirements. These are user reports, not universal product limits, but they flag two questions to settle before switching: who edits, and where the docs can be hosted.

zeroheight has a free plan, a 14-day free trial, and custom-priced Enterprise. According to the pricing information checked November 7, 2026, Starter costs $59 per editor per month when billed monthly, or $588 per editor per year ($49 per month) when billed annually—a 15% saving. The first Starter purchase has a minimum charge for one editor, and the plan supports up to five editors.

The free plan is limited to one editor, one styleguide, one token set, 500 MCP Standard Search calls per month and seven days of page history. Starter raises those caps to two styleguides, three token sets and 30 days of history, but still includes 500 monthly MCP calls. That is the practical jump: more editing capacity and documentation, not more MCP calls. Enterprise has custom pricing and includes five or more editors and reviewers, five or more styleguides, 10 token sets, SSO and a trusted IP range. Budget by editor, not reader; the published pricing details do not list a separate viewer price.

The published information lists connections for Figma, Storybook and code repositories, plus tools for docs, tokens and change control. It does not describe a migration service, import options for existing documentation, data-export formats or a self-hosting option. So we can’t estimate migration effort or confirm how easily content moves out. Before switching, inventory your current docs, tokens and component sources, then ask zeroheight to demonstrate the import and export paths for each.

The product is a poor fit if self-hosted documentation is a requirement, according to our verdict. That makes portability worth settling before you build workflows around it. Reddit posts or comments weren’t included in the published material, so we can’t responsibly say what users there report as reasons for leaving. Ask about export, access after cancellation and handling of linked source content before committing; those details are not published in the published information.