Heroku
Managed application platform that runs apps in containers called dynos, deployed from Git or Docker images, with add-on services such as Heroku Postgres.
- paas
- Not documented
- $5 per month (Eco dynos plan, 1000 dyno hours shared across the account)
- Common Runtime: us (United States), eu (Europe). Private Spaces: Dublin, Frankfurt, London, Montreal, Mumbai, Oregon, Singapore, Sydney, Tokyo, Virginia
Who it suits.
Teams that want to deploy by pushing to Git and let the platform handle the runtime, with Postgres, a scheduler and Docker deploys available on the same platform.
Consider something else if…
The dyno filesystem is ephemeral, and a web process must respond within 30 seconds of receiving a request.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Heroku does not publish are not listed.
Pricing
Entry paid plan
$5 per month (Eco dynos plan, 1000 dyno hours shared across the account)
Sources (1) →Sources ↓
- Eco Dyno Hours | Heroku Dev Center ↗
“The Eco dynos plan provides 1000 dyno hours for $5 per month. This dyno hours pool is shared by all Eco dynos in your account.”
Read 2026-09-05 · official docs
Pricing model
Usage-based on wall-clock time, prorated to the second
Sources (1) →Sources ↓
- Usage & Billing | Heroku Dev Center ↗
“Heroku computes usage from wall-clock time, not CPU time. Any dynos scaled above 0 accrue usage, regardless of traffic or activity. Heroku prorates all costs to the second.”
Read 2026-09-05 · official docs
When you exceed a cap
Service sleeps: on the Eco plan ($5/month for a 1000 dyno-hour pool, the cheapest paid tier) exhausting the pool forces every Eco dyno on the account to sleep for the rest of the month, and extra hours cannot be bought
Sources (1) →Sources ↓
- Eco Dyno Hours | Heroku Dev Center ↗
“When you use all your Eco dyno hours for a given month, all Eco dynos on your account are forced to sleep for the rest of the month. You can't purchase additional dyno hours.”
Read 2026-09-05 · official docs
Limits
Memory (entry plan)
0.5 GB RAM on the Eco dyno ($5 flat/month, the cheapest paid dyno) and 0.5 GB on the Basic dyno ($7/month)
Sources (1) →Sources ↓
- Dyno Types | Heroku Dev Center ↗
“Eco | 0.5 GB | 1x | 1x-4x | $5 flat* | N/A | No | ✔”
Read 2026-09-05 · official docs
Sites or apps included
100 apps per account, platform-wide on all plans (Heroku Team 100, Enterprise Team 200)
Sources (1) →Sources ↓
- Limits | Heroku Dev Center ↗
“An account can have up to 100 apps.”
Read 2026-09-05 · official docs
File or inode limit
1000 MB maximum compressed slug size, platform-wide on all plans; raisable via support ticket
Sources (1) →Sources ↓
- Limits | Heroku Dev Center ↗
“The default maximum allowed slug size (after compression) is 1000 MB.”
Read 2026-09-05 · official docs
Concurrent builds
10 concurrent builds for verified users without an established payment history; 300 for verified users with one (platform-wide, all plans)
Sources (1) →Sources ↓
- Limits | Heroku Dev Center ↗
“Verified users without an established payment history can create up to 10 concurrent builds at one time. Verified users with an established payment history can create up to 300 concurrent builds at one time.”
Read 2026-09-05 · official docs
Max request duration
30 seconds (initial window for the web process to return response data)
Sources (1) →Sources ↓
- Limits | Heroku Dev Center ↗
“HTTP requests have an initial 30 second window for the web process to return response data. It can be either the completed response or some amount of response data to indicate that the process is active. Processes that fail to send response data within the initial 30-second window see an H12 error in their logs.”
Read 2026-09-05 · official docs
Execution
Streaming response limit
Platform-wide (router): 30 seconds to send the first byte, then a rolling 55-second idle window — if no data is sent for 55 seconds the connection is terminated
Sources (1) →Sources ↓
- Request Timeout | Heroku Dev Center ↗
“Heroku supports HTTP features such as long-polling and streaming responses. An application has an initial 30 second window to respond with a single byte back to the client. However, each byte transmitted thereafter (either received from the client or sent by your application) resets a rolling 55 second window. If no data is sent during the 55 second window, the connection will be terminated.”
Read 2026-09-05 · official docs
Managed connection pooling
Limited
Sources (1) →Sources ↓
- Server-Side Connection Pooling for Heroku Postgres | Heroku Dev Center ↗
“Server-side connection pooling is available for Standard, Premium, Private, and Shield-tier databases. [...] Server-side connection pooling isn't available for Essential-tier databases.”
Read 2026-09-05 · official docs
Deployment
Git deployment
Supported
Sources (1) →Sources ↓
- Deploying with Git | Heroku Dev Center ↗
“To deploy your app to Heroku, use the git push command to push the code from your local repository's main branch to your heroku remote.”
Read 2026-09-05 · official docs
Docker deployment
Supported
Sources (1) →Sources ↓
- Container Registry & Runtime (Docker Deploys) | Heroku Dev Center ↗
“Heroku Container Registry allows you to deploy your Docker images to Heroku. Both Common Runtime and Private Spaces are supported.”
Read 2026-09-05 · official docs
Containers
Supported
Sources (1) →Sources ↓
- Cloud Application Platform Pricing & Plans | Heroku ↗
“Dynos are the heart of every Heroku app—lightweight, isolated containers that handle your code, dependencies, and scaling.”
Read 2026-09-05 · official pricing
Scheduled jobs
Supported
Sources (1) →Sources ↓
- Heroku Scheduler | Heroku Dev Center ↗
“Scheduler is a free add-on for running jobs on your app at scheduled time intervals, much like cron in a traditional server environment.”
Read 2026-09-05 · official docs
Infrastructure
Persistent processes
Supported
Sources (1) →Sources ↓
- Dynos (App Containers) | Heroku Dev Center ↗
“Worker dynos are typically used to run background jobs, queueing systems, and timed jobs. You can have multiple kinds of worker dynos in your application.”
Read 2026-09-05 · official docs
Persistent storage
Not supported
Sources (1) →Sources ↓
- Dynos (App Containers) | Heroku Dev Center ↗
“Each dyno gets its own ephemeral filesystem, with a fresh copy of the most recently deployed code. During the dyno's lifetime, its running processes can use the filesystem as a temporary scratchpad, but no files that are written are visible to processes in any other dyno.”
Read 2026-09-05 · official docs
Managed databases
Supported
Sources (1) →Sources ↓
- Heroku Postgres | Heroku Dev Center ↗
“Heroku Postgres is a managed SQL database service provided directly by Heroku. You can access a Heroku Postgres database from any language with a PostgreSQL driver, including all languages Heroku officially supports.”
Read 2026-09-05 · official docs
Scales to zero
Limited
Sources (1) →Sources ↓
- Eco Dyno Hours | Heroku Dev Center ↗
“If an app has an Eco web dyno, and that dyno receives no web traffic in a 30-minute period, it sleeps. In addition to the web dyno sleeping, if you have a worker Eco dyno, it also sleeps. Eco web dynos do not consume Eco dyno hours while sleeping.”
Read 2026-09-05 · official docs
Autoscaling
Limited
Sources (1) →Sources ↓
- Scaling Your Dyno Formation | Heroku Dev Center ↗
“Heroku offers Autoscaling for Performance-, Private- and Shield-tier dynos. If that feature doesn't meet your needs, consider a third-party add-on from the Elements marketplace.”
Read 2026-09-05 · official docs
Regions
Common Runtime: us (United States), eu (Europe). Private Spaces: Dublin, Frankfurt, London, Montreal, Mumbai, Oregon, Singapore, Sydney, Tokyo, Virginia
Sources (1) →Sources ↓
- Regions | Heroku Dev Center ↗
“eu Europe Common Runtime us United States Common Runtime dublin Dublin, Ireland Private Spaces frankfurt Frankfurt, Germany Private Spaces london London, United Kingdom Private Spaces montreal Montreal, Canada Private Spaces mumbai Mumbai, India Private Spaces oregon Oregon, United States Private Spaces singapore Singapore Private Spaces sydney Sydney, Australia Private Spaces tokyo Tokyo, Japan Private Spaces virginia Virginia, United States Private Spaces”
Read 2026-09-05 · official docs