Run PostgreSQL on a server you own.

Provision the database, give each app its own credentials, and keep backups in your own bucket.

dash.serversinc.io/applications
An application detail page with its deployments, status and settings

Your database stays with your workloads.

PostgreSQL runs on your server, with persistent storage and scheduled backups under your control.

Provision a real database instance

Choose PostgreSQL and a supported version. Serversinc creates persistent storage and starts the database container.

Separate databases and users

Create a logical database and a dedicated user for each app, then grant only the access it needs.

Keep backups in your bucket

Schedule backups to S3-compatible storage you provide, then restore a backup when you need it.

Connect apps on the same server

Attach the app to the database instance network and use the instance name as its host.

Put PostgreSQL to work for your app.

Provision an instance, create credentials for one app, and connect it without exposing the database publicly.

Provision PostgreSQL on your server.

  1. In Servers, select your server and open its Database tab.
  2. Start provisioning, choose PostgreSQL and a supported version.
  3. Review the generated settings and create the instance.
  4. Wait until its status is Running before connecting an application.

Serversinc creates persistent storage and starts the database container. PostgreSQL versions 13 through 18 are supported; see the database engines reference.

Create a database and an app user.

Open the running instance and create a logical database for your app. Add a dedicated user, save the one-time password in your secret manager, and grant that user access to the database. Do not share the administrative account with the application.

Keep the database name, username, password and instance name for the connection settings in the next step. A rotated or newly generated password is shown once.

Connect an application on the same server.

Attach the application to the network named after the database instance. Set its database variables to the logical database and app user you created:

DB_CONNECTION=pgsql
DB_HOST=<database-instance-name>
DB_PORT=5432
DB_DATABASE=<database-name>
DB_USERNAME=<app-user>
DB_PASSWORD=<saved-password>

Store the password as a secret variable. Redeploy the application so the new settings take effect. The instance name is the host on the attached network; localhost refers to the application container itself.

Schedule backups to your own storage.

Register an S3-compatible backup location, then create a schedule for the PostgreSQL instance. Choose whether it covers the full instance or selected logical databases, then check the schedule’s latest run and test a restore before relying on it. Configure retention separately under Settings → Backups.

See database backup schedules and retention for the exact steps. For a separate command-line workflow, use the PostgreSQL Docker backup and restore guide.

Connect from your laptop through SSH.

Keep PostgreSQL off the public internet. If you need a local client, open an SSH tunnel to the server and connect your client to the forwarded local port. The SSH command depends on your server’s SSH user and address; confirm those values with your provider before connecting.

Once PostgreSQL is running, Serversinc manages the instance and its scheduled backups alongside the apps on your server. Read how to manage database instances, users and access.

One flat price for every PostgreSQL app.

£5 a month covers your first three servers. Every server after that adds £2 a month. Builds and bandwidth are on the house, and the servers stay on your provider and your bill.

PostgreSQL on Serversinc, answered.

Ship your PostgreSQL app today.

Connect a server you already run, or provision one on your cloud account. £5 a month covers the first three.