Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
Hide categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
      • Working with Node.js
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • Working with PHP
      • PHP Behavior in Heroku
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Heroku Inference
      • Quick Start Guides
      • Inference Essentials
      • AI Models
      • Inference API
    • Working with AI
    • Model Context Protocol
    • Vector Database
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Security
  • Private Spaces
  • Add-ons and Private Spaces

Add-ons and Private Spaces

Last updated December 03, 2024

Table of Contents

  • Provisioning an Add-on
  • Add-on Region Availability
  • Add-ons Compatible with Private Spaces
  • Add-ons Available and Installable in Private Spaces
  • Private Datastores
  • Additional Reading

You can use add-ons from the Heroku Elements Marketplace for apps in Private Spaces. You can install some add-ons inside of a space, while others are compatible but operate outside of a space.

For information on Heroku add-on credits and overage payments mechanisms, see the Heroku Enterprise documentation.

Provisioning an Add-on

Not all add-ons are compatible with Fir-generation apps. Check the add-on’s page in the Heroku Elements Marketplace to check for compatibility.

Just like with the Common Runtime, you can use the heroku add-ons:create command or the Heroku Dashboard to provision an add-on.

For example, heroku add-ons:create newrelic:wayne -a appname.

You can also install select add-ons in specific regions with the --region flag. See Install a Database in Another Region for more info.

Add-on Region Availability

To view which add-ons are available in a region, go to the Add-on Runtime Availability. Select the Private Spaces tab to view information for Private Spaces regions.

Region Availability

You can also view this information in the Region Availability section of the Elements listing page for each add-on.

Region Availability Map

If you try to provision an add-on and it’s unavailable in that space’s region, you get an error message.

Add-ons Compatible with Private Spaces

Many add-ons offer plans that are compatible with Private Space regions, even though they operate outside the Private Space. Network traffic between your app’s dynos and the add-on resource travels across the public internet. These add-ons are marked as “Available” with a green dot in Add-on Runtime Availability.

Available

External Datastores

Some datastore add-ons are compatible. For these add-ons, we prompt you to confirm that you understand that this datastore isn’t contained within the space’s network boundary and sends data over the public Internet.

Provision Message

$ heroku add-ons:create <add-on name> -a app name
 !    This add-on is not automatically networked with this Private Space.
 !    To proceed, type "app name" or re-run this command with --confirm app name

Add-ons Available and Installable in Private Spaces

You can install some add-ons in Private Spaces, meaning that all network traffic between dynos and the add-on resource stays within a space’s network. These add-ons are marked as “Available & Installable in Private Space” with a blue dot in Add-on Runtime Availability.

Installable in Space

Private Datastores

Heroku Postgres, Heroku Key-Value Store, and Apache Kafka on Heroku are examples of add-ons that get created inside Heroku Private Spaces. When you select a private plan for an app in a space, we automatically create it in the same region as the space and peer it to the space.

Install a Database in Another Region

You can provision Heroku Postgres, Heroku Key-Value Store, and Apache Kafka on Heroku plans outside of your Space. Provision one by specifying app, plan, and region using the --region flag.

$ heroku add-ons:create heroku-postgresql:standard-4 --region=us -a your-private-app-name

We prompt you to confirm the addition of the plan.

 !    This add-on is not automatically networked with this Private Space.
 !    To proceed, type "app-name" or re-run this command with --confirm app-name

Additional Reading

  • Add-ons Overview
  • Managing Add-ons
  • Heroku Elements Marketplace
  • Heroku Private Spaces

Keep reading

  • Private Spaces

Feedback

Log in to submit feedback.

Working with Private Spaces Heroku Postgres on Private and Shield Spaces

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices