Cloudflare Startup Program · since May 2026
One operator. 120+ sites. Built on Cloudflare.
An Anthropic Claude Partner and OpenAI TAC-verified firm, running its whole ecosystem on Cloudflare: 120+ sites, one sign-in and wallet across them, an AI engine, MCP servers for agents, a 12-publication media network and our own ad network. Operated by one engineer with Claude Code.
- Anthropic Claude Partner· Official partner
- OpenAI TAC· Verified firm
- 400+ technology suppliers· Risk-to-solution sourcing
- Cloudflare Startup Partner
What runs on it
The whole ecosystem, on one edge.
Everything a visitor, a member or an AI agent touches runs on Cloudflare. That is how one person ships across 120+ sites: shared identity, payments and portal, deployed once and reused everywhere.
Sites and front doors
120+ sites across the ecosystem, this one included: static Astro at the edge, with a Worker in front that serves new pages and passes everything else to the app behind it.
WorkersPagesWAFcustom domains
One account, one wallet
A single sign-in, credits wallet, checkout and member portal shared by every property, so a new site gets accounts and payments on day one.
WorkersD1KVDurable Objects
AI services and agents
The AI engine behind our fixed-price reports, three MCP servers for AI agents, and document uploads sandboxed in their own bucket.
WorkflowsWorkers AIAI GatewayR2
Media and ads
12 security publications (4,747 articles, 1.8M page views a month across 15 zones) and CyberAdX, our own first-party pixel, ad serving and video library across 18 properties.
PagesWorkersD1Analytics Engine
Protection
Access in front of our admin tools, Turnstile on public forms, and the WAF at the edge of every zone: 435,000+ threats stopped before they reached a site, July to September 2026.
AccessTurnstileWAF
Operated with Claude Code
An AI agent at the controls. A person on every change.
We build on Claude, and we run the platform with it too. Claude Code works through scoped Cloudflare API tokens: it deploys Workers, applies D1 migrations, manages R2 and the AI Gateway, reads analytics, and helps tune WAF and Access rules.
That's how 10 production sites moved from Pages to Workers in a day, and how one engineer runs security for a 117-asset estate.
The guardrails
- Scoped API tokens, one job each. When our own scanning turned up an over-scoped token, every consumer moved to least-privilege keys the same day.
- A person owns every production change. The agent builds, tests and proposes; deploys, migrations and DNS changes wait for an explicit go.
- Migrations before code, verified live before the old thing is removed: the same rule we used moving 10 sites from Pages to Workers.
- Separate secrets per service, and the payment, identity and admin paths behind their own checks.
Case studies
The long version, in our own words.
Our ad network exists because we got banned. After a bot farm inflated our traffic, an ad network closed our account, payouts elsewhere were opaque, and a video partner dropped us. So we built our own, all on Workers.
CyberAdX ↗Live network stats ↗The catalogue: 12 publications ↗Video library ↗
Infrastructure
- Accepted into the Cloudflare Startup Program From Ghost on Netlify, through a bot-farm attack and an ad-network ban, to an ecosystem running on Workers, D1, Analytics Engine and Workers AI.
- 10 production sites from Pages to Workers in a day, with Claude Code One reference build, cloned across nine more, each verified live before its old project was deleted.
- Securing a 117-asset edge estate with one operator Discover, scan, validate, remediate, deploy and self-heal across 100+ repositories: our DevSecOps pillar, proven on our own estate first.
Media and ads
- 11 Astro sites, one ad stack How the blogs share one ad integration, one analytics pipeline and one deployment path, after 4,500+ articles moved off Ghost with every URL preserved.
- How we built CyberAdX A first-party pixel with signed clicks, a D1 event store and Analytics Engine, built after an ad network banned us over bot traffic we didn't send.
Agents and payments
- Rebuilding the marketplace for agent buyers One identity and one wallet across the ecosystem, MCP and API access, and the Cloudflare primitives at the agent boundary.
- Your agents now have wallets Cloudflare Wallets, Stripe and x402, and the controls that keep prompt injection from becoming a payment.
Work with us
We'll build yours the way we built ours.
Cloudflare team: we're glad to go deeper for a customer story. Get in touch.