The One-Person Backend
SQLite, edge functions, and the death of the ops tax.
You don’t need a backend team anymore.
That sentence would have been absurd five years ago. Running a production web application meant provisioning servers, managing databases, configuring load balancers, setting up CI/CD pipelines, monitoring uptime, rotating credentials, and praying nothing broke at 3 AM. The “ops tax” on a solo builder was so steep that most people either partnered up, raised money, or built something simpler than what they actually wanted.
In 2026, a single developer can ship a globally distributed, offline-capable, real-time application with a database that fits in their deployment artifact. No Kubernetes. No RDS. No ops team. The infrastructure story has quietly become the most consequential shift in independent software.
The SQLite Moment
SQLite has been around since 2000. It powers more deployed software than any other database engine. But for web applications, it was always dismissed as a toy.
That changed. Turso built a distributed SQLite service (libSQL) that replicates globally. Litestream solved backup and replication. Fly.io made it trivial to run SQLite at the edge. ElectricSQL added real-time sync between local SQLite and central Postgres.
The result: you can build apps where the database lives inside your application and replicates automatically. No connection strings. No cold starts. Your database is a file.
Edge Functions Ate the Server
The serverless revolution promised to eliminate servers. It delivered vendor lock-in instead. But edge functions are actually delivering on the original promise.
Cloudflare Workers, Deno Deploy, Vercel Edge Functions all offer the same proposition: write a function, deploy it, it runs everywhere. Combined with edge-native databases, you get full-stack at the network edge.
The Local-First Renaissance
Local-first software was a niche academic concept five years ago. Now it’s becoming the default for indie apps. CRDTs matured. PowerSync, Replicache, and Zero ship production sync engines. Local-first eliminates the always-on server. Your costs approach zero at rest.
The New Stack
Database: SQLite + Turso
Compute: Edge functions
Sync: PowerSync or ElectricSQL
Deployment: Git push
Monthly cost for a side project: under $20. For thousands of users: under $100.
What This Actually Changes
The ops tax was the great equalizer. Now that it’s disappearing, the constraint has shifted from “can you run it” to “can you build something people want.” That’s a much better problem to have.