Version control for design
Your design and your product,
always in sync
Capture what you shipped, or start blank. Change it on a branch, verify it against the live product, and merge when it ships.
Free for a month · No card · Or start blank
Northwind
/
Web
new-checkout
from main · v0.4.2
Your design file is not your product
Mockups drift from what ships. Babul starts from the live product, so the design and the code stay one thing.
- Redrawn by hand from screenshots
- "final-v3-really-final" instead of versions
- Nobody knows what changed, or who approved it
- Developers guess the spacing and the states
- Captured from the live site in minutes
- Branches, commits and versions like v0.5.0
- Every change reviewed and merged by name
- Code, tokens and an MCP server for developers
Your whole product, in five layers
One capture fills all five. Edit any of them; a change in one shows everywhere it is used.
From a URL, or from screenshots turned into HTML and CSS.
Every page and the real links between them.
Web, tablet and mobile, as one design or three.
Each with its variants and states, side by side.
Colours, type, spacing, radius and icons as tokens.
Four steps, like git
Main is always what you approved. Everything else happens on a branch.
From a URL or screenshots. Babul reads pages, components and styles.
Edit by hand or with AI, review, and commit with a message.
A match score per page shows what really shipped.
Main gets a new version: patch, minor or major.
AI, CLI and MCP built in
Change the design by asking. Take it into your code and your coding agents.
AI in the editor
Select anything and ask. The change lands on your branch, ready to review.
CLI
Pull tokens, icons and components into your repo, in your stack.
MCP server
Claude Code, Cursor and Codex read main and build to it.
Know what you shipped
Every capture scores the live product and lists what to fix first.
- Colours and type that are off your system
- Components missing a state or a variant
- Contrast and accessibility problems
- Drift between the live site and main
Set up in three steps
Name your company
Filled in from your email. No card.
Describe your product
A URL, images or blank, and the sizes your site supports.
Capture
Add a test sign-in for private pages, then go.
Pay for editors. Viewers are free.
Start with a free month. No card.
See Babul work on your own product.
Start free- 1 product, up to 3 editors
- Capture up to 25 pages
- 2 open branches, merge and versions
- Analysis scores
- 25 image conversions, 10 AI edits
- CLI and MCP
$19 billed monthly.
Start free, then Team- Unlimited products and branches
- Automatic capture, up to 500 pages
- AI: 50 actions per editor a month
- Full Analysis with ranked fixes
- Verify against the live site
For large teams and many products.
Talk to us- Everything in Team
- Custom page and AI limits
- Verify against any URL
Extra AI actions on Team: $0.10 each. Compare plans →
Questions
Do I need to install anything on my site?
No. Babul only needs a URL. Pages behind a sign-in use a test account you give it.
Does it replace Figma?
For the product you already ship, yes: you edit the real pages, not a copy. You can import a Figma file to start.
What does a version mean?
Each merge to main makes one. You pick patch, minor or major, like code.
Who counts as an editor?
Anyone who can edit or merge. People who only view and comment are free.
What happens after the free month?
Move to Team, or keep everything read-only for free. Nothing is deleted. You never enter a card until you choose Team.
Put your design under version control
Paste a URL. See your product in Babul in minutes.