Last updated November 07, 2024

Heroku Enterprise combines Heroku’s developer experience and platform features together with governance and management capabilities that you need as an organization.

When you sign up for Heroku Enterprise, your license includes:

• Dyno units and add-on credits for each month.
• Features such as Enterprise Teams and fine-grained access controls.
• Access to commercial plans for Heroku Connect.
• Access to Private Spaces, providing strong network-level isolation for apps that must meet strict security and governance requirements.
• Access to Shield Private Spaces, offering additional compliance features for applications with strong compliance requirements.

Fill out this form if you’re interested in Heroku Enterprise and want to have a member of our Sales team contact you.

Available Dyno Types

All professional dyno types are available in Heroku Enterprise. Professional dynos:

• Support multiple worker process types
• Enable horizontal and vertical scalability
• Include application metrics
• Offer faster builds and preboot

Professional dynos (performance- plans) are available in the Common Runtime. The private dyno types private-s, private-m, and private-l are available in Private Spaces. The private dyno types shield-s, shield-m, and shield-l dynos are available in Shield Private Spaces.

Basic dynos are also available. They are cheaper alternatives to professional dynos. Unlike professional dynos, basic dynos don’t have horizontal scalability, preboot, or language runtime metrics.

Dyno memory and CPU characteristics are listed in the table:

¹Overall, performance varies significantly based on app implementation. These figures show expected performance based on 99 percent of historical system loads. The performance of apps running on standard dyno types varies based on available system resources.

Default Dyno Types

In the Common Runtime, apps default to run on Basic dynos.

For Private Spaces, the default is Private-M. For Shield Private Spaces, the default is Shield-M.

Dyno Units

When you purchase Heroku Enterprise licenses, you estimate the number of dynos you need for application development and execution. These dynos can be used for different apps and also intermittently. Dyno units are a unit of consumption. In the dashboard, your total available quota, as well as how much of that quota your apps are currently using is shown in dyno units.

1 dyno unit = 1 standard-1x dyno running for a month

Dyno usage is aggregated across all apps that are part of the Heroku Enterprise account. It’s prorated to the second, and dyno units are consumed only for the period of time when the dyno is in use. For example, if you start 10 standard-1x dynos on the 1st of the month and scale it down to 5 for the second half of the month, you would have only consumed 7.5 dyno units. As another example, if your app runs every other day and uses 1 standard-1x dyno, you would have only used up 0.5 dyno units at the end of the month.

Burndown Rates

Different dyno types consume dyno units at different rates. A standard-1x dyno that runs for an entire month consumes 1 dyno unit, whereas a performance-l dyno that runs for the same time consumes 16 dyno units.

As an example, consider an app that runs a standard-2x web dyno, a performance-l worker dyno, and 3 standard-1x worker dynos. In the middle of the month, you add one more performance-l dyno and leave it running until the end of the month. Each month, this app’s total resource usage is:

1 standard-2x dyno for entire month: 2 dyno units

3 standard-1x dynos for entire month: 3 dyno units

1 performance-l dyno for entire month: 16 dyno units

Total: 21 dyno units

Mixing Dyno Types

Not all dyno types can be used by all apps. When you create an app, you choose whether to run it in a Private Space or in the Common Runtime (by specifying or omitting the --space parameter). Apps in Private Spaces can only run the private dyno types. Apps in the Common Runtime can mix Standard and Performance dynos as appropriate, but can’t use Private dyno types. You can’t mix Basic dynos with other dyno types.

Default Scaling Limits

Scaling limits are different for apps in Private Spaces and apps in the Common Runtime.

Common Runtime

For apps deployed to the Common Runtime, you can only scale one Basic dyno running per process type or a maximum of 100 dynos for standard-1X or standard-2X sized dynos. A process type can be scaled to a maximum of 10 dynos for performance dynos.

Private Spaces

See the Private Space Dev Center article for details on limits. Contact support to raise limits for applications and spaces in your Heroku Enterprise account.

Heroku Data Services

Heroku data services such as Heroku Postgres and Heroku Key-Value Store are purchased via add-on credits. You don’t need to purchase licenses separately to use these services.

Heroku Private Spaces

Heroku Private Spaces are purchased individually via the Private Spaces SKU as part of your Heroku Enterprise license. Private Spaces added during the month consumes add-on credits on a prorated basis. The list price for Private Spaces can be found in the Elements catalog.

Shield Private Spaces

Shield Private Spaces include additional features for building high-compliance applications. Like standard Private Spaces, Shield Private Spaces are purchased individually via their Shield Private Space SKU. Shield Private Spaces added during the month consumes add-on credits on a prorated basis. The list price for Shield Private Spaces can be found in the Elements catalog.

Heroku Connect

Optionally, Heroku Enterprise can include Heroku Connect. Heroku Connect is purchased via the Connect SKU as part of your Heroku Enterprise license. Work with your sales representative to have Heroku Connect included. You can’t use add-on credits to purchase Heroku Connect.

Shield Heroku Connect

Optionally, Heroku Enterprise can include Heroku Shield Connect. Shield Heroku Connect is purchased via the Shield Heroku Connect SKU as part of your Heroku Enterprise license. Work with your sales representative to have Shield Heroku Connect included. You can’t use add-on credits to purchase Shield Heroku Connect.

Add-on Credits

Heroku Enterprise includes access to a wide range of add-on services to help developers compose a complete application with minimal coding and operational overhead. When you purchase Heroku Enterprise licenses, you can purchase add-on credits to cover the usage of add-on services. Any service listed in Heroku’s Elements Marketplace can be used.

One add-on credit corresponds to $1 worth of add-on services. For example, if you purchase 2 1000-credit add-on credit SKUs, you can run a standard-6 Heroku Postgres database for one month (because this plan is listed at $2000 per month). Similar to dyno units, add-on credits are pro-rated to the second. For example, if you run a standard-6 Heroku Postgres database for exactly half a month, then you’ve consumed 1000 add-on credits for that month.

You can purchase add-on credits directly for Heroku data services and partner add-ons. Or you can use the “general add-on” bucket to pay for overages you incur in a given month for these add-ons.

Types of Add-on Credits

General add-on credits can be used for all Heroku & partner-provided add-ons. Heroku general add-on credits can’t be used for Heroku Connect.

Heroku Data add-on credits can be used for all Heroku-provided data add-ons, such as Heroku Postgres, Heroku Key-Value Store, and Heroku Kafka.

Partner add-on credits can be used for all non-Heroku-provided add-ons.

For information around the type of credits available under your current Heroku Enterprise contract, contact your Heroku Account Executive.

Add-on Credit Overages for Restricted Add-ons

In the event that restricted add-ons, such as data services and partner services, billed to your organization exceed their monthly contract, the overage can be auto-paid from available general add-on credits. Private and Shield space usage exceeding what’s contracted can also be paid using general add-on credits at the rate listed in the Add-ons marketplace.

Resource Usage

All members of an organization can inspect the current resource usage of all apps in the org by going to the team’s Resources page. This page is accessed by clicking Resources under the org in the sidebar. An up-to-date report is displayed.

The report shows the current usage for each app and the total estimated usage for all apps in the org. A count of development and production apps is also presented. A production app is any app that has more than one dyno at the time the report is generated.

You can drill down into the resource usage of each app by expanding the listed apps to get a breakdown of dyno units and add-on credits used by each app.