Cloudflare Emdash vs Claude Code + CDN

Head-to-Head Comparison

Feature	Cloudflare (Emdash)	Claude Code + Bunny/Netlify
Setup Time	Hours	Minutes
Monthly Cost	$5-20+/mo at scale	$0-1/mo
Dependencies	TypeScript, Astro, D1, Workers	None. Just HTML files
Build Step Required	Yes (Astro compiles)	No. Output IS final
Vendor Lock-in	High (Cloudflare ecosystem)	None. Files work anywhere
Multi-Editor Admin Panel	Yes, built in	Single operator
Team Collaboration	Great for teams of 5+	Built for one operator
AI-Native Workflow	MCP server (AI → CMS)	AI writes pages directly
Speed to First Page Live	30-60 min	5 min
Database Required	Yes (D1/SQLite)	No
Dynamic Content (auth, search)	Yes, native	Static only
Page Performance (TTFB)	Fast (edge Workers)	Fastest (zero processing)
Uptime / Reliability	Workers + D1 dependency	Near 100% (static CDN)
Security Surface	DB, API, auth, plugins	Near zero (no backend)
Portability / Migration	Content locked in database	Drag folder to any host
Content at Scale (1000+ pages)	Database queries	Proven (1,500+ live)
Plugin Ecosystem	New, growing	N/A (build what you need)
Maintenance / Updates	CMS, plugins, DB patches	Nothing to maintain
Learning Curve	Steep (Astro, Workers, D1)	None (you talk, I build)
Framework Overhead	TypeScript + Astro runtime	Zero
Content Backup	Database exports	Files on disk + GitHub
Offline Access to Content	No (needs D1)	Yes (local folder)
Custom SEO Control	Template-level	Per-page, total control
Long-term Viability	Depends on Cloudflare	HTML works forever

Final Score

5 Cloudflare Emdash

19 Claude Code + CDN

Cloudflare wins only where you need multiple human editors, dynamic features, or a traditional CMS admin panel. For a solo operator building static sites at scale with AI, it's not even close.

Emdash (Cloudflare) Pros & Cons

Pros

Modern stack (TypeScript, Astro 6, serverless)
Built-in admin panel for teams of editors
Native MCP server for AI agent integration
Sandboxed plugin security model
Structured JSON content, queryable via API
Dynamic content capabilities (auth, search)
Open source with community potential
Edge-deployed globally via Workers

Cons

Locked into Cloudflare ecosystem (D1, Workers)
Overkill for solo operators
Still requires CMS layer between AI and output
More attack surface (database, API, auth)
Content trapped in D1, harder to migrate
Requires learning Astro theming system
Brand new, uncertain long-term support
Costs scale with requests past free tier

Claude Code + Bunny/Netlify Pros & Cons

Pros

Zero dependencies. Pure HTML/CSS/JS
Files run anywhere: any CDN, any server
Concept to live in minutes, not hours
Bunny ~$1/mo, Netlify free tier
AI IS the builder. No middleware needed
Total per-page SEO control
Near-zero downtime (static files on CDN)
Proven at 1,500+ pages (pmconsulting.ca)
Nothing to update, patch, or secure
HTML works forever

Cons

No admin panel for non-technical editors
Single operator workflow
Requires Claude Code access for every edit
No dynamic features (search, auth, comments)
File management gets complex past 1,000 pages
Adding interactivity requires manual JS
No automated content workflows without scripting

The Bottom Line

Emdash is Cloudflare's play to own the CMS layer. Impressive engineering. The AI-native MCP integration is genuinely forward-thinking. Best fit: teams with multiple editors who need dynamic features and are already in Cloudflare's ecosystem.

Claude Code + CDN skips the middleman entirely. The AI doesn't talk to a CMS that generates pages. The AI IS the page generator. Zero dependencies, near-zero cost, total portability, and proven at 1,500+ pages. Best fit: solo operators who want maximum speed, control, and the lowest possible cost.

For PM Consulting's workflow, Claude Code + Bunny/Netlify wins 19-5.