carbn is the first tool that didn't try to clone our site. It read it. The traversal output matched our component tree, not a screenshot.
Inspect the architecture.Extract the component.
A headless traversal engine for the open web. carbn.sh maps, componentizes, and ships production-ready blocks to your codebase — or your agent.
Framework-agnostic output across React, Vue, Svelte, Solid, Astro, and more.
Transpiles to every surface you ship on
- React
- Next.js
- Vue
- Svelte
- Solid
- Astro
- Remix
- Tailwind
- HTML5
- CSS3
- Framer Motion
- GSAP
- Qwik
- Preact
- Vite
- TypeScript
Six primitives. One deterministic engine.
Every carbn surface decomposes into markup, styles, logic, and dependencies. The engine is headless; the output is framework-agnostic; the contract is your codebase.
Headless Traversal Engine
Crawl, classify, and resolve any surface into a labelled primitive tree. Deterministic selectors. No hallucination.
Hybrid Animation Engine
Capture motion behavior and transpile to Framer Motion, GSAP, or pure CSS. Spring physics preserved.
The Playground
Paste a URL. Inspect live. Scrub the timeline. Export the block — nothing leaves your browser.
Clean Code Inspector
Four tabs. Markup, styles, logic, dependencies. Everything carbn resolved, laid bare.
Local CLI
Drop components straight into your tree. Type-safe. Idempotent. Reversible.
Bi-Directional MCP
Agent-native from v0.1. Read from the public library. Write to your private namespace. Token-metered.
From URL to pull request.
Four deterministic phases. No intermediate steps. No manual reconciliation.
Input any URL
Hand carbn the surface you admire. Public-facing site, staging URL, or local dev server — the traversal engine accepts all three.
Built by people who had to ship it first.
No paid placements. No stock photography. Only the engineers who invoked the engine before we opened it up.
The MCP surface replaced three tools in our agent pipeline. Extraction is deterministic and write-back lands where we expect.
I scrub the Playground timeline while I'm on a call and ship the resulting block before the call ends. That is the loop.
No screenshot OCR. No hallucinated Tailwind. The inspector reads structure the way we review pull requests.
A capable solo developer is now genuinely faster than a small frontend team. carbn made that true for me in a weekend.
Our coding agent consumes the MCP directly. Read → write is one roundtrip. We stopped wrapping the CLI.
The load-bearing details.
Built for practitioners and their agents.
Transparent tiers. No seats for non-contributors. Agent pricing is metered by extraction, not by fiction.
Individual developers
- Playground access
- 50 extractions / month
- Local CLI
- Community library
- MCP read access
- Local-only history
Technical teams
- Unlimited extractions
- Private library
- Shared component namespace
- Priority engine queue
- Org-scoped MCP tokens
- GitHub integration
- Audit log (90 days)
Autonomous systems
- Bi-directional MCP
- Token-metered extraction
- Write-back to private library
- SLA-backed engine
- Dedicated region routing
- Programmatic provisioning
- Usage-level attestation
SOC 2 Type II · GDPR-compliant extraction · BYO region
Extract your first component.
One command. Your terminal. Your repo. Nothing proprietary in between.