Best Heroku Alternatives for Indie Hackers in 2026 (Now That Heroku Stopped Building)

On February 6, 2026, Heroku published a blog post announcing its move to a "sustaining engineering model." Translated from corporate: security patches continue, new features stop, and Salesforce won't sign new Enterprise contracts. Your dynos keep running. The platform stops moving.

That announcement settles a question indie hackers have been circling since the free tier died in November 2022. It's not "is Heroku too expensive?" anymore. It's "why pay premium prices for a platform in maintenance mode?" A small always-on app with a worker, Postgres, and Redis costs about $22 a month on Heroku, and the number only grows from there: the first real production tier of Postgres alone is $50.

My pick for most people is Railway. It's the closest thing to the Heroku workflow, usually at half the price. But there are four destinations worth knowing, and the right one depends on how much ops work you're willing to own.

Quick Verdict

What Does "Sustaining Engineering" Actually Mean for Your App?

Nothing breaks tomorrow. Heroku's own announcement is explicit: credit card customers, existing and new, keep the same pricing, billing, and service. Apps, pipelines, and add-ons all keep working.

What changes is the trajectory. No new features means the platform slowly drifts behind: new language runtimes arrive late or never, the developer experience stays frozen in 2023, and compliance capabilities stop evolving. Salesforce is pointing its investment at AI products instead. There's a telling precedent inside the same announcement: Enterprise sales are closed to new customers, which is historically how large companies begin a multi-year product wind-down.

So the migration question isn't urgent. It's directional. If you're starting something new, you shouldn't start it on Heroku. If you're running something old, you have time to move deliberately, and the four options below cover every migration style.

Railway

Railway is what people mean when they say "the new Heroku." Connect a GitHub repo, Railway detects the framework and builds it, no Dockerfile needed. Postgres, MySQL, Redis, and MongoDB are one click each. Preview environments spin up per pull request. It's the same push-and-forget promise, executed with a 2026-grade dashboard.

Pricing is the part to actually understand. There's a 30-day trial with a one-time $5 credit, then plans start at Hobby, $5 a month with $5 of usage included. Usage is billed per second on what your containers actually consume: roughly $20 per vCPU and $10 per GB of RAM per month at full utilization. A small Laravel or Node app idling at 100MB of RAM costs very little; the $5 Hobby credit genuinely covers light projects. A realistic small production setup, web service, worker, and a modest Postgres, lands around $10 to 20 a month. Compare that to $22 minimum on Heroku for less flexibility. Railway's own pricing page quotes a customer who cut hosting costs 75% moving off Heroku. Pro is $20 per seat with $20 of usage included when you need teammates.

The honest cons. Usage-based billing cuts both ways: a memory leak or a traffic spike shows up on your invoice, and Railway has no hard spending cap below the plan level, so set up usage alerts on day one. Reliability has also had wobbles; a December 2025 incident paused builds across the EU West region, and uptime-sensitive teams should read the status page history before committing. I compared Railway head to head with the other managed options in my Railway vs Render vs Fly.io comparison if you want the full breakdown.

Who should not use Railway: anyone who wants a fixed, predictable invoice. That's Render's job.

Render

Render is the plan-based counterpart. Instead of metering your usage, you pick an instance size per service and pay that number. A Starter web service is $7 a month, always-on, no sleeping. Managed Postgres starts at $6. Background workers and cron jobs are first-class service types. The mental model is Heroku's, with prices from a decade earlier.

Render is also the only managed option here with a real free tier: free web services (they spin down after 15 minutes of inactivity and take up to a minute to wake, very Eco-dyno energy), 750 free instance hours a month, free static sites, and a free 1GB Postgres. The catch you must know: free Postgres databases are deleted after 30 days. Not paused. Deleted. Prototype on it, but put anything you care about on the $6 paid tier.

One 2026 change makes Render better for small teams: workspace plans dropped per-seat billing. Hobby workspaces are free, and the Pro workspace is a flat $25 a month with unlimited members, replacing the old $19-per-user Professional plan. Legacy workspaces migrate automatically by August 1, 2026. If you read an older comparison complaining about Render's seat fees stacking up, that complaint is now outdated.

So a Heroku-equivalent stack, web service $7, worker $7, Postgres $6, comes to about $20 a month on a free Hobby workspace, roughly matching Heroku's price with a modern platform that's actively shipping. The trade against Railway: less efficient for spiky or idle workloads, since you pay for the instance whether it's busy or not.

Who should not use Render: high-bandwidth apps on the cheap tiers. Included bandwidth is limited and overages add up, so check the numbers if you serve heavy media.

Fly.io

Fly.io is the option for a specific reason: running your app in multiple regions, close to users. Machines are micro-VMs deployed across 30+ regions with anycast routing. If your users are split between the US, Europe, and Asia and latency is a product feature, nothing else on this list does what Fly does.

