Cloudflare platform map
Start from request, data, state, and asynchronous needs to find the Cloudflare products worth investigating.
Edited and verified by Orange Book Editorial Team ·
Do not choose technology by product name. First decide where the work belongs in the request path and what consistency and lifecycle the data requires.
Quick selection
| Need | Investigate first | Main trade-off |
|---|---|---|
| Run HTTP logic | Workers | CPU time, runtime compatibility, location-independent code |
| Read configuration or rarely updated data | KV | Eventual consistency and high read throughput |
| Relational data | D1 | SQLite model, location, and transaction boundaries |
| Files and objects | R2 | Operations, caching, public access, and lifecycle |
| Strong coordination for one object | Durable Objects | Single-threaded concurrency, location, and durable state |
| Decouple background work | Queues / Workflows | Delivery, retries, idempotency, and execution duration |
| Manage model calls | AI Gateway | Providers, observability, caching, and cost control |
This is not a pricing table
Plans, limits, and regional availability change. Open the current Pricing and Limits pages before implementation.
Next step
Return to the request path, deploy your first Worker, or use Workers and Pages vs Vercel, Railway, and Render to decide whether the application needs isolates, functions, or containers.
Primary sources
Did this page help you complete your goal?
Beta feedback is generated in this browser and is never uploaded automatically.
Troubleshooting: why CF-Cache-Status is not HIT
Distinguish DYNAMIC, BYPASS, and MISS from response headers, then locate cache problems with read-only steps.
Workers and Pages vs Vercel, Railway, and Render
Compare Cloudflare Workers, Pages, Vercel, Railway, and Render across runtime, static hosting, Next.js DX, containers, background jobs, persistence, and billing.