The components are free. The applications are Pro.
Every component and every block that has ever shipped free stays free, under MIT. Pro is the catalogue of whole application surfaces built on top of them, and Teams is for organisations that want a registry of their own.
Free
$0
MIT, forever
The whole component library, the blocks it started with, and every tool around them.
- 184 components, installed as source you own
- 47 blocks: auth, dashboard, analytics, billing, settings, AI chat, agent console and more
- The CLI, thirteen themes and the Theme Studio
- Agent docs, an MCP server, llms.txt and create-dowel-app
- Per-component quality scores and the accessibility notes behind them
Questions? thefullstackbuilder@gmail.com
Pro
Pro$79
per developer, per year
Whole application surfaces — a CRM, a command center, an AI workspace, an admin console — installed with the same command.
- Admin dashboard: An administration console
- AI workspace: A whole AI application surface
- Command center: Operations at a glance
- CRM: A sales pipeline
- Everything added to the Pro catalogue while the licence is active
- One key for the CLI and for CI, checked against the registry when you paste it
- What you install is yours: the files never expire, only the ability to install and update
Pro is opening soon. The previews are live now — see the blocks.
Teams & Enterprise
Talk to us
for organisations
Your own components, installed the same way as ours, by everyone in the organisation.
- A registry of your own, today: build one with @dowel-ui/registry and host it anywhere
- One URL that serves your components and everything upstream
- Pro licences for every developer in one agreement
- Planned: a hosted private registry, organisation-wide licences, SSO, and version governance across products
thefullstackbuilder@gmail.com, or read how a private registry works.
Questions
- Will something I use today stop being free?
- No. Free is a promise the build enforces: an item that has ever been installable without a licence is named in a test that fails the release if its access changes. Pro is only ever new things.
- What does the licence key actually do?
- It lets the CLI fetch the source of a Pro block.
dowel loginchecks the key against the registry before storing it, so a bad key fails when you paste it rather than during an install a week later. The key lives in your own config directory, never in the project; CI setsDOWEL_TOKENfrom its secrets store. - What happens when it lapses?
- Nothing, to your code. Every file the CLI wrote is in your repository and stays there. What stops is installing Pro blocks into new projects and pulling their updates.
- Can I see a Pro block before paying?
- The preview on every Pro block’s page is the real component, rendered from the same story the tests run, with every one of its states. Only the source is withheld.
- We want our own components in the registry.
- That works today, free, and does not need a licence:
@dowel-ui/registrybuilds a registry from your files, extends ours, and the CLI installs from it with--registry. Teams is for organisations that would rather we host it.