No. 01
Axolo, the guide
Your companion in the chat
Listens, suggests, and calls the other Axolos when needed.
Tell me what you want, I'll handle the rest.
Private beta · early November
Your real components, rendered with their real props. Your team and its agents iterate on one canvas, and what you keep is already code.
GitHub, GitLab, npmReact · Web ComponentsBring your own Claude
Any team can now generate a screen in thirty seconds. Almost none can ship it.
It comes out with the wrong button, invented spacing, a component your library never had. Designers redraw it. Developers recode it.
Axolo starts from your code. Agents compose with your real components, follow your rules, and stop before they break one.
Your PM, your designer and the agents work on the same canvas. What you keep, your developers already know how to build.
Each agent knows its part of your product and your design system. The guide listens, and calls the others when needed.
Your companion in the chat
Listens, suggests, and calls the other Axolos when needed.
Tell me what you want, I'll handle the rest.
The design system keeper
Colors, typography, components: everything that gives your screens their identity.
One more variable, one less gap.
The journey architect
Journeys, navigation, states: path first, decoration later.
Three clicks is already one too many.
The product compass
Vision, audience, tone: always asks who for and why.
Who for, and why?
The bridge to code
Code, Storybook, pull requests: talks to developers for you.
If it compiles, let's talk.
Import it from GitHub, GitLab, npm or a folder. Review what was detected, enrich it with your own Claude, request the components you're missing as drafts, and publish versions. The code stays the source of truth.
Ask for a returns flow. The agent reads your library, places your Button, your Card, your tokens, and shows every step it takes. It cannot paint a custom div: each change is a typed operation, checked by the server.
Four levels, set per prompt and per branch. Strict only places your components and tokens. Free explores a concept outside the system. The design system admin sets the ceiling, locked rules like accessibility apply at every level, and any gap stays visible.
Your design and product rules live next to your components: one primary action per screen, no modal on mobile, the tone of your error messages. When a prompt contradicts one, the agent stops and asks first.
Each screen is a graph of versions. Branch an idea, let the agent try three directions, compare them side by side and keep one. Your PM, your designer and the agent work on the same graph, live.
Write skills, the step-by-step methods the agent follows instead of improvising: a back-office list, a mobile variant, a handoff. Call them with /, share them across projects, and every screen comes out the way your team builds it.
Kept screens export as code that compiles against your library, in your framework. When the agent needed something your design system doesn't have, it files a component request. Library changes go out as one pull request, reviewed by your developers in GitHub.
Already paying for Claude? Connect it to Axolo through MCP. Your assistant composes with your design system, and Axolo's server checks every screen against your rules. No second AI subscription.
Prototypes versioned in Git.
Read access to your repos, pull requests reviewed by your developers.
Isolated execution.
In Strict mode, nothing outside your library.
ComingEU hosting.
Axolo works with product teams who hand their design system to an AI.
Early November. Join the waitlist and we'll let you know as soon as it's live; during the private beta, we onboard teams one by one.
The design system is at the center of the tool: working on it is the goal, not a side feature. Import it, review what was detected, enrich it through MCP with your own Claude, request new components that go through a draft, and publish versions. Editing components and tokens directly on the canvas is what we're building now.
Yes. Axolo builds your design system with your own build tooling and renders the actual components in an isolated scene, with their real props. Nothing is rewritten into a layer of ours: what you see is your code, and it stays the source of truth.
Import from GitHub, GitLab, a local folder or an npm package; Storybook can be used as a source if you have one. React and Web Components today, Vue and Angular next. Axolo works on a framework-independent model of your screens, so the framework only changes how components are read and rendered.
No. On a real repo, with vendored code, custom CSS setups or a monorepo, the component manifest is built by static analysis and scripts, then a small internal model helps with meaning (default texts, compositions). No external AI is needed for the import, and you can have the design system enriched afterwards.
The agent works from your design system's rules: foundations, locked rules and the level of freedom you allow. Markdown files give agents as much context as possible and the rules to apply. Screens are composed with your components in editable auto layout, every screen is scored by a quality check before it's kept, and each version can be compared with the previous one.
Axolo doesn't need Figma: the code is the source. The component manifest comes from your code, so there's no contract to maintain between a Storybook manifest and a Figma JSON. To get started without a coded library, Axolo can also build a design system from your Figma variables.
For the design system, it lives in your code and is edited in Axolo (tokens, themes, components). Your designers can keep Figma for free exploration.
You start on Axolo UI, a ready-to-use library, or on a design system built from your Figma variables.
Claude, by Anthropic. Use Axolo's built-in agent, with AI included in your plan, or connect your own Claude, Cursor or any MCP client and keep your existing subscription.
Your code stays in your own repos. Prototypes are versioned in a Git repo your developers can clone. Any change to your library goes through a pull request reviewed by your developers.
Only if you allow it. In Strict mode it only places your components; anything missing becomes a request for your developers.
Pricing is shared with the waitlist before launch. During the private beta, it is set with each invited team.