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
View 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
    • Working with AI
    • Heroku Inference
      • Inference API
      • Quick Start Guides
      • AI Models
      • Inference Essentials
    • Vector Database
    • Model Context Protocol
  • 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
  • Accounts & Billing
  • Usage & Billing

Usage & Billing

English — 日本語に切り替える

Last updated May 15, 2025

Table of Contents

  • Billing Cycle and Current Usage
  • Dyno Usage and Costs
  • Heroku Data Add-Ons Usage and Costs
  • Other Add-Ons Usage and Costs
  • Metered Add-Ons Usage and Costs
  • Transferring to Heroku Enterprise

Heroku calculates billing based on wall-clock usage. This article explains the billing calculations. For specific guidance on minimizing your costs for different environments, see Optimizing Resource Costs.

Billing Cycle and Current Usage

Heroku charges based on usage, except for the Eco Dynos Plan. In any given month, you receive the bill for the previous month of use, not the current month. All usage is included and charged for, including any apps you created for staging, tutorial, or testing purposes.

To see your balance for the current month, in the Billing Information section on your account’s Billing tab, look at Current Usage. It’s updated nightly, so it’s accurate as of the previous day, up to 00:00:00 UTC time. Heroku Enterprise customers can look at their Enterprise Account Usage Dashboard and export CSVs.

The Eco Dyno Plan is a flat fee monthly subscription. You are charged for this plan for each month that you are subscribed, whether you used any Eco dynos that month or not. Eco dynos are unavailable for Heroku Enterprise. See Eco Dynos Plan for more info.

Dyno Usage and Costs

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. You can scale down your dynos when they’re not in use.

For example, a Basic dyno costs US$7 per month. Running 1 Basic dyno costs roughly $0.01 per hour. If you scale your formation to 1 Basic dyno starting on 2022-01-01 00:00:00 and scale down to zero at 2022-01-01 02:00:00, it costs you approximately $0.02 for those 2 hours.

When executing a one-off dyno with heroku run or the Heroku Scheduler, a dyno provisions for your command. The time spent executing the command accrues usage.

Dynos used in your review apps also count towards your usage.

The max price per month shown in the table is the maximum price you’re charged if you run the dyno 24 hours a day, 7 days a week since your last billing cycle. Dyno units are shown for Heroku Enterprise customers. For more information about the different dyno types, see Dyno Types.

Common Runtime Dyno Usage and Costs

Dyno Type Dyno Price Per Hour Max Price Per Month Dyno Units Per Month
Eco ~$0.005/hour $5 for 1,000 dyno hours per month,
shared across all your Eco dynos
N/A
Basic ~$0.01/hour $7 0.28
Standard-1X ~$0.03/hour $25 1
Standard-2X ~$0.06/hour $50 2
Performance-M ~$0.34/hour $250 8
Performance-L ~$0.69/hour $500 16
Performance-L (memory-optimized) ~$0.69/hour $500 16
Performance-XL ~$1.04/hour $750 30
Performance-2XL ~$2.08/hour $1,500 60

The Eco dyno plan provides 1,000 dyno hours for $5 per month. All Eco dynos in your account share this dyno hours pool. The Eco dynos plan always renews on the first day of each month. If you subscribe to Eco after the first day, you’re charged the full $5 for that month.

For tips on optimizing your resources, see the Optimizing Resource Costs and Optimizing Dyno Usage article. See Common Runtime Dynos for technical specs.

Cedar Private and Shield Dyno Usage and Costs

Dyno Type Dyno Price Per Hour Max Price Per Month Dyno Units Per Month
Private-S ~$0.17/hour $125 5
Private-M ~$0.34/hour $250 10
Private-L ~$0.69/hour $500 20
Private-L-Ram ~$0.69/hour $500 20
Private-XL ~$1.04/hour $750 30
Private-2XL ~$2.08/hour $1,500 60
Shield-S ~$0.20/hour $150 6
Shield-M ~$0.41/hour $300 12
Shield-L ~$0.83/hour $600 24
Shield-L-Ram ~$0.83/hour $600 24
Shield-XL ~$1.25/hour $900 36
Shield-2XL ~$2.50/hour $1,800 72

