Volumes & Databases

Managed Postgres, linked to your app.

Serverless Postgres and persistent volumes, provisioned in one command, linked to your app, and backed up with point-in-time recovery.

  • Postgres 16
  • Automatic backups
  • 7-day PITR
my-app-db
Provisioning Running
pgdata /var/lib/postgresql 10 GB
4% used
Connection string · DATABASE_URL on my-app postgres://app:••••••••@my-app-db.internal:5432/my_app_db
Backups
  • Completed base-2026-08-22 212 MB
  • Archived WAL 00000001000000A3 16 MB
  • Archived WAL 00000001000000A4 16 MB
Plain Postgres

Standard connection string, standard tools.

Any Postgres client

It is real Postgres with a real connection string. ORMs, migration tools, psql, and your existing dashboards work unchanged.

From command to connection

A database in three steps.

  1. 01

    Run zwrm postgres create

    Pick a size. zwrm provisions Postgres 16, attaches a volume, and starts the primary with WAL archiving.

  2. 02

    Link it to your app

    DATABASE_URL is injected into the app's environment. No secrets to copy, no config to edit.

  3. 03

    Forget about backups

    Base backups and continuous WAL archiving to EU object storage run automatically. Restore to any point in the last seven days.

What you get

The storage layer your app needs, without the ops.

Databases and volumes are provisioned, linked, monitored, and backed up by the platform.

  • Managed Postgres

    Postgres 16 on dedicated resources, sized to your app, with updates and monitoring handled.

  • Persistent volumes

    Attach block storage to any app or agent. Data survives redeploys, restarts, and scaling.

  • Linked by default

    Link a database to an app and the connection string appears as DATABASE_URL in its environment.

  • Continuous backups

    Base backups plus WAL archiving to EU object storage. Point-in-time recovery for the last seven days.

  • Private networking

    Databases listen on an internal hostname that only your apps and agents can reach.

  • Visible

    Size, usage, backups, and connection details in the dashboard, with backup events in the audit log.

EU hosting and self-hosting

Hosted in the EU. Or on your infrastructure.

Databases, volumes, and backups stay on European infrastructure, or on your own storage when you self-host.

Discuss your deployment
Managed by you

Your infrastructure

Run zwrm in your own data center or private cloud and keep databases, volumes, and backups on your own storage.

  • On-premises or private cloud
  • Your storage and backup targets
  • Your security and compliance policies
Questions, answered

Before you create a database.

Which Postgres version do I get?

Postgres 16, kept up to date by zwrm. You get a standard connection string and can use any Postgres client or ORM.

How do backups work?

A base backup is taken regularly and WAL segments are archived continuously to EU object storage. You can restore to any point within the last seven days.

How does my app connect?

Link the database to the app in the dashboard or CLI and DATABASE_URL is injected into the app's environment. Connections stay on the internal network.

Can I connect with my own tools?

Yes. It is standard Postgres. Use psql, your ORM, or migration tooling with the connection string from the dashboard.

What are volumes for?

Persistent block storage for apps and agents: uploads, caches, agent workspaces, or anything that must survive a redeploy.

Where is my data stored?

On European infrastructure operated by European providers, with backups in EU object storage. Self-hosted installations use your own storage.

One command away

Give your app a database today.

Create a database in minutes, or talk with us about sizing, backups, and data residency.