Databases

Managed PostgreSQL

PostgreSQL.
Part of your stack.

Run PostgreSQL beside the services that use it. Create your database, connect privately, and manage data, extensions, and backups from the same project.

YOUR PROJECT
Your applicationWeb app · API · worker
DATABASE_URL
Managed PostgreSQLTables · queries · extensions
Private service reference Illustrative connection

Connect without copying secrets

A reference.
A working connection.

Add a private service reference and your application receives DATABASE_URL on deployment. Keep the password out of your repository; the reference resolves the database’s current credentials when you deploy again.

How service references work
The tested Next.js application linked to PostgreSQL with a private DATABASE_URL reference

A real connection from our Next.js walkthrough. The disposable tutorial services were removed after testing.

Familiar tools, useful choices

Make it fit your data.

The current catalog offers PostgreSQL 16, 15, and 14, with 16 selected by default. Choose a version compatible with your application and extensions.

Explore your data

Browse tables and run SQL from the database’s data tools. Keep connection settings, query results, and service metrics within reach.

Add the extensions you need

Use supported extensions such as pgvector, PostGIS, and pg_trgm. Check the Extensions panel for what is available and installed in each database.

Control outside access

External access starts disabled. Use the private connection for Helicarrier services; review TLS and source IP controls when an outside tool needs access.

Ship the schema with the code

Give migrations
a place in the release.

Set a release command on your application to run its migration before the new release starts. Then check a health endpoint that queries the database, and verify the actual records.

Keep schema changes compatible with the running application where possible. An application rollback does not roll back your database.

Follow the tested Next.js guide Practice Prisma failure and recovery Move PostgreSQL from Render

THE VERIFIED EXAMPLE

  1. 01
    Connect privately

    Supply DATABASE_URL through a service reference.

  2. 02
    Run the migration

    Use npm run db:migrate as the release command.

  3. 03
    Verify the result

    Check readiness and the four sample records after a second deployment.

Choose your capacity

Memory and storage.
Both in the price.

The totals below include each plan’s default storage. Choose 2–64 GB of provisioned storage as your data grows; backups are optional.

Display currency
Switch currency to update every price on this page.

Standard USD rates. Confirm your account’s current rates in the dashboard.

Heli DB-S1

512 MB memory

$3.5/ month

Memory
$3/mo
2 GB storage
$0.5/mo

Heli DB-S2

1 GB memory

$7/ month

Memory
$6/mo
4 GB storage
$1/mo

Heli DB-S3

2 GB memory

$14/ month

Memory
$12/mo
8 GB storage
$2/mo

Heli DB-S4

4 GB memory

$28/ month

Memory
$24/mo
16 GB storage
$4/mo

Storage is $0.25/GB/month. Daily backups add 20% of the storage fee: $0.1/month for a 2 GB database. Monthly rates describe a full month of service, before any applicable fees or taxes. Your account’s current prices appear in the dashboard. How billing works

Recovery you can inspect

Know your
restore points.

Daily backups are an optional add-on. Inspect completed backups and their timestamps before relying on a restore point, and test recovery with disposable data.

Rehearse a PostgreSQL restore

See the backup reference for retention and recovery limits.

A rolling set of restore points.

Successful backups are retained across Latest, 7-day, 14-day, Monthly, Quarterly, 6-month, and Yearly horizons when an eligible backup exists.

This is at most seven successful restore points, not a separate daily copy for every day of a year. A new database will not have older restore points yet.

Restoring can replace data in the target database. Review the selected backup and stop conflicting writes before a planned restore.

Good questions

Before you create a database.

Can my app connect without a public database endpoint?

Yes. Use an internal service reference. External access is not needed for connections from your services on Helicarrier.

Can I use my own PostgreSQL client?

Yes. An outside client needs the database’s external connection and the appropriate access and TLS settings. See the connection guide before enabling it.

Are daily backups enabled automatically?

Do not assume they are. Review the optional add-on when choosing a plan, and check completed backup history on the database itself.

Can my coding agent work with the database?

Customer MCP tools can inspect and operate resources within their granted permissions. Start with the correct project and environment, then give explicit instructions for changes. See the tested MCP workflow.

Keep building

The details, when you need them.

Ready when you are

Make something.
We’ll keep it running.

Bring your code. Give your next idea a home on Helicarrier Cloud.