I'm building a startup on Cloudflare's free tier. Here's the full stack

I’m Building a Startup on Cloudflare’s Free Tier. Here’s the Full Stack.

Everyone talks about cloud costs like they’re inevitable. “That’s just the cost of doing business,” they say, while burning €10K/month on AWS.

I disagree.

I’m building a production startup (a B2B2C event marketplace serving 11 languages) and my monthly infrastructure bill is exactly €0.

Not a typo. Let me break it down.

• Cloudflare Workers - Serverless compute at the edge. My backend runs in 300+ data centers worldwide. No servers to manage. No cold starts worth worrying about.

• Cloudflare D1 - SQLite at the edge. 19 tables, 7 migrations, production-ready. It’s not Postgres, and that’s fine. For what we need, it’s fast and free.

• Cloudflare KV - Key-value storage for sessions and cache. Simple. Fast. Done.

• Cloudflare R2 - Object storage with zero egress fees. This is the one that really matters. AWS S3 charges you every time someone downloads a file. R2 doesn’t. For a marketplace with images and documents, that’s a game changer.

• Cloudflare Pages - Frontend hosting. Build, deploy, done. SSL included. CDN included.

This isn’t a landing page. It’s a real application:

• User authentication (Better Auth)

• Organization management with role-based access

• AI-powered chatbot with 3 operating modes

• File uploads and storage

• Email notifications (via Resend)

• CAPTCHA protection (Turnstile)

• 11 languages with full i18n

• 12 vendor categories

• Admin module

All of this. Free tier.

I spent 10+ years working at companies that burned serious money on infrastructure.

Here’s what I saw over and over:

Servers sitting idle 90% of the time. We’d provision for peak load and pay for silence. Serverless flips this — you pay per request. No requests? No cost.

Egress fees that exist because someone decided they should. AWS charges you to get your own data out. That’s not a technical limitation. That’s a business decision. R2 said no to that.

DevOps headcount to manage the complexity. We hired people to manage the infrastructure that was supposed to make things simpler. The cloud was meant to abstract complexity. Instead, it just moved it and added a bill.

Here’s the honest part: this won’t stay free forever.

When we get our first paying vendors (€138/month each, break-even at 12), the D1 reads will tick up. Workers invocations will increase. R2 storage will grow.

My estimate for supporting the first 100 vendors? Maybe €5-10/month.

Not €500. Not €5,000. Single digits.

The free tiers are genuinely generous:

• Workers: 100K requests/day

• D1: 5M rows read/day, 100K written

• KV: 100K reads/day

• R2: 10GB storage, 10M reads/month

• Pages: 500 builds/month, unlimited bandwidth

For an early-stage startup, that’s more than enough runway to find product-market fit before spending a cent on infra.

What I’d Tell Bootstrapping Founders

If you’re building something new and your first instinct is to spin up an EC2 instance or deploy to a €20/month VPS — stop.

Ask yourself:

1. Do I actually need a server running 24/7?

2. Am I paying for capacity I’ll never use?

3. Is my infra choice driven by habit or by the problem?

The cloud was supposed to make things cheaper. For most companies, it made billing harder to understand instead.

Cloudflare didn’t invent serverless. But they made the economics honest: generous free tiers, transparent pricing, and zero egress.

Your infrastructure bill should be the last thing keeping you up at night when you’re trying to find customers.

I’m Rocco, a software engineer building Eveo, a B2B2C event marketplace. I write about Cloudflare infrastructure, bootstrapping, and the things nobody tells you about building products.

What’s the most you’ve ever paid for infrastructure you weren’t using?
I’d love to hear your horror stories.