Zeroheight
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Zeroheight Ltd · zeroheight.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Zeroheight at a glance
- Vendor
- Zeroheight Ltd
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- In the EU source, captured 17 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 17 Nov 2026
- Panel verdict
- The AI panel rates Zeroheight 3/5, the mean of 6 judges. Zeroheight is a design-systems documentation and token governance product rather than a drawing tool: the judges describe authoring in Figma, with token sets read-only and edits flowing back upstream. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Zeroheight is a design-systems documentation and token governance product rather than a drawing tool: the judges describe authoring in Figma, with token sets read-only and edits flowing back upstream. Its strongest scores sit in collaboration and handoff and file ownership and portability, both 6 to 7: bidirectional Git sync with GitHub, GitLab, Bitbucket and Azure DevOps, thirteen token export formats including W3C-compliant and DTCG JSON, an MCP server that checks code against tokens, and comment-only reviewers who see unreleased changes. Design and prototyping and brand asset governance also score 6 to 7; no judge disagreement was flagged, with shared gaps: no public information on a canvas or interactive prototyping, an API reserved for Enterprise plans, and no public information on bulk export or post-cancellation retention. The low scores are sovereignty, held at 4, where the stated EU-only data residency sits beside unknown legal-entity jurisdiction, DPA and subprocessor entries, and AI and content rights at 4 to 5, beyond the opt-in, no-training statement. No paid plan carries a public price.
Speaks for it
- Tokens export in thirteen formats including W3C-compliant JSON and DTCG JSON, delivered via exports, hosted URLs, pull requests or the API
- Bidirectional Git sync with GitHub, GitLab, Bitbucket and Azure DevOps sends token edits back as pull requests, with markdown sources syncing through the GitHub integration
- Comment-only reviewers see everything editors see — including unreleased changes and hidden pages — alongside per-styleguide permissions and SAML SSO
- Multi-brand setups run one styleguide per brand or a shared guide, with partner access scoped so partners see only the tokens they control
- The security page documents AWS hosting in Ireland with tested failover in Germany, AES-256 at rest and TLS 1.2+ in transit, backed by SOC 2 Type II, ISO 27001 and GDPR compliance
Held against it
- We found no public information on a canvas, vector editing or interactive prototyping — authoring and token edits run through Figma, and token sets are read-only
- The API that lists sets and fetches any format is Enterprise plans only
- We found no public information on the contracting entity's jurisdiction, a DPA or a subprocessor list, and the optional AI feature can send content to a provider whose location is not stated
- We found no public information on which provider runs the AI features, where its processing happens, commercial-use rights on generated output, or indemnity
- We found no public information on bulk export of a team's styleguides or on what happens to content after a downgrade or cancelled contract
Best for
- You document a multi-brand design system and need per-brand or shared styleguides with partner access scoped to the tokens partners control
- Your developers build from design tokens and want Git-based delivery — pull requests on GitHub, GitLab, Bitbucket or Azure DevOps and thirteen export formats including W3C-compliant JSON
- You need a review gate before publication, with comment-only reviewers able to see unreleased changes and hidden pages
- You already author in Figma and want governed token and styleguide publishing rather than a second design editor
Avoid if
- You need to draw and prototype inside the tool itself — the documented workflow routes authoring and token edits through Figma
- You need the API below the Enterprise tier — the pages list it as Enterprise plans only
- You need live, automatic propagation from Figma — sync is documented as deliberately one-way and on-demand rather than live
The scores
| Criterion | Panel median |
|---|---|
| Design, prototyping & design systems | 3.5 of 5 |
| Collaboration, review & developer handoff | 3.5 of 5 |
| Brand assets & governance | 3 of 5 |
| Files, formats & portability | 3 of 5 |
| AI features & rights to the work | 2.5 of 5 |
| European sovereignty | 2 of 5 |
Design, prototyping & design systems
Show reasoningHide reasoning
How this is scored
The making itself: vector and layout tools, interactive prototypes, and the shared components, styles and tokens that keep a company's products and materials consistent — judged on what the feature and help pages document, not on showcase images.
0 — Not a design tool: a file viewer, a stock library or a single-purpose converter in which nothing is laid out or drawn.
3 — A canvas or editor with templates, shapes, text and images; reusable components, shared styles and prototyping are basic or not described.
5 — Reusable components or styles shared across files, responsive or auto layout, and clickable prototypes or presentations linking screens.
8 — A design system managed in the tool: team libraries that update where they are used, variables or tokens for colour, type and spacing with modes or themes, component variants and properties, prototypes with transitions and conditional logic, and library changes published with versions.
10 — The design system is a governed product: library releases versioned and reviewable, token export in a documented format for development, usage analytics per component, and accessibility checks such as contrast built into the editor.
The Product Designer
The token system is managed as a product: Figma variables sync into a tokens manager where modes are shown as columns and multiple modes are viewed simultaneously, aliases resolve across brands, guardrails catch duplicate paths and broken aliases, and adoption analytics track usage. Release-gated styleguides with comment-only review make changes reviewable before publication, and tokens export in W3C-compliant and DTCG JSON — exactly the governed-product behaviour I look for. What holds it back is the making itself: the captured pages describe no canvas or prototyping, components are documented from Figma rather than authored here, and token sets are read-only with edits flowing back upstream through Figma. 3 4 5 10
The Frontend Engineer
The captured pages show a design-systems home rather than a design editor — I found no canvas, drawing or prototyping there — but the token management is genuinely deep: modes displayed as columns, aliases resolving across multiple Figma files, validation guardrails for duplicate paths and broken aliases, token adoption analytics, and export in thirteen formats including W3C-compliant and DTCG JSON. Token sets are deliberately read-only with edits flowing upstream through Figma, which keeps the single source of truth honest. I hold it below the top level because the authoring and prototyping layer is entirely absent from the evidence. 3 4 7 9 10
The Brand Marketer
This is a design-system documentation and token tool rather than a drawing canvas: Figma variables sync in with modes and aliases preserved, styleguide pages carry live token tables that update automatically on sync, and content ships through releases with unreleased changes and a changelog. Tokens with brand modes, guardrails against broken aliases and adoption analytics put the design-system side near the top of the range; we found no public information on vector layout tools or interactive prototyping in the product itself. 3 4 7 8
The Agency Owner
The drawing happens in Figma: token sets here are read-only with edits flowing back upstream, and no captured page shows a canvas, vector tools or prototyping. What is documented deeply is the system side — tokens synced from multiple Figma files with modes and themes, brand collections, and styleguide releases with a changelog — which lifts it past basic component sharing. 3 4 7
The Data Protection Officer
The captured pages document a design-system documentation and token governance tool: tokens synced from Figma variables and styles with modes and alias warnings, validation guardrails, token search, releases with a changelog, per-token adoption analytics, and live component previews with mode switching. We found no public information on vector or layout drawing, prototyping with transitions and conditional logic, or built-in accessibility checks, which is what would move it to the top level. 3 4 7
The Skeptic
This is a design-systems layer rather than a drawing tool: Figma variables sync one-way into a Tokens Manager that shows modes as columns, warns on broken aliases and duplicate paths, and publishes into styleguides and pull requests in thirteen formats including DTCG JSON. The token and documentation machinery is genuinely deep — mode-aware token tables, in-page mentions that resolve live, releases with changelogs — but the captured pages describe no canvas, vector editing, layout system or interactive prototypes, so I score the systems half of the criterion rather than a making tool. 3 4 7 9
Collaboration, review & developer handoff
Show reasoningHide reasoning
How this is scored
Working on the same files with colleagues, clients and developers: comments and review, permissions for internal and external people, and the handoff that gives engineering measurements, assets and code rather than screenshots.
0 — A single-user tool: files are worked on alone and passed on as exports.
3 — Files shared by link with comments or real-time co-editing; guest access, permissions and a developer view are basic or not described.
5 — Real-time co-editing, comments with mentions, sharing with view or edit rights per file or project, and an inspect or developer view with measurements and asset export.
8 — Guests and reviewers who comment without a paid seat, version history with restore, branching or review of changes before they reach the main file, a developer mode that links components to code, a documented API and plugins, and named integrations with issue trackers and code tools.
10 — Handoff is a contract between design and code: component properties mapped to code components, token and asset export automated through the API, an audit log of access and sharing, and external access governed by domain, expiry and admin policy.
The Product Designer
Comment-only reviewers who can see everything editors see and comment on unreleased changes give design ops a genuine review gate before anything is published, and per-styleguide view and edit permissions with named roles cover internal and partner access. The developer handoff is real rather than screenshots: an Inspect mode with an Open in Figma jump to the component, a documented API (Enterprise plans), token edits delivered as pull requests to GitHub, GitLab, Bitbucket or Azure DevOps, and an MCP server that lets coding agents check files against tokens and swap hardcoded values for the nearest token. The captured pages give no information on real-time co-editing, guest seat billing, or issue-tracker integrations. 3 5 6 7
The Frontend Engineer
The reviewer role is what I want to see: comment-only access to the signed-in view, including unreleased changes and hidden pages, seeing everything an editor sees without the ability to edit or push releases. Inspect mode carries an Open in Figma button, the MCP server lets a coding agent check a file against tokens and replace hardcoded values, and token sync runs bidirectionally over GitHub, GitLab, Bitbucket and Azure DevOps with pull requests. The API that lists sets and fetches any format is reserved for Enterprise plans, and the pages say nothing about whether commenters and viewers avoid a paid seat or about access logs. 3 5 6 7
The Brand Marketer
Comment-only reviewers who see everything an editor sees — including unreleased changes and hidden pages — plus per-styleguide view and edit permissions and SAML SSO for editors, reviewers and viewers give real review control before anything is published. Handoff is token-centric: an Inspect mode with an Open in Figma link, an API that lists sets and exports on Enterprise plans, pull-request delivery and an MCP server for coding agents; we found no public information on real-time co-editing, measurements and asset export, or version restore. 2 3 5 6 7
The Agency Owner
Reviewers get comment-only access including on unreleased work before a release is pushed, and per-styleguide permissions split admins, editors and viewers — though the pages are silent on whether reviewers need a paid seat. Developer handoff is strong: an Inspect mode with an Open in Figma link, tokens delivered as pull requests, an MCP server for coding agents, Git integrations and an API that sits on Enterprise plans. 2 3 5 6 7
The Data Protection Officer
Reviewers get comment-only access to everything editors see including unreleased changes, permissions are set per styleguide with named roles, and an Inspect mode links documented components back into Figma, with a documented API and named integrations with GitHub, GitLab, Bitbucket and Azure DevOps plus an MCP server for coding agents. We found no public information on whether reviewers are free of charge, on real-time co-editing, or on an audit log of access and sharing. 2 3 5 6 7
The Skeptic
Reviewer access gets its own page — comment-only, able to see unreleased changes and hidden pages, everything an editor sees minus editing and the release button — alongside per-styleguide permissions and SAML SSO for editors, reviewers and viewers. The handoff side is the strongest I have read in this category: tokens delivered as pull requests to GitHub, GitLab, Bitbucket or Azure DevOps, thirteen export formats, an MCP server that checks code against tokens, and scanning for hardcoded values in repos. Two things hold me back: the API is 'Enterprise plans only', and nothing states whether reviewers or viewers sit on a free or paid seat. 2 3 5 6
Brand assets & governance
Show reasoningHide reasoning
How this is scored
Keeping a brand usable and correct across a company: a central library for logos, images and templates, brand guidelines people can find, locked templates that let non-designers produce material, and rights and expiry metadata on every licensed asset.
0 — No shared assets of any kind; the product has no library, kit or template that a team uses together.
3 — A shared folder, brand kit or template set with logos, colours and fonts; locking, guidelines and asset metadata are basic or not described.
5 — A central brand kit or library with logos, colours and fonts, team templates that non-designers can fill, and the ability to lock brand elements or restrict who edits templates.
8 — Brand guidelines published in the tool, tagging and search across assets, approval workflows for new assets and template output, version control on assets, rights, usage and expiry metadata with warnings on expiry, and access per team, market or partner.
10 — Brand governance is auditable: every asset carries its licence, owner and permitted use, usage of each asset is tracked across files and channels, distribution to external partners is logged, and the whole library with metadata is exportable in a documented format.
The Product Designer
Multi-brand is a first-class concern: each brand can get its own styleguide or share one, brand-specific token collections are consolidated into a single token set, and white-label partner access can be scoped so partners see only the tokens they control while locked system-level values stay out of reach. In-page tabs with a theme switcher let one set of published pages serve multiple brands, themes or languages, and changes pass a reviewer gate before release with a changelog behind it. We found no public information on a library of licensed logos, images or templates carrying rights, usage and expiry metadata. 5 7 8
The Frontend Engineer
Multi-brand is a first-class concept — one styleguide per brand, a single shared multi-brand styleguide, or hybrids — with white-label partner access scoped so partners see only the tokens they control and never the locked system-level values, plus in-page tabs for languages, light and dark mode, and different brands. That is real brand governance structure with access control per audience. I found no public information on rights, usage or expiry metadata for assets, or on asset-level versioning and approval for asset output. 7 8
The Brand Marketer
Published styleguides support one per brand or a shared multi-brand hub, in-page tabs per brand, language or theme, and white-label partner access scoped so partners see only the tokens they control while system-level values stay locked — exactly the control I want over twelve offices. Changelogs, releases and per-styleguide permissions govern the guidelines well; we found no public information on a logo or stock library carrying licence and expiry metadata, or on locked templates that non-designers fill in to produce their own material. 3 4 5 7 8
The Agency Owner
Multi-brand setups, in-page tabs per brand, language or theme, a theme switcher, and partner access scoped so partners see only the tokens they control while system values stay locked — that is real brand governance across markets and partners. We found no public information on a logo or image library, locked templates for non-designers, or licence, usage and expiry metadata on assets. 7 8
The Data Protection Officer
Brand guidelines are published in the tool, structured as one styleguide per brand or a shared multi-brand styleguide, with in-page tabs for brands, languages and light or dark themes, white-label partner access scoped so partners see only the tokens they control, and releases plus a changelog giving versioning. We found no public information on rights, usage or expiry metadata for licensed assets, on tagging and search across images, or on approval workflows for new assets. 2 7 8
The Skeptic
Brand guidelines are the product here: one styleguide per brand or a shared multi-brand guide, partner access scoped so partners see only the tokens they control while system-level values stay locked, plus changelogs, contribution access controls and token adoption analytics. The governance shown is over tokens and documents; we found no public information on a central library of licensed logos, images or fonts, on rights, usage or expiry metadata, or on approval workflows for new assets. 4 7 8
Files, formats & portability
Show reasoningHide reasoning
How this is scored
Whether the work can leave: open or documented file formats, export that keeps layers, vectors and components, offline or self-hosted options, and what happens to files after a downgrade, a removed seat or a cancelled contract.
0 — Work cannot leave the product: no export or download of designs is offered.
3 — Export of designs as images or PDF per page or frame; export of whole files with structure and access after cancellation are basic or not described.
5 — Export to PNG, PDF and SVG with vectors and text kept, whole files downloadable to a local copy, and files of a downgraded or cancelled account addressed in the help centre or terms.
8 — An open or publicly documented file format, import from and export to other named tools documented, bulk export of a team’s files, an API that reads full file structure, files of removed users transferred to the organisation by policy, and a stated retention and deletion timeline after the contract ends.
10 — Portability is built in: an open-source or openly specified format, self-hosting or a local-first option, round-trip export without loss of components and prototypes, and the customer’s ownership of all files and their export rights written into the terms.
The Product Designer
Tokens leave in openly specified formats — W3C-compliant JSON and DTCG JSON among thirteen export formats — and delivery is engineered for pipelines: hosted Style Dictionary URLs that consuming projects pull directly, API access to fetch any format on Enterprise plans, and bidirectional Git sync that sends edits back as pull requests. Markdown documentation also round-trips through GitHub, GitLab and Bitbucket. We found no public information on bulk export of a team's styleguides, or on what happens to files after a downgrade or a cancelled contract. 3 7 9 10
The Frontend Engineer
Token export is the best-documented capability in the whole product: W3C-compliant and DTCG JSON, CSS, SCSS, Swift, Flutter, Android and iOS formats, Style Dictionary pulled via hosted URL, thirteen formats in total, with bidirectional Git sync that opens pull requests on a new branch and the token manager available on the free plan. Markdown source files also sync through the GitHub integration, so documentation content can live in your own repositories. The API that lists sets and fetches formats is Enterprise-only, and I found no public information on what happens to files after a downgrade, a removed seat or a cancelled contract. 3 4 9 10
The Brand Marketer
Tokens leave in thirteen formats including the documented DTCG and W3C JSON formats, delivered by export, hosted URL, pull request or API, with bidirectional sync to GitHub, GitLab, Bitbucket and Azure DevOps and import from Figma — the code-facing side of portability is well documented. We found no public information on downloading whole styleguides with their structure, bulk export of a team's content, or what happens to files after a downgrade or a cancelled contract. 3 4 9 10
The Agency Owner
The token system leaves cleanly: thirteen export formats including W3C-compliant JSON and DTCG, delivered as files, hosted URLs, pull requests or API, with GitHub, GitLab and Bitbucket round trips and the token manager on the free plan. For a client handover I still need answers the captured pages do not give — we found no public information on bulk export of a team's styleguides, a stated retention or deletion timeline after a cancellation, or ownership terms for the content. 3 4 9 10
The Data Protection Officer
Tokens export in thirteen formats including the open W3C-compliant and DTCG JSON formats, sync bidirectionally with named git platforms through pull requests, and can be delivered via exports, hosted URLs, the API or pull requests. We found no public information on export of whole styleguides with structure, bulk export of a team's content, transfer of removed users' files to the organisation, or a retention and deletion timeline after the contract ends. 3 4 9 10
The Skeptic
Token portability is real rather than marketing: thirteen export formats including DTCG JSON and W3C-compliant JSON, delivery by exports, hosted URLs, pull requests or API, and two-way sync with four Git platforms so source files can live in the customer's own repositories. The story stops at tokens and markdown sources: we found no public information on bulk export of a team's styleguides or on what happens to content after a downgrade or cancelled contract, and the API that fetches any format is gated to Enterprise plans. 3 4 9 10
AI features & rights to the work
Show reasoningHide reasoning
How this is scored
What the vendor's AI does with the customer's files and what the customer may do with the AI's output: training on customer content and the opt-out, the models and where they run, commercial use of generated images, stock licences and indemnity.
0 — The terms state that customer files train the vendor’s models with no opt-out, or that generated output may not be used commercially.
3 — AI features described on an AI or help page with a general statement on responsible use or data handling; training on customer files, admin controls and output rights are basic or not described.
5 — A statement on whether customer content trains the models (excluded, or with a documented opt-out), AI features that an admin can switch off for the organisation, and commercial use of generated output addressed in the terms or AI page.
8 — Training excluded by default for business plans, model providers and the processing location of AI features stated, generated content labelled or carrying content credentials, stock and template licences stated per asset type, and an IP indemnity for generated output on a named plan.
10 — AI is governed in writing: a per-feature list of models, providers and locations, admin controls per team and feature, a log of AI use, training exclusion and output ownership in the contract terms, and indemnity and licence limits published in full.
The Product Designer
The security page states plainly that nothing goes to an AI provider unless you opt in, and that if you do, your content isn't used to train models — a default-off posture that goes further than a documented opt-out and covers the admin-control question by making AI opt-in in the first place. The captured pages give no information on the AI provider or where its processing happens, commercial-use rights over generated output, content labelling, or indemnity, so I cannot place this higher. 2
The Frontend Engineer
The security page is direct: nothing goes to an AI provider unless you opt in, and if you do, your content is not used to train models — default-off with training excluded is exactly the statement I want in writing. The AI feature itself is opt-in and the MCP server keeps token checking inside your own coding agent. The pages give no model names, providers or processing locations for the AI features, and say nothing about commercial use of output or indemnity. 2 3
The Brand Marketer
The security page states that nothing goes to an AI provider unless you opt in and that opted-in content is not used to train models — a clear default-off, no-training position I can take to legal. What I still cannot answer is my trade-fair stand question: we found no public information on which models or providers are involved or where they process, on commercial-use rights for generated output, or on any indemnity. 2
The Agency Owner
The security page states that nothing goes to an AI provider unless you opt in, and that opted-in content is not used to train models — an opt-in model with training excluded. We found no public information on which models or providers run the AI features, where they process, admin controls per organisation, commercial-use rights on output, or any indemnity. 2
The Data Protection Officer
The security page states that nothing goes to an AI provider unless the customer opts in and that opted-in content is not used to train models, which is the default-off posture I want to see in writing. The AI provider and its processing location are not named, we found no public information on an organisation-level admin switch or a log of AI use, and commercial use of generated output is not addressed on the captured pages. 2
The Skeptic
One clean sentence on the security page: nothing goes to an AI provider unless you opt in, and if you do, your content isn't used to train models — default-off plus a training exclusion is the statement I read for. For everything else I read for — the model and provider behind the feature, where AI processing runs, commercial-use rights to generated output, and any indemnity — we found no public information. 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity is, where design files, brand assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline.
0 — Proven non-EU on every dimension the evidence covers: non-EU contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven: an EU contracting entity or EU representative, EU data residency (even if only on an enterprise plan), or a published DPA, with the rest of the chain unstated.
5 — EU hosting stated for files as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (AI, rendering, support) is unstated or partly non-EU.
8 — EU contracting entity, files, assets and backups stored in the EU on named infrastructure, subprocessor list published with locations and purposes, and the processing location of AI features stated.
10 — Sovereign end to end and evidenced: European ownership, EU entity, every hosting, AI and support subprocessor European or optional, self-hosting or a European cloud offered, and certifications published.
The Product Designer
Hosting is concrete and European: AWS in Ireland with tested failover in Germany, AES-256 at rest and TLS 1.2+ in transit, with SOC 2 Type II, ISO 27001 and GDPR compliance published and re-audited every year. But the contracting entity's jurisdiction, a DPA, and any subprocessor list are unknown from the captured pages, and the optional AI feature can send content to a provider whose location those pages do not state. Solid EU storage on named infrastructure, with the rest of the chain unproven. 2
The Frontend Engineer
The security page states hosting on AWS in Ireland with tested failover in Germany, AES-256 at rest and TLS 1.2+ in transit, alongside SOC 2 Type II, ISO 27001 certification and GDPR compliance, with annual re-audit and yearly third-party penetration testing whose results are shared. The captured pages give no contracting entity or jurisdiction, no DPA, and no subprocessor list, and the location of the opt-in AI provider is left unstated — so the chain is proven only at the hosting link, which is why this sits low despite the clean EU residency statement. 2
The Brand Marketer
Hosting is documented as AWS in Ireland with tested failover in Germany, behind SOC 2 Type II, ISO 27001 and GDPR compliance with annual re-audits and third-party penetration tests whose results are shared. We found no public information on the contracting entity's jurisdiction, a DPA, the subprocessor list or the location of the optional AI provider, so the chain stops short of a fully evidenced European setup. 2
The Agency Owner
Hosting is stated as AWS in Ireland with tested failover in Germany, alongside GDPR compliance claims and SOC 2 Type II and ISO 27001 certification with annual re-audits and shared pen-test results. The contracting entity's jurisdiction and a data processing agreement are not evidenced on the captured pages, and the optional AI feature can send content to a provider whose location is not stated. 2
The Data Protection Officer
Hosting is documented on named infrastructure, AWS in Ireland with tested failover in Germany, alongside SOC 2 Type II, ISO 27001 and GDPR compliance and annual third-party penetration testing. We found no public information on the contracting entity's jurisdiction, a DPA, a subprocessor list, or self-hosting options, and the optional AI feature can send content to a provider whose location is not stated, so the chain beyond the AWS hosting is unproven. 2
The Skeptic
The security page states hosting on AWS in Ireland with tested failover in Germany, AES-256 at rest and TLS 1.2+ in transit, backed by SOC 2 Type II, ISO 27001 and GDPR compliance, which puts EU residency forward as standard rather than an enterprise extra. That single page carries the whole case: the contracting entity's jurisdiction, a published DPA and any subprocessor list are unknown from the captured pages, and the optional AI feature can send content to a provider whose location is not stated — I will not go higher on a marketing line alone. 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual cost for their team from public pages alone — which seat types exist and what each may do, how viewers and guests are billed, how seats are added and trued up, AI credits, and the plan where SSO, admin controls and brand features begin.
0 — No public prices at all; every plan is a sales conversation.
3 — A public "from" price or one priced plan, per seat or flat.
5 — Per-seat prices public for the main plans with the billing period stated and the main features per plan listed.
8 — Every plan and seat type priced, free viewers and guests stated with their limits, how and when added seats are billed explained, AI credits and storage priced or included explicitly, the plan that unlocks SSO and admin controls named, and VAT treatment stated.
10 — Complete cost computability: annual cost derivable for a given mix of editors, viewers and guests, true-up and auto-upgrade rules published, every add-on priced publicly, and contract term, renewal and downgrade conditions stated.
The Product Designer
The captured pages show a free starting tier — the token manager is even available on the free plan — and name Enterprise plans as the home of the API, but no price figures, seat types, billing periods or per-plan feature tables appear on any page we read. A buyer cannot compute an annual cost for their team from these pages alone, and no public price for any paid plan appears on them. 3 4 9
The Frontend Engineer
The captured pages give no figures for any paid plan — just a Start for free option, with the token manager available on the free plan and the API reserved for Enterprise plans. There is nothing public here from which a buyer could compute an annual cost for a team, and the plan where SSO and admin controls begin is never named. 3 4 9
The Brand Marketer
The only public pricing information I found is that you can start for free, that the token manager sits on the free plan, and that the API is restricted to Enterprise plans. No paid plan carries a public price, and we found no public information on seat types, billing period, viewer or guest billing, VAT treatment, or which plan unlocks SSO and admin controls — so I cannot compute an annual cost for my twelve offices from public pages. 3 4 9
The Agency Owner
The captured pages show a free way to start with the token manager included, and reference an Enterprise plan for the API. We found no public per-seat prices, billing periods or seat-type billing on these pages, so I cannot compute an annual cost for my fifteen people from what was captured. 3 4 9
The Data Protection Officer
The captured pages show a free tier that includes the token manager and note that the API is available on Enterprise plans only, but no price figure for any paid plan appears. We found no public information on seat types, viewer or guest billing, how added seats are billed, AI credits, or VAT treatment, so a buyer cannot compute an annual cost from these pages. 3 7 9
The Skeptic
Beyond a 'Start for free' call to action and a note that the token manager is available on the free plan, the only pricing signal on the captured pages is that the API is 'Enterprise plans only' — we found no public prices, seat types, billing periods or VAT treatment, and nothing on whether reviewers or viewers are billed. A buyer cannot compute any annual cost from these pages. 3 4 9
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?Statement appears in marketing copy on the security page, and the optional AI feature can send content to an AI provider whose location is not stated. |
4/4 pts | 2 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Zeroheight
Is Zeroheight European?
Not determined: the vendor’s pages as captured do not say where Zeroheight is based.
Where does Zeroheight store data?
Zeroheight stores customer data in the EU, per the vendor’s page captured 17 Nov 2026.
Does Zeroheight have a free plan?
Yes. Zeroheight has a free plan, per the vendor’s page captured 17 Nov 2026.
What are the best alternatives to Zeroheight?
As of 19 Nov 2026, the panel rates Penpot (3/5), Sketch (3/5) and Frontify (3/5) highest among the other 27 Design products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Penpot (EU-Made, Spain). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Zeroheight alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. Statement appears in marketing copy on the security page, and the optional AI feature can send content to an AI provider whose location is not stated.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 21 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page zeroheight.com Checked 17 Nov 2026 Details →
- 2 Security / trust page — found from the homepage zeroheight.com Checked 17 Nov 2026 Details →
- 3 Design, prototyping & design systems — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →
- 4 Design, prototyping & design systems — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →
- 5 Collaboration, review & developer handoff — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →
- 6 Collaboration, review & developer handoff — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →
- 7 Brand assets & governance — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →
- 8 Brand assets & governance — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →
- 9 Files, formats & portability — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →
- 10 Files, formats & portability — found from sitemap zeroheight.com Checked 17 Nov 2026 Details →