Offsite Heroku Postgres Backups

Your secure Heroku postgres backup solution to deal with catastrophic Heroku outages, stored off platform in a location of your choice

Managed and unmanaged plans available

Why use

Heroku Backup Pro

Safe and secure

The backup process runs in your environment and uploaded directly to the storage backend with end-to-end encryption enabled by default

Quick and easy setup

Start capturing backups in no time thanks to our staightforward setup process with an intuitive UI

Flexible, cross-region storage options

Use your own storage backend or ours in the geographical region of your choice

Automated Backups

Schedule regular backups without any manual intervention

Monitoring and notifications

Receive timely notifications for any failed backups

Custom retention policy

You decide how long each backup must be kept

How it works

Postgres Backup Pro has been designed so that none of your data passes through our servers during the backup process. The add on requires you to add a tiny buildpack to your Heroku app. The buldpack includes a script that facilitates the backup process and it works as follows:

    1. The add on triggers the backup script and it runs in a once off dyno in your environment. This is either on demand or based on the backup schedule
    2. The backup is captured, encrypted and uploaded to either your own S3 bucket or to our managed storage solution
    3. Meta data such as the filepath, size of backup and current git commit is sent back to our servers

Frequently asked questions

1. Why do I need this if I can use pg:backups?

For most companies losing their data will most likely be catastrophic and lead to business failure. Any business continuity planning necessitates a backup solution outside the Heroku ecosystem, where database backups are stored in a different geographic region from the primary database.

The pg:backups solution offered by Heroku stores all database backups in the US region. For non-US customers and especially European customers this can present GDRP challenges. For US customers this means backups and the primary database are in the same geographic region. 

2. Why do a need to use an additional buildpack?

This approach ensures we don't have access to your data, providing an additional layer of transparency. Even when using our storage backend the files are encrypted with your encryption key

3. Why do you save the git commit hash?

Your database evolves with your codebase. By knowing which version of the code was running when the backup was captured greatly simplifies the restoration process.

4. Where can I find addional information?

If you have any further questions, please email us at 

©2023 Postgres Backup Pro, All right reserved.