← All posts

9 min read

Heroku Price: Real Monthly Costs for Four App Types

Key takeaways

  • Heroku's cheapest paid dyno is $5–$5.50 per month, but a realistic small production stack with Postgres, Redis and a worker runs $50–$100+ per month.
  • Heroku retired its free tier in late 2022, so even a side project starts around $10–$12 per month.
  • OpenMage and Magento-family apps need roughly 2 GB of RAM per web node, forcing Standard-2X dynos plus separate Elasticsearch, Redis and database add-ons.
  • The break-even point for switching is a second dyno plus a paid Postgres tier, where flat-rate platforms become cheaper and more predictable.
  • Heroku, Render and Railway all require an international USD-billing card, while Omeganodes accepts MTN and Airtel Money directly.

Heroku's cheapest paid dyno starts at $7 per month, but a real app rarely stops there: add Postgres, Redis, and a worker, and a small production stack commonly runs $50–$100+ per month. This guide itemises those costs for Node, Flask, Django, and OpenMage apps, then compares flat-rate alternatives you can pay for with mobile money.

What does the heroku price look like in its current plans?

Heroku bills dynos by the second against an hourly rate, with a published monthly equivalent. The Heroku pricing page lists the current tiers: Eco, Basic, Standard-1X, Standard-2X, Performance-M and Performance-L. Eco and Basic exist mainly for hobby and staging apps; everything above them is production money.

Eco, Basic and Performance dynos side by side

DynoRAMMonthly price
Eco512 MB$5 (shared Eco pool)
Basic512 MB~$5.50 ($0.007/hr)
Standard-1X512 MB$25 ($0.01/hr)
Standard-2X1 GB$50 ($0.02/hr)
Performance-M2.5 GB$250 ($0.0625/hr)
Performance-L14 GB$500 ($0.125/hr)

Note the jump: the first production tier costs 5x a Basic dyno, and one step up again costs 10x. Postgres, Redis and workers are billed separately on top of these numbers, which the worked cost models later in this article show.

What changed with the 2026 sustaining-mode announcement

Heroku is entering sustaining mode in 2026, meaning maintenance without meaningful new features. If you are re-evaluating your bill as a result, a side-by-side comparison like Omeganodes' Heroku comparison is a reasonable first stop before you re-architect anything.

How much does it cost to run a Node.js app on Heroku's cheapest dyno?

The one-dyno setup and its hidden minimums

A basic Node.js app needs one eco dyno, but the dyno is rarely the whole bill. Heroku's managed Postgres starts at its lowest paid tier, and Redis, if you use it for sessions or queues, is another add-on with its own monthly floor. So a "cheap" Node stack is realistically dyno plus database plus maybe Redis, three line items rather than one.

Push-to-deploy works the same as always: connect GitHub, git push, and Heroku builds and restarts. Automatic HTTPS on a custom domain is included.

When one dyno stops being enough

One dyno handles a side project. The moment you add a worker process for background jobs, you double the dyno line, and a crash or cold restart on a single dyno means downtime. If you outgrow that, flat-rate alternatives like Omeganodes price the whole stack as one plan, which is easier to budget in shillings or euros than three metered add-ons.

What do Flask and Django apps cost on Heroku once you add Postgres and workers?

Flask: web dyno plus Postgres line items

A Flask side project starts with one basic web dyno, then Postgres turns the bill into a real number. The cheapest paid Postgres plan on Heroku is mini at $5/month, and the next step up, basic, costs $50/month, with standard tiers running higher (Heroku Postgres plan pricing). So a Flask app with one $7 web dyno and a mini database runs about $12/month before backups, monitoring, or a custom domain.

Django: adding a worker dyno and scheduler

Django usually needs a second dyno for Celery workers, and scheduled tasks add a scheduler add-on on top. That is the long-run reality for most Python stacks: a web dyno, a worker dyno, a Postgres plan, and a scheduler each bill separately, so the line items multiply even though the app itself is one codebase. If you also run Redis for queues, that is another add-on line, and every one of these items is metered independently, so a traffic spike that scales the web dyno for an afternoon shows up as its own charge. The honest arithmetic: a Django production app on Heroku realistically lands around $25–$60/month for small traffic, and the database tier, not the dyno, is what pushes the total upward. On Omeganodes the same push-to-deploy setup, including the database and worker, is one flat price you can pay with MTN or Airtel Money, and if you are on OpenMage instead of Python, see our OpenMage hosting.

Why does running OpenMage or Magento on Heroku get expensive fast?

RAM and dyno size requirements for Magento-family apps

Magento and OpenMage are heavy PHP applications. The platform's own guidance calls for roughly 2 GB of RAM per web node, which rules out Heroku's smallest dynos. In practice that means Standard-2X dynos or larger for the web tier, plus a dedicated worker dyno for cron, indexing and order processing. Two web dynos and one worker on Standard-2X dynos already form the base of the bill before any data services.

Elasticsearch, caching and data-service add-ons

Magento-family apps also need services that Heroku does not run in-process. Elasticsearch (or OpenSearch) is required for catalog search, Redis for full-page cache and sessions, and a managed MySQL-compatible database for the store itself. Each of these is a separate paid add-on, and the search and cache tiers that handle a real catalog are not the cheapest ones. A store that fits on one small dyno plus free Postgres does not exist. Flat-rate hosts such as Omeganodes bundle these services into one monthly price instead of itemising them.

Which Heroku add-ons add the most to your bill?

Data services are the biggest line item

