Last updated 16 March 2018
Table of Contents
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.
- Enterprise-grade support backed by a 30 minute SLA and access to Heroku Solution Architects.
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 are available in the Common Runtime. The private dyno types
private-l are available in Standard Private Spaces. The private dyno types
shield-l dynos are available in Shield Private Spaces.
Dyno memory and CPU characteristics are listed in the table below:
|CPU Share||Dedicated||Runtime||Compute1||Dyno units consumed|
|standard-1x||512 MB||1x||no||Common Runtime||1x-4x||1|
|standard-2x||1 GB||2x||no||Common Runtime||4x-8x||2|
|performance-m||2.5 GB||100%||yes||Common Runtime||12x||8|
|performance-l||14 GB||100%||yes||Common Runtime||50x||16|
|private-s||1 GB||Burstable||yes||Standard Private Spaces||2x-10x||5|
|private-m||2.5 GB||100%||yes||Standard Private Spaces||14x||10|
|private-l||14 GB||100%||yes||Standard Private Spaces||52x||20|
|shield-s||1 GB||Burstable||yes||Shield Private Spaces||2x-10x||6|
|shield-m||2.5 GB||100%||yes||Shield Private Spaces||14x||12|
|shield-l||14 GB||100%||yes||Shield Private Spaces||52x||24|
1Overall, 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 will vary based on available system resources.
The Free and Hobby dyno types are not available with Heroku Enterprise, because they are intended for experimentation and hobby applications only.
When you purchase Heroku Enterprise licenses, you estimate the number of dynos you need for application development and execution. These dynos may 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 is 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.
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:
standard-2x dyno for entire month: 2 dyno units
standard-1x dynos for entire month: 3 dyno units
performance-l dyno for entire month: 16 dyno units
performance-l dyno for half the month: 8 dyno units
Total: 29 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 cannot use private dyno types.
Default scaling limits
Scaling limits are different for apps in Private Spaces and apps in the Common Runtime.
For apps deployed to the Common Runtime, each process type can be scaled to a maximum of 100 dynos for
standard-2X sized dynos. A process type can be scaled to a maximum of 10 dynos for
Heroku data services
Heroku data services such as Heroku Postgres and Heroku Redis are purchased via add-on credits. You do not need to purchase licenses separately to use these services.
Heroku Private Spaces
Heroku Private Spaces are purchased via add-on credits similar to any other add-on. Once a Private Space is created, add-on credits will be consumed for the duration of its existence according to the unit pricing listed in the Elements catalog. For example, given a list price of
$1000 per Private Space, creating 2 Private Spaces at the beginning of a month and keeping them for the duration of the month will consume 2 add-on credits for the month.
Shield Private Spaces
Shield Private Spaces include additional features for building high-compliance applications. They are purchased via add-on credits similar to Standard Private Spaces. Add-on credits will be consumed from when a space is created until it is destroyed. The list price for Shield Private Spaces can be found in the Elements catalog.
Optionally, Heroku Enterprise can include Heroku Connect. This requires a separate line item on the contract. Please work with your sales representative to have Heroku Connect included.
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
$1000 worth of add-on services. For example, if you purchase 2 add-on credits, 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, you will have consumed 1 add-on credit for that month.
You can purchase add-on credits directly for Heroku data services and partner add-ons, or use the “general add-on” bucket to pay for overages you may incur in a given month for these add-ons.
General vs. Restricted add-on credits
General add-on credits can be used for all Heroku & partner-provided add-ons, including Heroku Private Spaces. Heroku General Add-on credits can not be used for Heroku Connect.
Restricted add-on credits are used for a specific type of add-on only. Heroku Enterprise customers can elect to break down add-on payment and usage by electing a contract based around four separate granular add-on credit types:
Heroku Data add-on credits can be used for all Heroku-provided data add-ons, such as Heroku Postgres and Heroku Redis.
Partner add-on credits can be used for all non-Heroku-provided add-ons.
Private Space credits can be used for Heroku Private Spaces.
Heroku Connect row credits can only be used for Heroku Connect.
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 (e.g. Data services, Partner services) billed to your Organization exceed their monthly contract, the overage can be auto-paid from available Flexible add-on credits.
Private Spaces and Heroku Connect rows overages can also be auto-paid from available Flexible add-on credits.
All members of an organization can inspect the current resource usage of all apps in the org by going to the org’s Resources page. This page is accessed by clicking on “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 1 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.
Organization admins also have access to the Usage page in Dashboard (other members do not). Admins can see current usage against the total dyno units and add-on credits available to them for that month. They can also see historical usage for previous months.