Your agent never logs into GitHub, Vercel, Cloudflare, or Stripe. Caddi hands it the deploy key, the env var, the staging URL, the API token — at the moment it needs them.
Free up to 3 projects · $99/mo for unlimited + team
How it works
Drop a template. Caddi hands your agent the deploy, the env vars, the domain. Real feedback flows back as pin-on-page comments your agent fixes. Repeat.
Your agent owns it from minute one.
Pick a starter or run caddi link on an existing repo. Caddi connects GitHub, Vercel, and Cloudflare once — server-side — and writes the AGENTS.md your agent reads.
Deploy, env, domain — on demand.
Your agent calls the CLI. Caddi hands it the deploy, the env var, the staging URL, the API token — at the moment it needs them. No tokens in your agent’s context. No dashboards open in another tab.
Pin-on-page comments your agent fixes.
Real visitors click an element on the deployed site and leave a comment. It lands in the same inbox your agent reads via caddi requests list. Caddi Auto can open a PR locally with Claude Code.
What the caddie carries
The CLI, the environments, the inbox — one common interface for you and your agent to drive every project from.
CLI + AGENTS.md
Every Caddi project ships with an AGENTS.md and a caddi.json. Your agent reads them and uses the caddi CLI to deploy, set env vars, attach domains, and act on feedback — without ever touching a provider dashboard.
Three environments
Three branches, three deployments, three sets of env vars per project. Promote with one click — or one CLI command. The managed-host experience your agency had ten years ago, on the modern stack you build on now.
Pinpoints + Caddi Auto
A drop-in widget on your deployed site. Visitors click an element, leave a comment, and a screenshot lands in the same inbox your agent reads via the CLI. Turn on Caddi Auto and Claude Code opens a PR on your machine.
Where your AI-built projects live
Caddi does not replace Vercel or Cloudflare. It replaces the four-to-six dashboards your agent would otherwise need accounts on — and gives you and your agent one place to drive every project from.
If you’re using
World-class hosting. But your agent still needs a token, your env vars live in a dashboard, and there is no project-level forms backend, client portal, or feedback inbox.
What Caddi does instead
Caddi runs the deploy, the env vars, the domains, and the customer portal on top of Vercel. Your agent calls one CLI; the keys stay server-side.
If you’re using
Built for the pre-AI world: a visual editor a human clicks through. If your agent is writing the code, the visual builder is the wrong layer.
What Caddi does instead
Code-first. Whatever your agent writes — Next.js, Astro, plain static — Caddi takes the repo and ships it.
If you’re using
One slice each — forms, in-page feedback, support tickets — in separate dashboards your agent cannot read.
What Caddi does instead
One unified requests inbox: pinpoints, portal tickets, API submissions, all in one place, all available to your agent via the CLI.
If you’re using
The managed home for the last era of the web. Built around a CMS and a page-builder, not a coding agent driving a real repo.
What Caddi does instead
WPEngine for the post-AI-coding era. Where your AI-built projects live — a common interface for humans and agents to manage the same project.
Made for
One caddie for the solo builder shipping their first SaaS, the indie dev with a portfolio of side projects, and the agency running client work. Free for one user; Pro for teams.
Solo builder
Caddi gives your agent a domain, three environments, and a feedback widget so the people you show it to can tell you what is broken.
Indie dev
Link an existing repo or bulk-import a GitHub org. Every project gets the same three environments, the same env-var workflow, the same CLI your agent already knows.
Agency
Each client gets a magic-link login at clients.youragency.com. Pinpoint feedback flows into one inbox; your team — and your agents — work from a shared queue.
Pricing
Monthly billing. Cancel anytime — your projects stay live, your data exports.
Free
A caddie for one — your projects, your agent, your account.
Pro
A caddie for the whole team — agencies, operators, real client work.
Caddi never marks up Anthropic. Caddi Auto runs against your own API key.
Questions
No. Caddi connects to them once via your account; after that, your agent uses the CLI and never sees a token. The keys stay server-side with Caddi.
No. Caddi sits on top of Vercel — your project still deploys to Vercel, on your account. Caddi becomes the place you (and your agent) drive deploys, env vars, domains, and feedback from.
Run `caddi link` in the local repo, or use the Import wizard. Caddi reads your GitHub org, lists every repo with its current Vercel project, and lets you bulk-pick which to manage.
Only two files: AGENTS.md (shipped in every starter, written on `caddi link`) and caddi.json. Claude Code reads AGENTS.md natively. Cursor, Copilot, anything that respects AGENTS.md works.
Yes. Pinpoints — the drop-in widget plus the unified inbox for every request, ticket, and pinpoint — is on Free. Pro adds team, clients, white-label portal, audit log, and approval gates.
Run `caddi listen` on your machine. When a Pinpoint comes in, it spawns Claude Code locally with the request, URL, and screenshot. Claude opens a PR; you review. Caddi never marks up Anthropic — Auto runs on your API key.
Yes. Cancellation takes effect at the end of the current billing period. Your projects keep serving on Vercel, and you can export every byte of Caddi-side data to JSON.
No. Caddi’s architecture is hostile to self-hosting — multi-provider OAuth, R2, a websocket daemon for Caddi Auto, Stripe. Hosted-only by design.
Free up to three projects, every feature included. Pro when you bring on a team or start working with clients.
Get started →No card up front. Free forever for personal projects.