See Cedar Private Dynos and Cedar Shield Dynos for technical specs.

Fir Dyno Usage and Costs

Family Dyno Type Dyno Price Per Hour Max Price Per Month Dyno Units Per Month
Classic dyno-1c-0.5gb ~$0.035/hour $25 1
Classic dyno-2c-1gb ~$0.07/hour $50 2
General Purpose dyno-1c-4gb ~$0.11/hour $80 3
General Purpose dyno-2c-8gb ~$0.22/hour $160 6
General Purpose dyno-4c-16gb ~$0.44/hour $320 13
General Purpose dyno-8c-32gb ~$0.88/hour $640 26
General Purpose dyno-16c-64gb ~$1.39/hour $1000 40
Compute dyno-2c-4gb ~$0.21/hour $150 6
Compute dyno-4c-8gb ~$0.42/hour $300 12
Compute dyno-8c-16gb ~$0.83/hour $600 24
Compute dyno-16c-32gb ~$1.67/hour $1200 48
Compute dyno-32c-64gb ~$3.33/hour $2400 96
Memory dyno-1c-8gb ~$0.14/hour $100 4
Memory dyno-2c-16gb ~$0.35/hour $250 10
Memory dyno-4c-32gb ~$0.69/hour $500 20
Memory dyno-8c-64gb ~$1.04/hour $750 30
Memory dyno-16c-128gb ~$2.08/hour $1500 60

See Fir Dynos for technical specs.

Heroku Data Add-Ons Usage and Costs

A data add-on accrues usage as long as it’s enabled. Heroku prorates all costs to the second, calculated based on when you created or destroyed an add-on.

For example, an Essential-0 Heroku Postgres database costs US$5 per month. If you create an Essential-0 Postgres database and delete it after 15 days, it costs you roughly US$2.50.

Destroying an add-on also destroys all associated data.

For pricing, see the Elements Marketplace. The price per add-on per month shown is the maximum that you’re charged if you run the dyno 24 hours a day, 7 days a week since your last billing cycle.

  • Heroku Postgres
  • Heroku Key-Value Store
  • Apache Kafka on Heroku
  • Heroku Connect

For tips on optimizing your Postgres database, see Heroku Postgres Database Tuning.

Other Add-Ons Usage and Costs

Heroku prorates all costs to the second, calculated based on when you created or destroyed an add-on. For pricing, see each add-on’s individual Elements Marketplace page. The price per add-on per month shown is the maximum that you’re charged if the add-on is provisioned 24 hours a day, 7 days a week since your last billing cycle.

Metered Add-Ons Usage and Costs

Metered add-ons incur usage-based charges. A metered add-on can include free plans where the costs are entirely usage-based, or it can include plans with a pro-rated monthly price and additional usage charges. Additional usage charges can be for consumption such as storage, bandwidth, AI tokens, and more.

When you provision a metered add-on from the Heroku Dashboard, you see if the add-on will incur metered charges. You can see the price of the metered usage on the Elements page for the add-on. You can view the metered usage for the current billing period on the Resources tab from your App or Team in the Heroku Dashboard.

Heroku charges customers monthly for the metered add-on usage. Customers can see the details of the charges on their invoice and on the Billing tab. For Heroku Enterprise customers, add-on credits are applied to metered add-on usage costs.

Transferring to Heroku Enterprise

When you become a Heroku Enterprise customer, you have the option to move your existing Heroku Teams to your Enterprise licenses. If you transfer your teams, we’ll invoice you for any usage incurred prior to transferring it to your Enterprise account. Any usage incurred after the transfer counts against your Enterprise licenses.

Keep reading

  • Accounts & Billing

Feedback

Log in to submit feedback.

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