Cloudflare Ecosystem

Cloudflare is the edge-cloud route when work involves Workers, Pages, KV, R2, D1, Queues, Workflows, Workers AI, tunnels, bindings, or edge deployment behavior. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27

When To Use This

Use Cloudflare when the runtime is edge-first or the task names Workers, wrangler, R2, D1, KV, Queues, or cloudflared. Use Vercel for Vercel-hosted Next apps unless Cloudflare is the target runtime. Source: Skill Resolver, 2026-06-27

Decision Matrix

Core Model

Cloudflare combines edge compute, storage, networking, and deployment config. The key safety boundary is account/resource confirmation before writes, because small CLI commands can touch real edge infrastructure. Source: Frontend and Design Skills, 2026-06-27

A 2026 bookmark frames the practical small-product stack as Workers, D1, Better Auth, KV, R2, Queues, Hyperdrive, email routing, WAF, and DDoS protection around a roughly $5/month account floor. An earlier @ibocodes variant states the minimum version more bluntly: many projects can start with Workers + D1 instead of VPS + Postgres or Supabase + Vercel. Treat both as stack-shape evidence: good for edge-first apps and predictable-cost experiments, but not an automatic replacement for Vercel-hosted Next apps. Source: X/@ibocodes, 2026-06-21; Source: X/@ibocodes, 2026-06-28

The follow-up "no reason to use Vercel + Supabase anymore" image is market-sentiment evidence, not migration advice. The reviewed visual crosses out Vercel and Supabase while presenting Cloudflare plus PlanetScale as the alternative app-platform pair. The durable signal is that Cloudflare's Workers/D1/Hyperdrive/runtime story and PlanetScale's relational-data route are being perceived as a coherent replacement stack for some small apps. Keep the route workload-specific: Cloudflare + PlanetScale is strongest when the app wants Workers execution and centralized relational data, while Vercel + Supabase remains reasonable for Vercel-native Next apps or teams already standardized on Supabase. Source: X/@ibocodes and local image review, 2026-07-04

Startup credits

Cloudflare for Startups is a current infrastructure-subsidy route for early-stage technology startups, not a separate runtime. As of 2026-07-04, the program offers one-year credits in three tiers: $10k for bootstrapped/self-funded companies under $1M raised, $100k for companies under $5M raised and funded by an affiliated partner, and $350k for companies with $5M+ raised and an affiliated partner. Source: Cloudflare Startups, 2026-07-04

Credits cover usage-based developer platform services including Workers, Workers for Platforms, Durable Objects, Workflows, Workers AI, KV, D1, Queues, Vectorize, R2, Pages, Images, Stream, Cache Reserve, and Argo Smart Routing. R2 has a $10k cap; Workers AI caps vary by tier ($2.5k / $25k / $50k); AI Gateway is temporarily excluded. Core security/networking benefits include three enterprise domains, unlimited Business/Pro plans, DDoS and bot protection, WAF custom rules, SSL, CDN/DNS, two-origin load balancing, one rate-limit rule, and 100% SLA. Source: Cloudflare Startups, 2026-07-04

Qualification requires an incorporated company no more than 10 years old, funded up to Series B within the last 12 months, a technology product, a public website, public social presence, first-time program approval, and a domain-matching business email. The practical caveat: credits are tracked on invoices, not directly in the Cloudflare dashboard, and they expire after the original one-year cohort window even if a tier upgrade is approved. Source: Cloudflare Startups, 2026-07-04

Lunora is an alpha reference for a Convex-style Cloudflare backend: schema-defined TypeScript functions, realtime state through Durable Objects, D1, R2, Queues, and a typed ctx surface. Use it as design reference only until a pinned release is audited; normal Cloudflare work still starts with wrangler, Cloudflare Workers, and Security and Review Skills. Source: X/@prisis, 2026-06-26; Source: GitHub anolilab/lunora, 2026-06-30

PlanetScale Billing Route

Cloudflare now exposes PlanetScale Postgres and MySQL creation from the Cloudflare dashboard for Workers apps, with pay-as-you-go usage billed through the Cloudflare account. The integration routes Workers to regional PlanetScale databases through Hyperdrive, which provides connection pooling and query caching while keeping existing drivers, ORMs, and SQL tooling. This strengthens Cloudflare as a full app platform for centralized relational data that does not fit D1/edge SQLite, while keeping the default Cloudflare path target-specific rather than a blanket Vercel replacement. Source: Cloudflare changelog, 2026-06-18; Source: Hyperdrive PlanetScale docs, 2026-06-18

VPS Front Door / Edge Sidecar

