cdbx.ai
Plan. Build. Ship.
The AI-native development environment where you plan, build, and ship with AI by your side. You decide. cdbx executes.
The story so far
Where we started. Where we are. Where we're going.
A real IDE. In your browser.
cdbx is built on the belief that you should be able to start building immediately, on a solid foundation. The full IDE — Monaco editor, 20+ languages, live preview, streaming terminal — instantly available from any browser.
AI-native. Context-aware. Connected.
The IDE got smarter — and gained a planning surface. Not just autocomplete: the AI reads your files, fixes errors, iterates your UI, connects to your services, and now helps you think and plan before you write a line of code.
The orchestrator at the center of your workflow.
In the next phase, cdbx sits at the center of the modern AI workflow — not just a tool in your stack, but the hub your entire stack connects to. cdbx calls GitHub to ship your code. Claude, ChatGPT, or Grok calls cdbx to build an app. Every direction flows through one place.
Four stages. One workflow.
Every phase of development, connected.
Each stage feeds the next. The Planning Agent's output becomes the Build Agent's input. The Build Agent's output triggers Ship. Once it's live, Agents keep working on your behalf. No copy-paste. No context switching.
Plan with your actual context.
The Planning Agent is a product strategist, architect, and UX designer you can think out loud with. Pick a plan type — General, Architecture, Research, Slides, or API Spec — and the agent reads your Notion docs, GitHub issues, and Linear backlog to give advice grounded in your real situation.
Connectors
Produces
Pushes back to Notion, GitHub, and Linear automatically.
Build with full context.
The Editor AI reads your PRD, queries your live database schema, knows your design system, and generates code that actually fits. Self-Healing fixes errors. Visual Loop iterates the UI. You steer; the agents execute.
Connectors
Produces
Reads planning artifacts from Notion automatically.
Ship without the handoff.
When the code is ready, connectors handle delivery. Open a PR, trigger a deploy, post to Slack, close the ticket — all from the same conversation that built the feature. The finish line is not a preview URL. It is production.
Connectors
Produces
Reads build output; notifies your team on completion.
Agents that keep working after you ship.
Agents act on your behalf across whatever services you connect — check a backlog, post an update, triage an inbox — on demand or on a schedule, with an approval step before anything risky. One Agent can also be bound to an App you have shipped, so it works on that app directly. Workflows (fixed, deterministic recipes) are next.
Connectors
Produces
Agents are in early access today. Workflows are on the roadmap.
The pipeline
No copy-paste. No context switching. Every handoff is automatic.
The bigger picture
cdbx doesn't just connect to the ecosystem. The ecosystem connects to cdbx.
Today, cdbx calls out to your services — Notion, GitHub, Google Drive. Tomorrow, other AI tools call in to cdbx. Claude, ChatGPT, or Grok can build an app here. A CI pipeline can push code here. An external agent designing a product can hand it to cdbx to build and get back a live preview URL.
The relationship is the same as cdbx calling GitHub to open a PR — just reversed. cdbx becomes a composable “build and preview” capability that any AI workflow can invoke. Not just a standalone product. Infrastructure for the agentic web.
What makes us different
Built different. On purpose.
Your AI knows your services
Other tools give you generic AI. cdbx gives you AI that has read your Notion pages, your database schema, your GitHub repos. The difference is code that fits from the first line.
AI that acts, not just responds
cdbx agents loop, observe, and self-correct. The Self-Healing Agent fixes errors without you clicking anything. The Visual Loop iterates until the UI matches the goal. Agents do the work; you review the result.
It builds in your design language
Give cdbx your design system — a built-in like Material 3 or Carbon, your Figma tokens, your own component library over MCP — and the AI builds against it. Colours come out as your tokens, not pasted hex codes, and every change is checked against the system afterwards. Switch systems and the whole app follows.
Run code from anywhere
The cdbx Code Execution API executes code in a secure sandbox via a single POST request — no infrastructure needed. 30 languages, IP rate-limited, per-user quotas. Designed for agents, scripts, and CI pipelines alike.
Part of a bigger ecosystem
cdbx connects outward to your tools and inward from other AI. Claude, ChatGPT, or Grok can call cdbx to build an app. Your planning session flows into your build session. Nothing lives in a silo.
You own everything
Your code exports to GitHub as a real repo. Your experiments download as ZIP. No vendor lock-in, no proprietary format. BYOK means you use your own Anthropic, OpenAI, Moonshot, or xAI key — no double-paying.
Built by
One person.
One mission.
cdbx is built and maintained by Christopher Butler — from every product decision to every line of code. Built exactly the way it's designed to be used: one person, a clear idea, and AI doing the heavy lifting.
Christopher Butler
Founder
Christopher is a Computer Engineer and Director of Engineering at Aidn, a health tech startup — but first and foremost, a builder. He created cdbx because the most powerful thing you can do is take an idea and make it real. cdbx exists to make that possible for everyone.
Have an idea?
Bring it to life with cdbx.
No setup. No credit card. Get started in seconds.
Questions? Get in touch · Investor page · Documentation