Borealis Isolated Postgres: Serious Database Security for the Common Runtime
- Last Updated: November 20, 2026
The power of Heroku lies in its simplicity. Developers can spin up an entire app stack, complete with its own database and caching layers with just a single command. No need for the specialized, time-consuming work of managing servers and virtual machines. This convenience applies to interacting with your app stack as well. Need to apply some database schema migrations or populate your database with reference data? Just connect directly to the PostgreSQL database server using your app’s username and password and run your scripts.
Heroku Postgres supports several levels of database isolation. Common Runtime and Standard databases are on a public network, making remote management simple. Private and Shield are on private networks for additional isolation. Borealis Isolated Postgres fills an important niche by offering network-isolated PostgreSQL to apps on the Heroku Common Runtime.
The best of both worlds: strong isolation and easy access for authorized users
Every Borealis Isolated Postgres database cluster is provisioned inside its own isolated VPC that rejects all incoming network traffic by default. This satisfies the need to keep database servers isolated from untrusted networks, but without a way to connect to your database, it wouldn’t be very useful! Therefore, we support three main scenarios for connecting to your add-on database:
- A Heroku app’s dynos use our custom buildpack to automatically establish a secure tunnel to the database servers. There’s generally no need to modify your app’s code at all; if your application code already uses the
DATABASE_URLconfig var to connect to a database service, switching to Borealis Isolated Postgres is a seamless transition. Just add the buildpack to your app and it takes care of the rest invisibly. We even offer aDATABASE_READONLY_URLconfig var that optionally allows your app to connect with a strictly read-only database user role. - A developer or admin uses our custom CLI plugin (it’s seamlessly integrated into the Heroku CLI) to create a temporary secure tunnel to the database servers on the fly. Commands like
heroku borealis-pg:tunnelandheroku borealis-pg:psqlmake it possible to connect to the database from your local machine for remote administration and querying. Meanwhile, theheroku borealis-pg:runcommand can be used to execute database schema migrations or other non-interactive database scripts from your CI/CD process. Authentication and authorization are seamlessly tied to your Heroku user account, so you can get started without any extra configuration required. Just runheroku plugins:install borealis-pg-clito begin. To prevent accidental data loss, CLI connections are read-only by default, but you can always supply the--write-accessoption to get around that. - A third party service uses SSH local port forwarding (aka SSH tunneling) to connect to the database servers with an external data integration. This is useful for data warehousing and ETL services, many of which already support the use of an SSH tunnel to securely access a data store that is behind a firewall. By default, external data integrations have read-only access, but if the third party service needs write access, you have the option to enable it at creation time.
We integrate deeply with Heroku and always aim to provide a consistent experience to keep the learning curve to a minimum. Plus, all of our infrastructure is hosted on AWS, just like Heroku itself, so latency is not an issue. Taken together, this all ensures that, however you need to access your add-on database, the process is as quick, painless and secure as possible.
Database security in depth
It’s considered best practice to block all incoming network traffic to your data stores from untrusted networks. This prevents an attacker from performing password-guessing attacks, exploiting any known or unknown vulnerabilities or conducting denial-of-service (DoS) attacks directly against your data store.
However, a firewall alone isn’t enough to ensure data security. We employ a variety of other measures to keep your data safe and secure by default. Some highlights:
- Strict internal access controls: Add-on databases and their associated resources are restricted by platform-level role policies on AWS so that only staff with a documented need are allowed to view or make changes. In addition, all staff actions in AWS are recorded in a cryptographically tamper-proof audit log that is maintained by AWS.
- TLS 1.2+ encryption: All network traffic to and from the database is encrypted at the transport layer using modern cryptography.
- AES-256 encryption of data at rest: We follow the standard best practice to ensure that all data are fully encrypted when written to nonvolatile storage (a hard drive or SSD).
- Auto installation of minor updates: We periodically and automatically install minor version updates with security and bug fixes for PostgreSQL with zero downtime. Major version upgrades are performed on demand from the CLI and with less than a minute of downtime.
- Server certificate verification: Optionally set the standard PostgreSQL sslmode and sslrootcert connection parameters in your app’s code to verify a database server’s identity.
- Single-use end user credentials: Every time you connect to an add-on database using our plugin for the Heroku CLI, you receive a new, temporary set of database credentials.
- Frequent rotation of Heroku app credentials: Every week your Heroku app receives a new set of credentials and the old credentials are invalidated.
- SSH server protections:
- Dedicated instances: Every add-on gets its own completely independent SSH server to minimize your database’s exposure.
- SELinux enforced: SELinux strictly limits processes to the minimum privileges required to operate.
- Fail2ban: Detects and blocks clients that repeatedly try and fail to connect over SSH.
- Blocked shell access and remote commands: Even authorized users are not allowed to execute arbitrary operations on the server.
- Firewall: All network ports are blocked from incoming traffic except for SSH.
- DDoS protection: AWS provides DDoS protection at the platform level.
Don’t compromise on database security
You have flexible options for ensuring your database servers are properly isolated from the open internet, no matter what dyno runtime you choose for your apps. Heroku Private Spaces is a comprehensive solution that puts your entire stack into its own VPC for maximum protection. And for those using Heroku’s Common Runtime, Borealis Isolated Postgres can provide a similar level of protection along with enhanced ease of access for your app database.
- Originally Published:
- Add-onsDatabaseHeroku Postgres