In Modern Web VPS Stack, Cloudflare is the public edge and selective service layer around a TanStack/Tailwind/Vite app. The app can run on Hetzner/Coolify/Node while Cloudflare owns DNS, CDN, WAF/DDoS, Access, Tunnel, and edge services; or the same TanStack Start app can target Workers when the runtime constraints fit. Cloudflare's Workers docs list TanStack Start as a supported full-stack framework, and the Cloudflare Vite plugin supports TanStack Start SSR while running Worker code inside workerd. Source: Cloudflare TanStack Start and Vite plugin docs, 2026-07-06

For VPS origins, Cloudflare Tunnel is useful when the origin should initiate outbound connections and avoid exposing inbound ports directly. The safety model is still explicit: verify the zone/account, named tunnel, DNS route, origin service, Access policy, and rollback path before changing production routing. Source: Cloudflare Tunnel docs, 2026-07-06

Version Snapshot

Checked 2026-07-06 against the npm registry:

Before changing Cloudflare resources, verify both tool version and account state: wrangler --version, wrangler whoami, then read/list target resources. Source: npm registry packument, 2026-07-06

Routing Summary

Preferred order: Frontend and Design Skills skill plus wrangler CLI for Cloudflare resources, Security and Review Skills for code review, cloudflared for tunnels, and service CLI registry for unknown products. Source: Skill Resolver, 2026-06-27; config/capability-harvest-seeds.json

Failure Modes

• Deploying to the wrong account or environment.
• Missing bindings in local vs production config.
• Treating Workers runtime as Node.js.
• Forgetting rollback or route impact.

Verification Path

Run wrangler whoami, read/list target resources, and use preview/local dev before production deploy. For tunnels, verify active config and target origin. Source: config/capability-harvest-seeds.json; Skill Resolver, 2026-06-27

---

Timeline

• 2026-07-06 | Added Cloudflare's role in Modern Web VPS Stack: DNS/CDN/WAF/Tunnel/Access as the VPS front door, Workers/bindings as optional edge sidecars, and first-party TanStack Start/Vite plugin support when the app targets Workers. Refreshed @cloudflare/workers-types to 5.20260706.1. Source: User request, Cloudflare docs, npm registry, 2026-07-06
• 2026-07-04 | Deep-reviewed the CloudflareDev and CFchangelog PlanetScale billing bookmarks. Added the Cloudflare-dashboard creation and billing route for PlanetScale Postgres/MySQL, with Hyperdrive as the Workers connection-pooling/query-cache layer. Source: X/@CloudflareDev, 2026-06-19; Source: X/@CFchangelog, 2026-06-19; Source: Cloudflare changelog and Hyperdrive docs, 2026-07-04
• 2026-07-04 | Deep-reviewed the @ibocodes Cloudflare + PlanetScale replacement-stack image. Preserved it as sentiment evidence for the Cloudflare/PlanetScale pairing, not as blanket advice to leave Vercel + Supabase; refreshed @cloudflare/workers-types to 5.20260704.1. Source: X/@ibocodes, 2026-06-20; Source: npm registry, 2026-07-04
• 2026-07-01 | Refreshed npm registry snapshot: wrangler advanced to 4.106.0; @cloudflare/workers-types advanced to 4.20260701.1. Source: npm registry packument, 2026-07-01
• 2026-07-04 | Added Cloudflare for Startups as the current credits/subsidy route for early-stage teams building on Workers, storage, networking, and security products; recorded the $10k / $100k / $350k tiers, major caps, AI Gateway exclusion, and eligibility constraints. Source: Cloudflare Startups, 2026-07-04
• 2026-07-03 | Deep-reviewed the earlier @ibocodes Workers + D1 minimum-stack bookmark and refreshed tooling: wrangler advanced to 4.107.0; @cloudflare/workers-types advanced to 5.20260703.1. Source: raw/x-bookmarks/enriched/2068652359194992778.json; npm registry, 2026-07-03
• 2026-06-30 | Deep review refreshed versioning: wrangler remains 4.105.0; @cloudflare/workers-types advanced to 4.20260630.1; no new skill was created because skills/engineering/cloudflare/ already owns this stack. Source: npm registry, 2026-06-30
• 2026-06-30 | Added Lunora as an alpha/reference route for Convex-style realtime DX on Cloudflare; default Cloudflare execution still routes through wrangler and Workers best practices. Source: X bookmark artifact audit, 2026-06-30
• 2026-06-29 | Added the small-product Cloudflare stack signal: Workers, D1, Better Auth, KV, R2, Queues, Hyperdrive, email routing, WAF, and DDoS protection as a predictable-cost route. Source: X/@ibocodes, 2026-06-28
• 2026-06-29 | Recorded tooling version snapshot: wrangler 4.105.0 and @cloudflare/workers-types 4.20260629.1. Source: npm registry via npm view, 2026-06-29
• 2026-06-27 | Canonical ecosystem page created so Cloudflare has a platform-level page beyond Wrangler and Workers-specific skills. Source: User request, 2026-06-27; Ecosystem Capability Coverage