Backend-as-a-server vs backend-as-a-service: owning the process vs renting the platform
When I started building backends, the choice looked binary: wire up Express and provision everything yourself, or rent a backend-as-a-service and let someone else run it. BaaS earned its popularity honestly. Supabase an
When I started building backends, the choice looked binary: wire up Express and provision everything yourself, or rent a backend-as-a-service and let someone else run it.
BaaS earned its popularity honestly. Supabase and Firebase give you a database, auth, storage and realtime without touching a server. You sign up, you build. For a weekend project or a team that never wants to think about infrastructure, that is a genuinely good deal.
But renting has a shape, and the shape shows up later. The bill scales with your usage. The limits are someone else's decisions. Moving off means rewriting the parts of your app that only existed inside their platform. You don't own the backend — you rent access to it, and the landlord sets the terms.
Yatta JS is the other shape. It is a backend-as-a-server: the whole backend in one Bun process you own and run. Database, auth, mail, storage, realtime, jobs, observability — built in, not bolted on, and not rented from anyone. One process to deploy, one log stream to read at 2am, no per-request meter running in the background.
Version 1.0.5, live on npm now, keeps pushing that one process outward instead of adding more services: it speaks WebDAV, OAuth 2.0 and OpenID Connect, exposes an embedded MCP server, and adds gRPC-Web, DNS over HTTPS and WebFinger. The point is the same as day one — the process learns the protocols the rest of the world already uses, so you don't have to add a service for each one.
I am not going to pretend the trade is one-sided. A managed service buys you things a single process can't: someone else's on-call rotation, a dashboard your whole team already knows, scaling you never have to plan. If your team needs that, rent it — that's what it's for.
But if you're a solo builder, or a small team shipping something of your own, ask what you're actually renting. A database you could run. Auth you could own. Jobs, mail, realtime — all things one process can already do. Every service you rent is a bill, a limit, and a migration waiting to happen.
The honest test is simple: if the platform disappeared tomorrow, how much of your app would you still have? With a backend-as-a-server, the answer is all of it. The process is yours. The data is yours. The code runs anywhere Bun runs.
npm i yatta.js
Docs: https://yatta.js.org — Code: https://github.com/psrockstar098/yatta.js
Rent when you need a landlord. Own it when you want the keys.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.