FAQ
Short answers to the questions that come up most. Where something is a direction rather than a shipped feature, it says so.
#Do I own the generated code?
Yes. The generated code is yours - unrestricted, not a derivative work - and export is always available whatever the edition. The paid value is the seamless pipeline (versioned packages, npm install, live updates), not lock-in. Because that pipeline is seamless, ejecting is an escape hatch you rarely reach for rather than a routine step. See Release & registry.
#What frameworks are supported?
React is the shipping code target today - the generator emits self-contained React components plus a shared theme. Figma is supported as a design target (tokens as Figma Variables). Other targets - additional frameworks and native platforms - are on the roadmap. The whole point of the platform-neutral IR is that new targets are added as generators without changing your design system. See Targets.
#Is it open source?
It follows an open-core model. The IR spec and @mildastudio/core, and the React generator, are open - client-side, zero infrastructure, the basis for trust and a standard. The visual editor, hosted registry and collaboration, curated archetypes, and premium generators are the commercial product. The moat is deliberately the editor experience and hosted infrastructure, not the generator.
#How does pricing work?
The value metric is the editor seat: a small number of people design the system, and the whole front-end org consumes it - so Milda charges the maintainers and keeps consumers free and unlimited. There are three tiers: Free (local generation, core and the React target, one design system, curated archetypes, local/public registry only), Team (private registry hosting, collaboration, version history, multiple design systems, design exports), and Enterprise (SSO/SAML, self-hosted registry, audit and governance, premium generators, support). See Editions & pricing.
#Can AI tools use my design system?
Yes - that's what the MCP server is for. Once a system is published, an AI coding agent can discover its components, read their exact contracts, pull tokens, generate real source, and check breaking changes over the Model Context Protocol. The result is code that is on-system by construction: real component names, exact prop types, your tokens instead of hard-coded values.
#How do consumers install a released system?
Consumers don't need Milda. They route only your scope to the registry in .npmrc, then install the package like any dependency - everything else keeps resolving from npmjs:
# .npmrc @your-scope:registry=https://registry.your-company.com
npm install @your-scope/design-system
#What happens if I stop paying?
You keep the code you own - the generated output is unrestricted and export is always available, so nothing you've shipped stops working. What you lose access to is the paid pipeline: the hosted private registry, collaboration, version history, and premium generators. Consumers of an already-published package installed from your own registry are unaffected. See Release & registry and Editions & pricing.