One Admin Design System, Every Framework You Use
Token-driven, accessible components and the admin screens built from them: data tables, record forms, charts, auth and a working back office. Ships as source, so the code is yours the moment you download it.
Prefer to look first? Every component runs in a full working demo app with real datatables, forms, charts, and auth screens.
Set a new milestone
Define a target and we'll help you pace it.
Monthly revenue
$48,120
+12.5%This is not an admin template
It is one design system with an edition per framework. The same tokens, the same markup and the same screens, rendered by React, Vue, Angular, plain HTML or Laravel, because the class strings live in one file that every edition imports rather than in five files that agree for a while.
You know how buying an admin theme usually goes. You pick the framework you use today, you get a folder of screens, and the theme is a fork from the moment you open it. A year later another team needs the same product in another framework, and you buy it a second time and maintain two things that drift. Or you find the theme was built for a demo rather than for your brand, and you spend a fortnight fighting specificity to change a radius.
That is what this is built to avoid, on five principles.
- One source, every edition: The class strings are written once and imported, not copied.
- Tokens, not overrides: Retheme by changing seventeen values, not by fighting the cascade.
- Screens, not just components: A button is easy. A data table with a record workflow is the job.
- Yours as source: No runtime dependency on us. The free editions are MIT.
- Built for coding agents: A rules file your agent reads, and an MCP server it can query.
One source, every edition
A shared module holds the class strings, and React, Vue and Angular import them. Nothing is retyped per framework, so a fix to a button lands in every edition at once and the editions cannot quietly diverge into lookalikes.
This is checked rather than promised. pnpm check:shared-classes fails the build if a class string is written in two editions, or written out at all when a shared constant for it already exists. It exists because prose alone missed the same drift twice and two copies that happen to agree look exactly like one copy.
What is honestly not equal yet: React renders all 78 component families. Vue is at 68, Angular 67 and plain HTML 65, and pnpm check:editions keeps those numbers true rather than aspirational. Any framework says which family is missing where.
Tokens, not overrides
The theme is a contract of seventeen fields: colour, radius, typography, spacing and the four state colours. Change them and every component moves, including the ones you write yourself, because they read the same variables.
The point of that number being small is that it is learnable in a sitting. The point of it being a contract is that a component cannot opt out: a state colour written as a raw palette class is a build failure, which is how success, warning and info stopped being the one colour family a themed product could not theme.
Screens, not just components
A component library hands you a Button and wishes you luck. An admin application is a data table that sorts the whole set rather than the visible page, a record form that knows which fields are required, a settings surface, an inbox, a pipeline, a checkout.
Those are the screens here, built from the same components you get, so what you copy is not a screenshot of a solution. The free editions ship nineteen screens and the Pro editions well over a hundred.
Yours as source
You download a folder and run it. There is no account to keep, no package of ours in your dependency tree at runtime, and no version of ours that can break your build on a Friday.
The free editions are MIT and yours to keep, including in commercial work. Pro is a commercial licence for the paid editions and the record workflow; Free vs Pro is the line between them.
Built for coding agents
Readable code is table stakes; every unminified library has that. What an agent actually needs is the design decisions in a form it can query, and the Pro pack ships them: a rules file at the paths Claude, Cursor and Copilot already read, and an MCP server with seventeen tools.
So your agent can ask which component family answers a requirement, which page pattern a screen should start from, and what the spacing rule is, instead of guessing from the markup and producing a screen that nearly matches.
Who this is for
It is worth being specific, because a product that claims to suit everybody suits nobody.
- You are building an internal tool, a back office or a dashboard, rather than a consumer marketing site.
- Your teams are not on one framework, and you want the same product to look like one product anyway.
- You have to ship your brand's theme, not ours, and you would rather change a token than a stylesheet.
- You build with a coding agent and want the screens it writes to match the ones you bought.
And when it is not
If you need a general-purpose kit for a consumer product, a headless library with no opinions is a better fit. If you want a hosted service that runs your admin for you, this is the opposite of that: it is source you own and host. And if you only ever ship one framework and never intend to retheme, a single-framework template will cost you less.
The CSS framework is an axis, not a rewrite
Today every edition renders Tailwind. Bootstrap and Bulma are next, and they are a binding rather than a fork: the class strings already live behind one shared module, so a second binding is a second set of values for names that already exist, not a second codebase.
That is what makes a Pro edition a combination rather than a product: a shell, a CSS framework and a framework. It is also the honest cost, and worth saying out loud: every binding has to answer for all of the shared constants, which is the largest single item on the roadmap and the reason Bootstrap and Bulma are dated rather than shipped.
Where each framework stands today: React and Next.js are available now. Vue, Angular, plain HTML and Laravel are built and on the waitlist rather than on sale, and Any framework carries the current state of each. We would rather tell you a framework is not ready than sell you one that is not.
Free to start, Pro when you need it
The free edition is MIT, the data table included. Pro adds the record workflow around it, the admin screens and every framework edition.