Skip Navigation
Show nav
Heroku Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
  • 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
    • Dynos (app containers)
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Command Line
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery
    • Continuous Integration
  • Language Support
    • Node.js
    • Ruby
      • Working with Bundler
      • Rails Support
    • Python
      • Background Jobs in Python
      • Working with Django
    • Java
      • Working with Maven
      • Java Database Operations
      • Working with the Play Framework
      • Working with Spring Boot
      • Java Advanced Topics
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku Data For Redis
    • Apache Kafka on Heroku
    • Other Data Stores
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
    • Compliance
  • Heroku Enterprise
    • Private Spaces
      • Infrastructure Networking
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
    • Single Sign-on (SSO)
  • 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 February 06, 2023

Table of Contents

  • Billing Cycle & Current Usage
  • Dyno Usage and Costs
  • Heroku Data Add-ons Usage and Costs
  • Other Add-ons Usage and Costs

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.

This article does not apply to Heroku Enterprise accounts. Please see Heroku Enterprise for more information.

Billing Cycle & Current Usage

Heroku charges based on usage. In any given month, you receive the bill for the previous month of use, not the current one.

To see your balance for the current month, look at Current Usage in the Billing Information section on your account’s Billing tab. It’s updated on a nightly basis, so it’s accurate up to the previous day (up to 00:00:00 UTC time).

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 $7/month. Running 1 Basic dyno costs roughly $0.01/hour. If you scaled your formation to 1 Basic dyno starting on 2022-01-01 00:00:00 and scaled down to zero at 2022-01-01 02:00:00, it would cost you approximately $0.02 for those two hours.

When executing a one-off dyno withheroku 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 price per dyno/month shown in the table is the maximum you are charged if you run the dyno 24 hours a day, 7 days a week since your last billing cycle.

Dyno Type Price per dyno/month
Eco $5 for 1000 dyno hours/month, shared across all your Eco dynos
Basic $7
Standard-1X $25
Standard-2X $50
Performance-M $250
Performance-L $500

For more information about the different dyno types, refer to the Dyno Types article.

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. The Eco dynos plan always renews on the first day of each month. If you subscribe to Eco after the first day, you are still charged the full $5 for that month.

For tips on optimizing your resources, see the Optimizing Resource Costs and Optimizing Dyno Usage article.

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, a Mini Heroku Postgres database costs $5/month. If you create a Mini Postgres database and delete it after 15 days, it costs you roughly $2.50.

Destroying an add-on also destroys all associated data.

See the Elements Marketplace for pricing. The price per add-on/month shown is the maximum you are charged if you run the dyno 24 hours a day, 7 days a week since your last billing cycle:

  • Heroku Postgres
  • Heroku Data for Redis
  • Apache Kafka on Heroku
  • Heroku Connect

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

Other Add-ons Usage and Costs

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

Keep reading

  • Accounts & Billing

Feedback

Log in to submit feedback.

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Podcasts
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing

Subscribe to our monthly newsletter

Your email address:

  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Heroku Podcasts
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Facebook
  • Instagram
  • Github
  • LinkedIn
  • YouTube
Heroku is acompany

 © Salesforce.com

  • heroku.com
  • Terms of Service
  • Privacy
  • Cookies
  • Cookie Preferences