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
      • Working with Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
    • 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
      • PHP Behavior in Heroku
      • Working with PHP
    • 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
    • Model Context Protocol
    • Vector Database
    • Heroku Inference
      • Inference Essentials
      • AI Models
      • Inference API
      • Quick Start Guides
    • Working with AI
  • 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
  • Heroku Architecture
  • Compute (Dynos)
  • Dyno Reference
  • Dyno Scaling and Process Limits

Dyno Scaling and Process Limits

Last updated March 05, 2025

Table of Contents

  • Default Scaling Limits
  • Concurrent One-Off Dyno Limits
  • Process/Threads Limit
  • Additional Reading

The following are the limits for different Heroku dynos. For dyno features, see Dyno Tiers. For dyno specs, see Technical Specifications by Dyno Size.

Default Scaling Limits

Cedar Scaling Limits

The following limits exist per Cedar-generation app:

  • By default, applications can run a total of 100 dynos across all process types.
  • Apps running on Eco or Basic dynos can have only one dyno running per process type.
  • Apps running on Eco dynos can have a maximum of two concurrently running dynos. For example, you can have one dyno running for your web process, and one dyno running for worker.
  • You can’t scale a single process type that uses Performance, Private, or Shield dynos to more than 10 dynos.

Submit a request to raise these limits for your application.

Fir Scaling Limits

Fir, the latest generation of the Heroku platform, offers higher limits than Cedar. The following limits exist per Fir-generation app:

  • By default, applications can run a total of 255 dynos across all process types.
  • You can’t scale a single process type to more than 255 dynos.

Submit a request to raise these limits for your application.

Concurrent One-Off Dyno Limits

  • 1 Eco one-off dyno (Eco requires a subscription to the Eco dynos plan)
  • Up to 50 concurrent one-off Basic dynos
  • Up to 50 concurrent one-off Standard dynos
  • Up to 5 concurrent one-off Performance dynos
  • Up to 5 concurrent one-off Private dynos
  • Up to 5 concurrent one-off Shield dynos
  • Up to 255 concurrent one-off Fir dynos

Submit a request to raise this limit for your application.

Process/Threads Limit

The maximum number of processes/threads that can exist in dynos for Cedar-generation apps depends on dyno size:

  • Eco, Basic and Standard-1X dynos support no more than 256
  • Standard-2X and Private-S dynos support no more than 512
  • Performance-M, Private-M, Shield-M and Performance-L-RAM dynos support no more than 16384
  • Performance-L, Performance-XL, Private-L and Shield-L dynos support no more than 32768
  • Private-L-RAM, Shield-L-RAM and Performance-2XL dynos support no more than 65536
  • Private-XL and Shield-XL dynos support no more than 131072
  • Private-2XL and Shield-2XL dynos support no more than 262144

These limits include all processes and threads, whether they are executing, sleeping or in any other state. Note that the dyno counts threads and processes towards this limit. For example, a Standard-1X dyno with 255 threads and one process is at the limit, as is a dyno with 256 processes.

Fir dynos have dynamic limits for threads based on CPU and memory limits.

Additional Reading

  • Scaling Your Dyno Formation
  • Dyno Tiers
  • Technical Specifications by Dyno Size
  • Limits

Keep reading

  • Dyno Reference

Feedback

Log in to submit feedback.

Technical Specifications by Dyno Size Technical Specifications by Dyno Size

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