The edge-first challenger vs the cloud giant. One keeps it simple, the other has a service for everything. Here's when each one wins.
Cloudflare's developer experience, zero egress fees, and edge-native architecture make it the better starting point for most builders. AWS is the answer when you need managed databases, ML pipelines, or enterprise compliance at scale.
Edge-first platform with Workers, R2, D1, and zero egress fees
The everything cloud, 200+ services for any workload imaginable
| Feature | Cloudflare | AWS |
|---|---|---|
| Compute | Workers, edge, sub-ms cold starts | Lambda, EC2, ECS, Fargate, etc. |
| Object Storage | R2. S3-compatible, zero egress | S3, industry standard |
| Database | D1 (SQLite at edge), Hyperdrive | RDS, DynamoDB, Aurora, Redshift |
| CDN / Edge | 350+ cities, built-in by default | CloudFront, powerful but separate |
| DNS | Fastest DNS globally, free tier | Route 53, reliable, pay per query |
| DDoS Protection | Unlimited, free on all plans | Shield Standard free, Advanced $3K/mo |
| Egress Fees | Zero on R2 and Workers | Significant, often the biggest cost |
| Developer Experience | Wrangler CLI, simple dashboard | Complex console, steep learning curve |
| Service Breadth | ~20 core services | 200+ services for every use case |
| Compliance | SOC 2, ISO 27001 | FedRAMP, HIPAA, PCI, SOC, ISO, etc. |
For indie hackers and startups, start with Cloudflare. Workers + R2 + D1 + Pages gives you a complete stack with incredible DX, zero egress fees, and global edge performance out of the box. You can build and scale remarkably far before hitting limits. When you need managed Postgres, ML services, or enterprise compliance, add specific AWS services alongside, they're not mutually exclusive. The smartest builders use Cloudflare as their default and AWS as their specialist.
Not entirely. Cloudflare excels at edge computing, CDN, DNS, and security, and with Workers, R2, D1, and Queues it covers many use cases. But AWS has 200+ services including managed databases, ML/AI, IoT, and enterprise tooling that Cloudflare doesn't offer. For many solo builders and startups, Cloudflare's stack is sufficient. For complex enterprise needs, AWS remains hard to replace.
Generally yes, especially for bandwidth. Cloudflare has zero egress fees on R2 (their S3 alternative), while AWS charges significant egress on S3 and other services. Cloudflare Workers has a generous free tier (100K requests/day). AWS can get expensive fast if you don't watch bandwidth and compute costs carefully.
For many use cases, yes. Workers run on Cloudflare's edge network (350+ cities) with sub-millisecond cold starts, while Lambda has variable cold starts and runs in specific regions. Workers are better for low-latency APIs, middleware, and edge logic. Lambda is better when you need long execution times, VPC access, or tight integration with other AWS services.
R2 is Cloudflare's object storage service with an S3-compatible API. The killer feature is zero egress fees, you pay only for storage and operations, not bandwidth. For apps that serve lots of files (images, videos, downloads), R2 can be dramatically cheaper than S3. It supports the same SDKs and tools as S3.
For most startups building web apps and APIs, Cloudflare's stack (Workers + R2 + D1 + Pages) is simpler, cheaper, and faster to ship with. Start with Cloudflare for its simplicity and predictable pricing. Move specific services to AWS only when you hit Cloudflare's limits, like needing managed Postgres, ML pipelines, or enterprise compliance features.
Tell us what you are building and we will pick the right tool for you. Or if you are ready to switch, we can help you move without breaking things.
Free. No signup required.
Want someone to choose for you?
Get a Decision Memo (£29) →Personalised recommendation with rationale, based on your use case.
