Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My Heroku bill is higher than I expected

Short answer

Heroku charges for wall-clock time, prorated to the second, so any dyno or add-on left on keeps billing whether it gets traffic or not. Look at the Billing tab and each app's Resources tab, find forgotten apps, dynos and add-ons, and back up data before removing a database.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The invoice is bigger than last month and nobody changed anything on purpose.
  • I see add-ons on the bill that I do not recognise.
  • There are old test apps or review apps still listed.
  • The previous developer set it up and I do not know what each part does.

Why does this happen?

  1. Usage is billed by time, not by traffic

    Heroku bills wall-clock time, prorated to the second, in arrears for the previous month. A dyno scaled above zero accrues usage whether or not it receives traffic. Heroku says to scale a dyno down to zero to stop its charges.

  2. Add-ons keep billing while they exist

    Standard add-ons such as databases accrue usage from creation to destruction. Metered add-ons can also charge for things like storage or bandwidth on top of their base plan.

  3. Hidden extras: one-off dynos, scheduler jobs and review apps

    One-off dynos, Heroku Scheduler jobs and dynos in review apps count toward usage too. Old pipelines and test apps keep these running.

  4. The app was sized for a busy day and never sized back

    More or larger dynos added for one busy period stay on the bill until someone reduces them. The moving-off-Heroku question is covered on a separate page.

What can I do about it today?

  1. Open the Billing tabAt dashboard.heroku.com/account/billing the current usage figure shows this month so far. It updates nightly, so it is accurate to the previous day.
  2. Open the Resources tab of each appFor every app, list the dynos and add-ons you see, with what they are called. Include apps you have not opened for a long time.
  3. Make a plain listApp name, what it is for, who uses it, which add-ons. Mark anything nobody can explain.
  4. Do not destroy a database add-on to save moneyHeroku states that destroying an add-on permanently deletes its data. Back up first and ask a developer to confirm that nothing uses it.
  5. Ask before scaling live apps downScaling the main app to zero takes the site offline. Only scale down apps that you are sure are unused.

When should I bring someone in?

  • You cannot tell which apps and add-ons are live and which are leftovers.
  • A database or add-on may hold customer data and you must not lose it.
  • You want to compare staying with moving to a server you control.

How do I handle it?

  1. Inventory everythingI list every app, dyno, add-on, pipeline and scheduler job against the invoice lines.
  2. Mark what is usedFor each item I check logs and connections to see whether anything real depends on it.
  3. Back up before any removalA database export is made and tested before an add-on or app is removed.
  4. Right-size what remainsDyno counts and sizes are matched to actual memory and traffic, using the app's metrics.
  5. Give you the options in writingReduce, keep, or move, with the effort and risks of each, so you decide.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Why am I billed if nobody uses the app?

Heroku says any dyno scaled above zero accrues usage whether or not it does work or receives traffic.

When does Heroku bill?

Monthly in arrears for the previous month's usage. The exception is the Eco Dynos Plan, a flat monthly subscription.

Is there another page for moving away from Heroku?

Yes, see the page on moving from Heroku to your own server.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.