Backup · Render Postgres

Back up Render Postgres, and prove it restores

Restore-tested backups of your Render Postgres, written to storage you control. Paste the external connection string, and every backup can prove it restores.

Start free Read the Render guide →

External connection stringWorks with IP allow listsRestore-tested backupsStandard pg_dump archives

Backup · Restore test

Restore test Passed

prod-postgres Latest backup · 2.4 GB

Spin up a throwaway database
Restore the backup
Check the data came back 48 of 48 tables
Delete the throwaway database

This backup restores. Restore health 96%

A second copy, outside Render

An off-site backup is the one you can still reach when something goes wrong with the platform or the account. Norcube keeps it outside Render, in storage you control, and proves it restores.

Off-site, in storage you control

Norcube runs a full pg_dump on your schedule and writes the encrypted archive to Norcube-managed storage in Frankfurt or to your own S3-compatible bucket.

Proven to restore

Every backup can be restore-tested: Norcube restores it into a throwaway database and confirms your schemas, tables and rows come back.

Yours, in a standard format

Download any backup and restore it with standard Postgres tools, independent of Norcube. No proprietary format, no lock-in.

Connect Render, step by step

The Render-specific settings, from the connection string to network access. Everything after that is the standard Protect form: schedule, retention and restore testing.

Open your database's Info page
In the Render Dashboard, open the database and find PostgreSQL public connection details on its Info page.
Copy the external connection string
Use the External Connection String, not the internal one, which only resolves inside Render's private network. It looks like postgres://username:[email protected]:5432/database.
Paste it into Norcube with SSL required
Choose Protect a database, pick PostgreSQL, paste the string and set SSL mode to require. For least privilege, put a read-only role's credentials in the URL.
Allow Norcube's IP if you restrict access
Render Postgres accepts external connections from any IP with valid credentials by default. If you add an IP allow list, include 18.196.207.101.

What Norcube adds

Restore testing

Prove each backup restores, not just that the dump ran. A Passed badge per backup and a restore-health score per database show recoverability at a glance.

Failure and missed-backup alerts

Get notified when a backup fails, a restore test can't confirm your data, or a schedule silently stops. By email, Slack or a signed webhook, on every plan.

Your own bucket

Keep backups in Norcube-managed storage in Frankfurt, or in your own Amazon S3, Cloudflare R2, Backblaze B2, Wasabi or MinIO bucket.

Standard archives

Every backup is a standard pg_dump archive, gzip-compressed by default. Download it any time.

Render backups, answered

The questions that come up when backing up Render Postgres. The full guide is in the docs.

Why the external connection string?

The internal URL only resolves inside Render's private network. Norcube connects from outside Render, so it needs the external one.

Do restore tests flag Render-specific extensions?

No. Render doesn't ship proprietary extensions. Anything you enable, like postgis or pgvector, is a standard community extension, so restore tests exercise your real schema and run clean.

Is the connection encrypted?

Yes. Render encrypts external connections with Render-managed TLS certificates, and Norcube connects with SSL mode require.

Your Render data, backed up and tested

Start on the Free plan. No credit card required. Connect Render, pick a schedule and let the first restore test prove it.

Start free Read the guide

Free plan
No credit card
Standard formats
Restore-tested