Why Drift?
It doesn't make your app smaller. It makes the surface you operate smaller.
Here's the honest version, because it's the one that actually tells you when Drift is the right call.
Drift is not a way to write less code. A real app — auth, a database, file uploads, a frontend — is roughly the same amount of code whether you build it on Postgres + a web server + a reverse proxy, or on Drift. What Drift removes is everything around that code: the part that isn't your product, the part you'd otherwise own forever.
What actually disappears
Not the architecture — the yak-shaving, and then the long tail of operating it. On Drift you never write or run:
| The usual | On Drift |
|---|---|
| Dockerfile, container registry, image builds | One Driftfile, one deploy. |
| nginx/Caddy, TLS certs, certbot renewals | HTTPS on your slice's URL, renewed for you. |
DATABASE_URL, connection pools, a migration runner | drift.SQL("app") — the DB is declared and reachable by name. |
| CORS preflight config between frontend and API | Same-origin /api/* — Canvas serves the site, no CORS exists. |
| A box you own: patches, backups, secret rotation, the 2am page | None of it. The slice is operated for you. |
That last row is the real one. A docker-compose.yml for the same app isn't large —
Postgres, a binary, Caddy, maybe forty lines. The weight was never the config. It's that the moment it's
running, you are the operator: the renewals, the backups, the upgrade that breaks at
midnight. Drift's win is that you never sign that contract.
What Drift doesn't do (on purpose)
Drift won't make the hard part of your app easy — because the hard part was never the containers. If your problem is concurrent ledger integrity, or a tricky permissions model, or a real-time merge, that difficulty is yours and it stays yours. Drift hands you sharp primitives — SQL transactions, Locks, Queues, a realtime hub — and then gets out of the way. It shrinks the boring surface so you can spend your attention on the part that's actually your product.
Who it's for
Drift wins hardest for the person who would otherwise be the operator — the solo builder, the small team, the side-project that you want to outlive your attention span. If you'd rather ship features than babysit a database and a TLS cert, the trade is squarely in your favour. If running infrastructure is your craft and your joy, you may not need it — and that's a fair answer too.
And because Drift runs on European infrastructure with no US-owned dependency in the data path, "I never operate it" doesn't cost you sovereignty — see Security.