PostgreSQL, Redis, and MinIO in one click — with backups
Start a managed service next to your applications and reach it by name on a private network. Schedule backups to local disk or to S3, and stop paying for a second database bill.
What you get
No port, ever
A managed service publishes nothing to the internet. Your applications reach it by container name on a shared private network.
Backups that restore
Backups run the service’s own client inside its own container, so a dump is always made by the same version that will read it back.
Local disk or S3
Schedule backups to the server’s disk or to S3-compatible storage. A failed backup opens an alert rather than failing silently.
Pinned versions
Every image tag is pinned. “latest” on a database is how an on-disk format changes under you on an ordinary restart.
In detail
- Start, stop, and restart from the portal, like an application.
- Generated credentials reach the container through the process environment, never written into a file a backup would copy.
- Connection details are shown only to owners and admins, and every time they are shown it is written to the audit log.
Works well with
Environment variables
Encrypted, write-only configuration that never touches the disk.
Alerts
Alerts that open and resolve themselves — in the portal, email, webhook, or Telegram.
Teams and security
Organizations, roles, passkeys, two-factor, API tokens, and an audit log.
Your server is ready when you are
Create an account, connect a VPS, and ship your first application.