After dynos, Postgres and Redis are where your Heroku price climbs fastest. A hobby Postgres plan and a mini Redis instance together can cost more than the basic dyno running your app, and every worker or background job you add needs its own dyno on top. Redis pricing tiers are the clearest example of how quickly data add-ons compound: Heroku's Redis add-on documentation shows plans that scale from a few dollars for a small dev instance to far more once you need persistence and higher connection limits in production. Scheduler jobs and log drains add smaller but recurring charges.

Free-tier add-on minimums

The catch for side projects: Heroku's cheapest data plans often can't run alongside free dynos without upgrading both. Flat-rate alternatives priced for your region, like the ones compared at Omeganodes vs Ziploy, bundle Postgres and HTTPS into one payment instead of itemising each add-on.

How does Heroku's metered dyno pricing compare to flat-rate PaaS pricing?

Heroku bills per dyno per hour. A Basic dyno costs a fixed rate whether your app serves 10 requests or 10 million, but Eco and Basic dynos can sleep, and usage-based plans charge for the compute seconds you actually consume.

What metered billing means for a sleeping side project

Metered billing rewards apps with real traffic and punishes idle ones less than you'd expect: a sleeping Eco dyno still costs its monthly subscription. The real risk is the opposite direction. A Django app with a background worker runs two dynos around the clock, and metered pricing means every extra process, every scaled-up dyno during a traffic spike, shows up on the invoice. You model it, you estimate, and the bill still surprises you in month three.

Flat-rate alternatives: Render, Railway, Fly.io, Ziploy and Omeganodes

Flat-rate platforms charge a fixed monthly price per service. Render, Railway, Fly.io and Ziploy all work this way: you pick a plan, you know the ceiling. Omeganodes applies the same model with regional pricing and mobile money payment via MTN and Airtel, so no USD card is needed.

For a single Flask app with one worker, flat rate usually wins on predictability. Heroku wins only if your usage stays genuinely tiny. The honest gap: Omeganodes runs fewer regions than Fly.io, so latency outside Europe and East Africa is worse.

When does Heroku pricing stop making sense for a small production app?

The 2-dyno-plus-Postgres threshold

The break-even arrives the moment your app needs a second dyno plus a paid Postgres tier. Heroku's free Postgres is gone, and background jobs push you toward the Scheduler, whose jobs run on dynos you pay for by the second, with the add-on itself free but the usage billed (Heroku Scheduler). Once you're paying for two Standard dynos, a mini Postgres, and a worker, a flat-rate PaaS that charges one fixed monthly price for the app, database, and worker is usually cheaper and predictable. If you're paying in USD with a card you don't have, the comparison ends before it starts.

Where Omeganodes falls short too

We run the same honest test against ourselves. Omeganodes has no metered dynos and accepts MTN and Airtel Money, but there's no free tier, no managed Postgres add-on marketplace on Heroku's scale, and no SOC 2 story for compliance-driven buyers. If you need Heroku's breadth of add-ons or a compliance report, a flat-rate PaaS alone won't cover you either.

How can you pay for hosting without a USD-billing card?

Platforms that require international cards

Most Heroku alternatives, including Render, Railway, and Fly.io, bill in USD and require a credit or debit card at signup. If your bank in Kenya or Uganda issues a card that cannot make international payments, you cannot get past the checkout, no matter how good the free tier looks. Some developers work around this with virtual dollar cards, but those services carry their own fees and availability problems, and they fail without warning.

Mobile money support: MTN and Airtel

Omeganodes accepts MTN Mobile Money and Airtel Money directly, so you pay in your local currency from the same balance you use every day. There is no card application, no dollar conversion, and no intermediary to trust. Regional pricing keeps the monthly cost predictable for a side project or first SaaS app. The trade-off: the platform runs fewer regions and fewer managed add-ons than the bigger names, so check that your stack is supported before you commit.

FAQ

Can we deploy a Node.js app on Netlify instead of paying Heroku prices?

Netlify works for static sites and serverless functions, but it is not a drop-in replacement for a long-running Node server. If your app relies on websockets, background workers, or persistent processes, you will need a platform that runs full dynos or containers. For simple APIs, Netlify's free tier can genuinely replace a paid Heroku dyno.

Is Heroku still free or does it have a free tier in its current pricing?

No. Heroku retired its free dynos and free Postgres in late 2022. The cheapest options now are Eco at $5 per month and Basic at roughly $5.50, and even those are dyno-only: any database, Redis, or worker bills separately. A side project therefore starts around $10–$12 per month, not zero.

How do I deploy a Flask app on Heroku and what will it cost me per month?

Connect your GitHub repo or run git push heroku main with a Procfile declaring a web process. Costs: one Basic dyno at about $5.50 plus the mini Postgres plan at $5, so roughly $12/month. Add a Celery worker or Redis and the total climbs toward $25–$60 for production traffic.

Do I need a credit card that bills in USD to pay for Heroku, Render or Railway?

Yes, effectively. Heroku, Render, and Railway all bill in USD and require an international credit or debit card at signup. If your bank cannot make international payments, checkout fails regardless of the plan. Workarounds like virtual dollar cards exist but carry fees and can stop working without warning. Omeganodes accepts MTN and Airtel Money instead.

Is OpenMage the same as Magento 1 and can it run on a small dyno?

OpenMage is the community-maintained continuation of Magento 1, so the codebase is the same lineage. It cannot run on a small dyno: Magento-family apps need roughly 2 GB of RAM per web node, which means Standard-2X or larger, plus a worker dyno for cron and indexing, plus Elasticsearch, Redis, and a MySQL-compatible database as separate paid add-ons.

Deploy at the speed of Africa

World-class hosting, open to every developer, wherever you build and however you pay. Start free in a couple of minutes — no credit card, no lock-in.