◆
Publish & install in pnpm
Every component is a versioned package with its own API, tests, and docs — published and installed natively in pnpm, 7–10× faster.
Made with HopeThis entire site was created by Hope ✨
◆For developers · ship 10× faster→
Build with components.
Not from scratch.
Compose apps from versioned, tested components — published and installed natively in pnpm. Change one thing, ripple it everywhere. Let AI build on the context you’ve already created.
zsh — bit
$ bit create react ui/pricing-card
✔ created ui/pricing-card · tests + docs scaffolded
# MCP is auto-configured — your agent already sees the graph
✦claude › compose a pricing page from ui/pricing-card
✔ 5 components reused · 0 written from scratch
$
Why developers choose Bit
Less boilerplate. More shipping.
✦
AI that knows your code, over MCP
Connect any agent — Claude Code, Codex, Gemini — to your graph through Cloud MCP. They read your real APIs, docs, and dependencies, and build on what exists instead of guessing.
↗
Ship independently
Components version and deploy on their own. Teams move in parallel without stepping on each other.
◉
Type-safe by default
Full TypeScript across boundaries. Imports resolve to real types, so refactors stay safe at scale.
⚡
Change once, ripple everywhere
Update a component and Ripple CI rebuilds every dependent automatically. No more hunting down consumers by hand.
◇
Test in isolation
Every component runs its own tests and compositions. Catch breaks before they reach an app.
Native in pnpm
No new CLI to learn. It’s just pnpm.
Publish and install your components as packages with the commands you already use. Because the registry knows your dependency graph, installs resolve 7–10× faster — and you can publish a whole monorepo in one command.
Explore the registry→pnpm
$pnpm add @your-org/ui.button
7–10× faster installs
$pnpm publish --batch -r
every package in the monorepo, at once
$pnpm update @your-org/ui.*
the registry knows the graph
The loop
Three commands. The whole workflow.
~/acme — bit · zsh
RIPPLING$bit create react ui/button
✓ created ui/button — tests, docs, compositions
$bit install @acme/design.ui.card
✓ added @acme/design.ui.card to graph
$bit snap && bit export
✓ snapped 1 · rippling 12 dependents…
RIPPLE CI● live
L0✓ui/button0:06
L1✓ui/card0:09
L2↻sections/hero0:14
L2↻sections/pricing0:14
L3·pages/home—
01
Create
Scaffold a component with tests, docs, and compositions from a template.
02
Compose
Pull in any component as a package and build on top of it.
03
Ship
Version and publish. Ripple CI rebuilds every dependent automatically.
Cloud MCP
Plug your agents into your component graph.
The Bit Cloud MCP server gives any AI coding agent live access to your components — so it builds on what your team already shipped instead of starting from scratch.
Claude Code
Codex
Gemini CLI$ claude mcp add --transport http bit-cloud https://mcp.bit.cloud/mcp
⌕
Search the org
Agents find existing components across every scope before writing a line — no duplicate work.
◳
Read real APIs
Full component context — props, types, docs, and dependencies — streamed straight into the model.
⚙
Build & ship
Create components, wire dependencies, and export to Bit Cloud directly from the agent session.
Start Creating
Stop rewriting.
Start composing.
Free for personal use. No credit card. Your first component in 60 seconds.