Pricing is pure pay-as-you-go, billed per second. The smallest always-on machine (shared CPU, 256MB) is about $1.94 a month, volumes are $0.15 per GB, and a realistic single-region production app with a database lands in the $10 to 20 range. Know the 2026 fine print: there's no free tier for new accounts anymore (the old three-free-VMs allowance is grandfathered for legacy users only), dedicated IPv4 addresses cost $2 a month per app, and volume snapshots started incurring charges in January 2026.

The bigger caveat is operational. Fly's classic Postgres is not a managed database; it's Postgres running on your machines, and backups, upgrades, and failover are your responsibility (a managed Postgres offering exists, billed separately). Fly also assumes more comfort with infrastructure thinking, machines, volumes, regions, than either Railway or Render. Coming from Heroku's fully managed world, that's a real step, and community threads through 2025 flagged reliability grumbles alongside the pricing changes.

Who should not use Fly.io: single-region apps that just need a web server and a database. You'd be taking on infrastructure complexity for a multi-region capability you're not using.

Coolify + Hetzner

This is the money option. Coolify is an open source, self-hosted platform: install it on any VPS and you get git-push deploys, automatic SSL, preview environments, and one-click Postgres, Redis, and 300+ other services, on hardware you control. It crossed 55,000 GitHub stars in 2026, making it the most popular self-hosted PaaS by a wide margin.

Pair it with Hetzner and the economics get silly. A CX23 instance (2 vCPU, 4GB RAM, 40GB SSD) costs €5.49 a month, and that single box comfortably runs a web app, a queue worker, Postgres, and Redis. That's the entire $22 Heroku starter stack, plus room for two more side projects, for roughly the price of one Basic dyno. Even after Hetzner's 2026 price adjustments, nothing managed comes close per euro. Coolify itself is free self-hosted forever; if you want the control plane managed for you, Coolify Cloud is $5 a month for two connected servers.

Now the honest part, because this pitch always sounds too good: you are the ops team. You patch the OS, you configure the firewall, you own the backup strategy, and when the server misbehaves at 2am, there's no support ticket, just you and the logs. Coolify removes maybe 80% of the daily friction, and it's genuinely impressive software, but the remaining 20% is real responsibility that Railway and Render charge you to make disappear. Budget a weekend for initial setup and a couple of hours a month after that.

Who should not use this: anyone whose time is currently worth more than the savings, or who has never secured a Linux server. There's no shame in paying $15 a month to never think about fail2ban.

What Does the Same App Cost on Each?

Take the standard indie stack: one web service, one background worker, a small Postgres, and Redis, running always-on.

On Heroku that's two Basic dynos at $7 each, Essential-0 Postgres at $5, and the Key-Value Mini at $3: $22 a month, with a 1GB database and no failover. On Render, roughly $20 with services that Heroku would charge $25-plus for. On Railway, typically $10 to 20 depending on actual consumption, less if your app idles quietly. On Fly.io, a similar $10 to 20 for one region, growing with each region you add. On Coolify plus a Hetzner CX23, about €6 with an IPv4 address, plus your time.

The pattern: every option is cheaper than Heroku, and every option is on a platform that's still being built. That second part is the one Heroku can no longer say. It's the same trap I covered with Vercel's pricing cliffs: the platform you start on shapes your costs for years, so pick one with a future.

flowchart TD
    A{Comfortable managing a Linux server?} -- yes --> B[Coolify + Hetzner]
    A -- no --> C{Users spread across continents?}
    C -- yes --> D[Fly.io]
    C -- no --> E{Prefer fixed monthly bill?}
    E -- yes --> F[Render]
    E -- no --> G[Railway]

How Do You Choose?

Start with the ops question, because it filters hardest. If you can run a server, Coolify plus Hetzner wins on cost, especially once a second and third app share the box. If you can't or won't, you're choosing between managed platforms, and the split is billing philosophy: Railway meters what you use, Render charges what you provision. Spiky traffic and idle side projects favor Railway. Steady production traffic and budget predictability favor Render. Fly.io only enters the conversation when multi-region is a genuine product requirement, not a nice-to-have.

And migration effort is lower than you think for all four. Heroku apps are twelve-factor by design: environment variables, a Procfile, a Postgres URL. Every platform here imports that shape almost natively. Export your config with heroku config, capture a database backup with heroku pg:backups:capture, and most single-app migrations finish in an afternoon.

Final Recommendation

For most indie hackers leaving Heroku, use Railway. Same workflow, half the cost, actively developed.

Use Render if you want a fixed number on your invoice and a free tier for prototypes. Use Fly.io only if multi-region latency actually matters to your product. And if you're the kind of person who reads server logs for fun, Coolify on a Hetzner box will host your entire portfolio of projects for less than a Netflix subscription.

Staying on Heroku is the one choice I'd push back on for anything new. The platform works, but you'd be building on ground that's officially stopped moving.

Made the jump already? Tell me where you landed and what the bill looks like on Twitter @devtoolpicks.