Self-Hosting / Deployment
Version 1.2.0
Carapace runs on your own Cloudflare and GitHub accounts. There's no managed hosting option yet — you deploy your own instance.
What you need
- A GitHub account, for the app repo and the content repo
- A Cloudflare account, for Pages hosting and the supporting Workers
- An MCP client (Claude, or any MCP-compatible tool) to actually write content once it's running
What gets provisioned
Two GitHub repos — app and content — kept deliberately separate so access controls apply cleanly to each. A GitHub App scoped to write access on the content repo only, never the app repo; this is what makes "the connector can't touch site code" a structural fact rather than a policy. Cloudflare Pages for the static build, plus a small set of Workers handling drafts previews, scheduled publishing, image uploads, and the remote MCP server itself.
Every Cloudflare piece here runs on free-tier limits comfortably at blog-to-small-team scale. There's no required paid tier to get a working instance live.
Cost
The software itself is free and open-source, permanently. What you pay is whatever your own Cloudflare and GitHub usage costs — at hobby-to-serious scale, that's $0 on free tiers, with a pay-as-you-grow path if traffic ever gets large enough to need it. There's no re-architecture required to get there; the same setup scales up as-is.
Portability
The published site is plain static output — nothing Cloudflare-specific baked into it — so it stays portable to a different static host later if that's ever useful. The operational features around it (draft previews, scheduling, instant rollback) are deliberately Cloudflare-coupled, since those are exactly the features a CMS vendor would otherwise charge for, and the free tier covers all of them at this scale.