Pinned versions.
On paths you can open.
Postgres, MySQL, MariaDB, Redis, MongoDB and Elasticsearch run as containers you version yourself, on your server, with data on host paths you can inspect and back up. They change when you change them, never on an OS timer.
Choose the engine and the exact version.
Every service is a pinned image. No implicit “latest,” no surprise majors: the version you pick is the version that runs until you decide otherwise.
PostgreSQL
The default for most apps.
MySQL
Drop-in for existing stacks.
MariaDB
Community MySQL fork.
Redis
Cache, queues, sessions.
MongoDB
Documents, first-class.
Elasticsearch
Search & analytics.
Version lists shown are illustrative. The picker always reflects images currently offered.
Bind-mounted, not buried.
Service data lives on ordinary host paths, not opaque named volumes. You can list it, snapshot it, rsync it off-box and reason about exactly where every byte sits. It survives docker volume prune because it was never a hidden volume to begin with.
- inspectableOpen the directory. It's just files.
- portableCopy it anywhere. No lock-in, no export ritual.
- yoursLeaving the platform never means leaving data behind.
A version bump is a reviewed change, not a surprise.
Changing an engine version is a plan you approve: see the diff, apply when you're ready. Nothing upgrades itself behind an apt timer.
Stop paying per database.
Managed databases like Supabase, Neon, PlanetScale and Upstash are each their own subscription, growing with projects, branches and storage. On Sproobo a database is a container on the server you already pay for. The tenth instance costs what the first did: nothing new.
Instances are free moves
A staging copy, a per-client database, a throwaway box for an experiment. On usage-billed platforms each one is a purchasing decision. Here it's a click, on capacity you already own.
No usage meter
No per-request pricing, no per-GB egress, no per-branch charges. Your server's disk and RAM are the only budget a database draws from.
Caps, not prices
Plan tiers cap how many services you can create (2 on Free, 10 on Pro, unlimited on Team), but no tier ever prices a database individually.
Coming from Vercel with a Neon or Supabase stack next to it? Read Sproobo vs Vercel for the full cost-model comparison, or Vercel alternatives for four options weighed side by side.