Stop Over-Engineering Your Side Project: Why I Moved Everything to the Edge
Look, I’m done. I’m tired of waking up to AWS billing alerts that look like a car payment just because I wanted to host a simple CRUD app. For years, we’ve been told that “real” developers need a massive VPC, three availability zones, and a load balancer that costs $20/month before a single packet even hits your server.
It’s overkill. It’s expensive. And honestly? It’s killing your momentum.
I used to spend more time configuring YAML files and worrying about cold starts on bloated “serverless” functions than actually shipping features. Then I moved my stack to the Edge (specifically Cloudflare Workers and Vercel Edge), and I realized we’ve been playing the game on “hard mode” for no reason.
The Myth of the “Enterprise” Stack
For a long time, Edge Computing was a buzzword reserved for Netflix or Cloudflare’s internal teams. The narrative was: “You don’t need global low latency for your cat photo app.”
They were wrong. Not because your 10 users in Ohio care about a 50ms vs. 200ms TTFB (Time to First Byte), but because the developer experience of the Edge is simply superior. When you move to the Edge, you aren’t just moving closer to the user; you’re moving away from the “Infrastructure Tax.”
Why I Ditched the Centralized Cloud
Here is what I’ve learned after migrating three of my active Indie Hacker projects to Edge-first environments:
- Zero Infrastructure Overhead: I don’t manage servers. I don’t manage Dockerfiles. I don’t even manage “regions.” I ship a function, and it’s just there.
- The Death of Cold Starts: Traditional AWS Lambda functions have to “boot up,” which feels like waiting for a 90s PC to start. Edge functions run on V8 isolates. They start in milliseconds. It makes your app feel like it’s running locally.
- The “Real” Free Tier: Most cloud providers give you a free tier that feels like a trap. Cloudflare gives you 100,000 requests per day for free. For a solo dev, that’s basically “infinite” until you actually have a business—at which point, paying $5 is a rounding error.
- No Vendor Lock-in Paranoia: People scream about lock-in, but let’s be real: you’re writing JavaScript/TypeScript. If I want to move from Cloudflare to Vercel or Deno Deploy, the logic remains the same. The “lock-in” is actually just “convenience.”
Is it Worth it for a Small App?
If you’re asking “Is it overkill?”, you’re asking the wrong question. The real question is: “Do I want to spend my Saturday debugging an Nginx config or shipping a new feature?”
For 90% of your projects—APIs, Webhooks, Auth proxies, or SaaS landing pages—the Edge is the only logical choice. You get global distribution for free, security at the edge (DDoS protection by default), and you never have to worry about a “viral” tweet crashing your $5 DigitalOcean droplet.
My Current Stack (The “Indie” Special)
I’ve stopped overcomplicating things. Here is what I’m shipping in 2026:
- Framework: Next.js or Remix (running on Edge Runtime).
- Database: Turso (SQLite at the Edge) or Neon (Postgres with a WebSocket proxy).
- Compute: Cloudflare Workers.
- Auth: Clerk or Kinde.
The Verdict: Traditional Data Centers are for legacy companies with legacy problems. If you are an Indie Hacker trying to find product-market fit, every minute spent on “infrastructure” is a minute you aren’t talking to users.
Stop building like you’re Google. You aren’t. Move to the Edge, save your money, and ship faster.