Understanding your invoice
Table of Contents
Summary of Changes
On June 1, 2011, Heroku switched from billing for “dynos” to billing for “dyno-hours”, which is more clear. This brings pricing inline with the new process model, wherein you can run one-off processes as well as manipulate the dynos for each of your app’s process types independently.
Understanding the Invoice
Each process type has its own section. Process types are defined by your Procfile on Cedar, and default to Web and Worker on Aspen & Bamboo. Additionally, all one-off administrative process are rolled up into a “one off administrative process” section. This includes running “heroku console”, “heroku run XXX” and “heroku rake” as well as any other one-off process you run.
If you change your processes to 0, you will not have an entry. You will see the previous entry ends and the next one begins with a gap where you were not charged for any dynos.
For process defined in your procfile, you have the ability to expand the view by clicking the arrow and see both a graph of usage over time as well as detailed line items of changes. The graph shows average usage per day, while the detailed usage below the graph shows every change made.
This means that if you ran your app with a single dyno for half of the day, and then scaled your app to 2 dynos at noon, your chart would display an average of 1.5 dyno-hours for that given day. If you look to find the exact detail of when you scaled up and down your dynos, this information is listed below. In the case above you would find the change around noon from 1 to 2 dynos.
