Heroku Postgres Legacy Plans

Last Updated: 13 May 2015

Table of Contents

Heroku Postgres is Heroku’s database-as-a-service running an unmodified PostgreSQL installation. If you’re looking for Heroku Postgres' current plans please visit the pricing page. The below pertains to the legacy plans for Heroku Postgres. These legacy plans are still available and provisionable, but not listed in heroku addons:list or within dashboard provisioning.

While the legacy plans are provisionable, they are not as performant as our current production tier plans. We strongly recommend that current production tier plans be used.

Second Generation Legacy Plans

The second generation legacy plans are also known as Heroku Postgres 2.0 plans.

The features of the Standard, Premium, and Enterprise tiers have similar features to the current (3rd generation) plans (with the exception of encyption-at-rest), but have about ½ the memory and less performance.

Tier Plans Description
Standard standard-yanari standard-tengu
standard-ika standard-baku standard-mecha
Standard production databases.
Premium premium-yanari premium-tengu premium-ika
premium-baku premium-mecha
Production databases with built-in hot-standbys for high-availability.
Enterprise enterprise-mecha enterprise-ryu Production databases with premium features and uptime SLAs.

First Generation Legacy Plans

The legacy plans consist of two tiers, starter and production, across a variety of plans.

Tier Plans Description
Starter dev, basic Free and low-cost database plans for evaluation, application development, and testing.
Production crane, kappa, ronin, fugu,

ika,zilla, baku, mecha
Production-grade monitoring, operations, and support.

Starter Tier

The starter tier database plans are not intended for production-caliber applications or applications with high-uptime requirements.

The starter tier, which includes the dev and basic plans, has the following limitations:

  • Enforced row limits of 10,000 rows for dev and 10,000,000 for basic plans
  • Max of 20 connections
  • No in-memory cache: The lack of an in-memory cache limits the performance capabilities since the data can’t be accessed on low-latency storage.
  • No fork/follow support: Fork and follow, used to create replica databases and master-slave setups, are not supported.
  • Expected uptime of 99.5% each month
  • No postgres logs

Production Tier

As the name implies, the production tier of Heroku Postgres is intended for production applications and includes the following feature additions to the starter tier:

  • No row limitations
  • Increasing amounts of in-memory cache
  • Fork and follow support
  • Max of 500 connections
  • 1 TB of storage (if you need beyond 1 TB please contact us)
  • Expected uptime of 99.95% each month
  • Database metrics published to application log stream for further analysis

Management of production tier database plans is also much more robust including:

  • Eligible for automatic daily snapshots with 1-month retention (see PGBackups for more details)
  • Priority service restoration on disruptions

Non-production applications, or applications with minimal data storage, performance or availability requirements can choose between one of the two starter tier plans, dev and basic, depending on row requirements. However, production applications, or apps that require the features of a production tier database plan, have a variety of plans to choose from. These plans vary primarily by the size of their in-memory data cache.

The cache and price for each legacy production plan is:

Plan Name Provisioning name Memory Price per month
Crane heroku-postgresql:crane 400 MB $50
Kappa heroku-postgresql:kappa 800 MB $100
Ronin heroku-postgresql:ronin 1.7GB $200
Fugu heroku-postgresql:fugu 3.75 GB $400
Ika heroku-postgresql:ika 7.5 GB $800
Zilla heroku-postgresql:zilla 17 GB $1600
Baku heroku-postgresql:baku 34 GB $3200
Mecha heroku-postgresql:mecha 64 GB $6400

Legacy plan technical characterizations

First Generation Legacy Plans

The following table outlines our production tier plans along with relevant specifications about the underlying hardware.

Heroku Postgres plan vCPU RAM PIOPs Multitenant
Crane 2 400MB 200 yes
Kappa 2 800MB 200 yes
Ronin 1 1.7GB 200 no
Fugu 1 3.75GB 200 no
Ika 2 7.5GB 500 no
Zilla 2 17.1GB 750 no
Baku 4 34.2GB 1000 no
Mecha 8 68.4GB 2000 no

Second Generation Legacy Plans

Heroku Postgres plan vCPU RAM PIOPs Multitenant Connection Limit Disk Size
Yanari 2 400MB 200 yes 60 64 GB
Tengu 2 1.7GB 200 yes 200 256 GB
Ika 2 7.5GB 500 no 400 512 GB
Baku 4 34.2GB 1000 no 500 1 TB
Mecha 8 68.4GB 2000 no 500 1 TB
Ryu 32 244GB 4000 no 500 1 TB

Legacy plan replacements

Most legacy Heroku Postgres database plans have replacements in the current plan lineup. When upgrading to the new lineups and architecture, please refer to this table to find the current replacement plan.

Legacy plan Current replacement
Crane Standard 0
Kappa Standard 0
Ronin Standard 2
Fugu Standard 2
Ika Standard 4
Zilla Standard 6
Baku Standard 6
Mecha Standard 7
Standard Yanari Standard 0
Standard Tengu Standard 2
Standard Ika Standard 4
Standard Baku Standard 6
Standard Mecha Standard 7
Standard Ryu Premium 8
Premium Yanari Premium 0
Premium Tengu Premium 2
Premium Ika Premium 4
Premium Baku Premium 6
Premium Mecha Premium 7
Premium Ryu Premium 8