Heroku Review

Heroku is still the platform a Rails or Node team means when they say the app should go live from a git push, and in 2026 that habit has a floor price. Eco is a paid hour pool, not a free dyno, and the always-on size bills even when nobody is hitting the app. A personal project can sleep and a Team app cannot, which is the split in this purchase.

This review prices Cedar dynos, Postgres, and the Private Space that Fir requires, then sets them next to Render, Railway, Fly.io, DigitalOcean App Platform, and Northflank. Stay if the Procfile and the add-on invoice are the workflow you want. Leave if you need more memory than the smallest metrics dyno.

Toolradar data: the September 2026 hosting and deployment ranking evaluated 297 tools, and 230 of them offer a free or freemium plan. Heroku is in that catalog and sits outside the top 10. A dyno that stays awake is a paid line on day one.

How we compared: vendor pricing and product pages read on September 24, 2026. Dyno and data prices are Heroku's published monthly maximums for a resource that runs the whole month. Eco is the exception, a flat subscription whether you use the hours or not. No vendor paid for a place in this review.

Heroku is Salesforce's platform as a service, acquired in 2011, which is why Enterprise features and a Salesforce sync sit behind a contract rather than a self-serve switch. You push code, Heroku builds it, and runs each process type in a dyno, so the bill follows process count, not a single app price.

The common runtime is Cedar, where Eco, Basic, Standard, and Performance dynos live, along with Postgres, Key-Value Store, and Kafka. Fir is the Kubernetes generation, and every Fir dyno requires a Private Space, so those shapes are not a cheaper Basic.

Heroku Connect syncs Postgres with Salesforce, and the Demo edition starts free, enough to see the mapping and not enough for production data. Enterprise and Shield editions are limited to Heroku Enterprise customers, so a production sync is a contract.

Managed Inference sits on the same pricing page, with token rates rather than a seat fee, so you pay only when a model is called.

The everyday loop is a git push and a Procfile, which is the habit you are paying for. The web process and a worker are separate formations, so both running is two dynos, not a bundled app fee.

One-off commands, including Heroku Scheduler, provision a dyno for the length of the command and that time is billed, so a short nightly task is not free.

Eco is only for personal apps, meaning apps that are not in a Heroku Team or an Enterprise Team. The plan is a fixed hour pool for the month, shared by every Eco dyno, review app, and Heroku CI run on that account, so a pull request and the live app spend the same hours.

A web dyno sleeps after 30 minutes without requests, and sleep does not consume hours, so idle time stays inside the pool. A worker-only Eco app does not sleep, because it never sees web traffic, and it can burn the pool around the clock.

When the account hits the full pool, every Eco dyno is forced to sleep until the next month, and Heroku does not sell extra Eco hours. The documented move for an app that must stay up is Basic, roughly $0.01 an hour.

Standard-1X adds metrics, threshold alerts, preboot, and horizontal scale, and the RAM does not increase with those features, so you pay for a safer deploy rather than a larger process. Performance dynos are limited to accounts with an established payment history, so a new team cannot use them as the first production size.

Heroku bills dynos on wall-clock time, not CPU time. Anything scaled above zero accrues usage whether or not requests arrive, prorated to the second, except Eco, which is a flat fee for the month you are subscribed. A dyno left scaled up still costs the full month, traffic or not.

A Basic dyno that runs the whole month is the always-on common-runtime size. A Standard-1X web dyno plus a Standard-1X worker is two of those $25 lines, and the database is a third line.

Essential-0 Postgres matches the Eco monthly fee, with a 4-hour downtime ceiling and shared RAM, which fits a side project and fails if that outage would wake a customer, and the dedicated step up is Standard-0.

High availability is Premium-0 at $200, still on the same RAM and disk, with rollback out to 7 days and a 15-minute downtime ceiling.

Kafka's cheapest plan, Basic 0, is $100 a month, often a larger line than the web dyno.

Render's always-on Starter matches that Basic monthly maximum, and its free web instance spins down after 15 minutes inside a 750-hour pool. Railway Pro is $20 per workspace with a matching usage credit and unlimited seats, plus the per-vCPU and per-GB rates in the table.

Fly.io's shared-cpu-1x is $2.02 a month in Ashburn and Amsterdam, and $2.43 in San Jose, so the city is part of the price. App Platform's smallest shared container matches Eco's monthly rate, and a development database is another line at Basic's monthly maximum. Northflank's nf-compute-10 is $2.70 a month for a container you can leave running.

Prices below were verified on each vendor's pricing page in September 2026. Heroku Enterprise, Render Enterprise, Railway Enterprise, and Northflank Enterprise are quotes. Fly.io support is a separate purchase from the machine price.

Heroku fits a small team that wants a Procfile, a Postgres add-on, and a bill made of named dynos rather than a cloud calculator. Personal projects can live on Eco if idle sleep is acceptable. A customer-facing app on a Team starts at Basic, because Eco is refused there, and it should move to Standard once you want preboot and metrics.

It is the wrong default when the process needs more memory than the smallest metrics dyno and you are not ready to step up, or when high availability on Postgres means the Premium plan. Fir and network isolation add a Private Space before the first Kubernetes-shaped dyno, so isolation is a platform fee.

If the workload is a VM you SSH into, read VPS hosting for developers and the DigitalOcean review.

If it is a container you run yourself, the self-hosting tools list is the other path, and it pays off only when someone will patch the host.

Skip Heroku when the front end is the product. A Next.js app is usually a closer call on the Vercel review and the serverless platforms roundup, because an always-on dyno is the wrong meter for a page.

Managed Postgres you want to shop on its own is the Postgres hosting page, with Supabase if the database should be the platform. Pipelines that outgrow review apps belong with the CI/CD tools list.

A monitor that pings an Eco app every minute will keep it awake and spend the hour pool, which is the same failure mode Heroku documents for uptime checks. Production alerts belong on the monitoring tools list, not on a cron that defeats sleep.

Dyno price changes show up in the Devshot brief. Subscribe free if you want that note in the inbox.