Simple pricing.
Start free, scale when you're ready.

If the design system is used in a product or service that generates revenue, that's commercial use. Personal projects, portfolios, learning, and open source are all fine on the free plan.

We want anyone working on non-commercial projects to have access to a proper design system, not a crippled demo. The free tier is limited in scope to keep it sustainable, and we reserve the right to modify or discontinue it, but our goal is to keep it available for as long as we can.

Individual and Studio pricing is designed to be accessible for freelancers and small teams. Enterprise is where the platform delivers the most value, potentially saving companies hundreds of thousands of euros a year in design-development coordination. Pricing is based on the value delivered rather than a fixed rate, and depends on company size, the number of designers and developers consuming the output, CDN usage, and the level of support required.

Your projects become read-only and your data is retained for 90 days. During that window you can export everything or reactivate your subscription. After 90 days, your data may be permanently deleted.

Beta pricing is locked in for as long as your subscription stays active. If you cancel and resubscribe later, you'll be on the standard rate at that time.

Yes. You can upgrade or downgrade at any time. When upgrading, you're charged the prorated difference for the remainder of your billing cycle. When downgrading, the change takes effect at the start of your next billing cycle.

We offer a free Studio license to verified non-profit organisations. Get in touch with proof of your non-profit status and we'll set you up.

Yes. Everything the platform generates for you, including code, tokens, and components, is yours. On paid plans you have full commercial ownership of all output.

Studio is gated on total company headcount, not the number of people actively using the platform. If your company employs more than 25 people in total, you need the Enterprise plan. This keeps Studio pricing accessible for small teams and freelancers, while larger organisations, where the platform delivers the most value, move to Enterprise. For agencies the headcount that counts is whoever owns the license. If a 20-person agency buys a Studio license to build design systems for its clients, that agency qualifies as Studio even when delivering a system to a 500-person client. But if that 500-person client buys the license directly, so their own employees have accounts in the platform, the client's headcount applies and they need Enterprise.

No, but it helps. We designed the platform with two tracks: a fast, guided flow that makes it easy to pull off a solid design system with minimal expertise, and an advanced mode for experienced users who want granular control over every token and relationship. You can start simple and go deeper as you learn.

Currently we support React for web and React Native for mobile. As long as your web platform uses React or your mobile app uses React Native, you can use Zaklad to generate and sync your design system directly into your codebase.

Figma is the primary design integration and where the platform delivers the most value. However, if your team doesn't have a design department, you can skip Figma entirely and use just the developer output: tokens and components delivered via NPM. There are no plans to support other design tools at this time.

Technically no, but you'll be limited. Zaklad uses Figma modes for light/dark themes and responsive sizing tiers, which adds up to around 7 modes. Figma's free plan only supports 1 mode, so you'd lose theming and responsive design tokens in Figma (development output still works). The Professional plan supports up to 10 modes which covers most setups. Organisation (20) and Enterprise (unlimited) give plenty of room for additional themes.

Yes. We support DTCG JSON imports, so if your current tooling exports to the DTCG standard you can bring your tokens in directly. Depending on the complexity of your existing structure, you may need to import files separately and do some manual adjustments to map things to our schema. It's not a one-click migration, but it's a lot faster than starting over. Additional import formats are on the roadmap.

Absolutely. Any part of the platform registry can be omitted. If you want to design your own components but use Zaklad for tokens, typography, and icons, that works. Or any other combination. You're not locked into using everything.

This is on the roadmap but hasn't been released yet. When available, you'll be able to bring your own components into the platform alongside generated ones.

Yes. We review every request individually and decide whether it's something we'll add. We want to keep the platform focused and easy to use, not overengineered, but we also want to empower advanced users. If a request aligns with that philosophy, it'll make the roadmap.

Report bugs directly through the platform or via email. During the beta phase we're actively prioritising bug fixes, aiming to resolve issues within 48 working hours. Some complex issues may take longer, but we'll keep you updated on progress.

Yes. Your project data is private by default. We can't see inside your projects and we don't access them. We collect minimal personal data (your account information and basic analytics), we don't sell or share any data with third parties, and you can export or delete your data at any time. We don't use tracking cookies or invasive analytics.

Not currently. The platform is designed around the Figma plugin and NPM package workflow, which covers most use cases. An API for CI/CD integration and automation is something we're open to exploring post-beta based on demand.

Through a Figma plugin that acts as a two-way bridge. Everything you configure in Zaklad syncs directly into your Figma file, keeping design tokens, typography, and components in lockstep with development.

As versioned NPM packages, published as part of synced releases. Fully typed, tree-shakable, with clear namespacing and self-documenting APIs. What developers consume is a 1:1 match with what designers see in Figma.

Releases follow semantic versioning. When you publish a change, design and development release simultaneously at the same version number. If a designer is working with v2.1.0, the developer's NPM package is guaranteed to match. No more "this component exists in design but not in code." Paid plans retain your full version history.

Every generated Figma component includes Code Connect, so when a developer inspects it they see the exact import and usage for the matching component in code. If they're using AI tools to build pages from Figma designs, those tools automatically know how to use the correct components from your library. Design, code, and tooling all reference the same source of truth.

Coming soon. Documentation will be automatic, interactive, and cross-discipline: designers and developers referring to the same docs, not separate specs that drift apart, generated from your design system and staying in sync as it evolves.

On Individual and above, yes. Upload your TTF/OTF files and we host them on a global CDN. Free plan users can still upload fonts for use in the editor, but without CDN hosting.

No, the CDN is optional on paid plans. But you should still upload your fonts to the platform so what you see in the editor matches what ships in production.

Yes. Export everything as a .zaklad archive or DTCG JSON at any time. Your tokens are always portable, no lock-in to our format.