Adios
Data services · plans from $10/month

Deploy PostgreSQL.Make persistence and credentials explicit.

Choose a PostgreSQL version, keep database credentials out of Git, attach persistent storage, connect the application, and verify data after a restart.

Deploy my projectDeploy a template
Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy

Candidate release

PostgreSQL

Healthy

SOURCE

Git

REGION

de

ROUTE

HTTPS

01Source received

02Build completed

03Runtime started

04Health check passed

Promoted route

production.adios.run

A production path for

PostgreSQL 15PostgreSQL 16PostgreSQL 17SQLPersistence

The production path

A working PostgreSQL project still needs a safe release.

The application or service is only one part of production. Build evidence, runtime state, health, secrets, logs, routes, and the promoted version should remain inspectable together.

Start PostgreSQL from a versioned template

Pick PostgreSQL 15, 16, or 17 and declare the application database plus user through the template environment contract.

Make persistence an explicit decision

The official PostgreSQL templates use persistent storage. Confirm backup, restore, capacity, and version-upgrade expectations before the database carries irreplaceable data.

Keep service state visible to operators

Inspect service health and application connectivity, then test writes, reads, reconnects, and restarts before production traffic depends on the database.

From source to release

Three steps keep the deployment path reviewable.

Use the source and production behavior the project already has. The manifest records what the platform should build or provision and how the result becomes ready.

  1. 01

    Start with source or a template

    Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.

    $adios login
  2. 02

    Review the deployment contract

    Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.

    $git diff -- adios.yaml
  3. 03

    Deploy and inspect the result

    Follow build and runtime evidence, verify the candidate, and open the promoted route or service connection.

    $adios up
adios.yaml
Your project
name: application-db
template: postgres:16

env:
  POSTGRES_USER: app
  POSTGRES_PASSWORD: secret://POSTGRES_PASSWORD
  POSTGRES_DB: app_production
Choose the required major version and store the password with adios secret set before deployment.

Deployable starting points

Start PostgreSQL from a template when the repository is not ready.

Compare supported PostgreSQL major versions before choosing the exact service template for your application.

Data services

PostgreSQL 15

PostgreSQL 15, 16, and 17 templates, plus PostgreSQL 16 with pgvector.

SQLAdios managed
Template key
postgres:15
Runtime
postgres
Repository
templates
Source path
postgres/15
git clone https://github.com/adiosdotdev/templates.git
cd templates/postgres/15
adios up
DeployView source

Data services

PostgreSQL 16

PostgreSQL 15, 16, and 17 templates, plus PostgreSQL 16 with pgvector.

SQLAdios managed
Template key
postgres:16
Runtime
postgres
Repository
templates
Source path
postgres/16
git clone https://github.com/adiosdotdev/templates.git
cd templates/postgres/16
adios up
DeployView source

Data services

PostgreSQL 17

PostgreSQL 15, 16, and 17 templates, plus PostgreSQL 16 with pgvector.

SQLAdios managed
Template key
postgres:17
Runtime
postgres
Repository
templates
Source path
postgres/17
git clone https://github.com/adiosdotdev/templates.git
cd templates/postgres/17
adios up
DeployView source
Read the PostgreSQL deployment guide

Before production

Verify the workload.Then promote it.

The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.

Ready when…

  • The application database and least-privilege user are defined.
  • Passwords are stored outside the manifest.
  • The application can reconnect after a restart.
  • Backup and restore ownership is documented.

Preview when…

  • The app moves between PostgreSQL major versions.
  • A migration rewrites or locks large tables.
  • Extensions or unusual server settings are required.

Questions, answered

What to know before deploying PostgreSQL.

Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.

Can I deploy PostgreSQL from an official template?

Yes. Choose the PostgreSQL template that matches the version or configuration you need, store credentials as Adios secrets, and deploy it from the console or with adios up.

Does the PostgreSQL template use persistent storage?

The official PostgreSQL templates use persistent storage. Confirm backup, restore, capacity, and version-upgrade expectations before the database carries irreplaceable data.

Which PostgreSQL versions have templates?

The current catalog includes PostgreSQL 15, 16, and 17, plus a PostgreSQL 16 variant with pgvector for vector search workloads.

Can an Adios app connect to PostgreSQL?

Yes. Store the connection value as a secret, inject it into the application runtime, and verify authentication, queries, and reconnect behavior before promotion.

Where should database and broker passwords be stored?

Store sensitive values in Adios secrets and reference them with secret://NAME. Do not place production credentials directly in adios.yaml or commit them to Git.

What should I verify before production traffic?

Verify authentication, application connectivity, write and read behavior, restart persistence, backup or recovery expectations, capacity, and the failure behavior of every dependent application.

Related deployment paths

Connect the rest of the stack.

Browse all deployment pages

Deploy pgvector

Start PostgreSQL with the pgvector extension, connect an embedding application, verify vector writes and nearest-neighbor queries, and test persistence.

Deploy MySQL

Start MySQL 8 with persistent storage, create a dedicated application database and user, protect both passwords, and verify data after restart.

Deploy Redis

Start Redis 7 for cache, session, pub/sub, or fast state workloads, then verify connectivity, persistence expectations, eviction, and dependency failure behavior.

Deploy FastAPI

Deploy a FastAPI service with its ASGI import target, dependency install, runtime port, health endpoint, secrets, and promoted release tied to source.

The first release

Deploy PostgreSQL with the source and evidence attached.

Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.

Start with AdiosCompare plans