A Heroku Alternative For Your App And Its Front End

Choosing a Heroku alternative? Sort your app into parts that need a server and parts that don't, then compare Render, Railway, Fly.io and more. Nov 2026.
The OxyPages Team · · 9 min read
You probably didn't build your Heroku app. A freelancer or an agency did, years ago, and handed you a login and a monthly bill. It still works. Then you read a headline about Heroku winding down, and now you're wondering whether to move.
Most advice on picking a Heroku alternative is written for the developer who built the thing. It assumes you know which parts of your app are which.
You don't need to read code to work that out. Every Heroku app is a handful of pieces, and each piece either serves files or runs code. Files can live almost anywhere, often for free. Code needs a server, and that's where the real choice is.
So this post does the sorting first, then the shopping. Every price below comes from the vendor's own pricing page, as of November 2026. I run a small static hosting service, so I'll say plainly where it fits, and most of your app is on the side where it doesn't. For static hosts alone, every static host compared side by side has the full table.
TL;DR: Heroku hasn't announced a shutdown. On 6 February 2026 it moved to "sustaining engineering", meaning stability and security work rather than new features, and stopped offering Enterprise contracts to new customers. There's been no free tier since 28 November 2022, and the cheapest always-on dyno is Basic at $7 a month. Before choosing, split your app into parts that serve files (a marketing site, a React front end) and parts that run code (the app server, background workers, the database). The code parts need an app platform such as Render, Railway, Fly.io, DigitalOcean App Platform or Northflank. The file parts can go to any static host, and a static host can't run your server or database at all.
Why Are People Leaving Heroku?
People leave Heroku for three reasons: the free tier is gone, the cheap tier has strings attached, and the February 2026 announcement made long-term plans feel shaky.
The free tier ended on 28 November 2022, when Heroku started shutting down free dynos and free databases.
The cheapest plan now is Eco, at $5 a month. That buys a pool of 1,000 dyno hours shared across every Eco dyno on your account, not $5 per app. An Eco web dyno sleeps after 30 minutes with no visitors, so the next person waits while it wakes. When the hours run out, every Eco dyno sleeps until next month, and you can't buy more. Heroku's own docs also say "Only personal apps can use Eco dynos." A business app starts at Basic, $7 a month per dyno.
Then, on 6 February 2026, Heroku announced a "sustaining engineering model focused on stability, security, reliability, and support ... rather than introducing new features." Tech press read that as a wind-down. Heroku's own post says it "remains an actively supported, production-ready platform," and it has shipped updates since.
Who Should Stay On Heroku
Heroku still does the original job well. You push code and it runs, with automatic OS patching, certificates and Review Apps (a preview copy of the app for each change). Teams tied into Salesforce get those integrations built in.
If your app works and your bill is a few dyno charges, staying is reasonable. There's no deadline. Move when there's a reason, not because of a headline.
Which Parts Of Your App Need A Server?

Any part that has to think when a visitor arrives needs a server; any part that hands out the same files to everyone doesn't. Open your Heroku dashboard, go to the Resources tab, and sort what you see:
- A marketing site or landing pages. Usually plain HTML, CSS and images. If it's on its own dyno, it's a file server, and it's the easiest thing to move.
- A React, Vue or Vite front end. Once built, it's a folder of files that runs in the visitor's browser. Static, as long as it talks to an API somewhere else.
- The web dyno running Rails, Django, Express or similar. This is the app server. It checks logins, reads the database and builds pages per request. Needs a server.
- Worker dynos. These do background jobs like sending reminder emails or processing uploads. Needs a server.
- Heroku Scheduler jobs. Timed tasks, such as a nightly report. Needs something that runs on a schedule.
- Heroku Postgres or Key-Value Store. Your data. Needs a managed database, and it's the riskiest piece to move.
- Other add-ons, like email or logging. Most are separate companies that sell directly too, so they come with you.
Items one and two are files. Items three to six are code and data. MDN's introduction to what server-side code does goes deeper, and what a static website is, and what it can't do is the short version.
The Platforms That Can Run Your App Server
These five run code the way Heroku does: connect a repository or a Docker image and they keep it running. All prices are monthly and as of November 2026.
Render
Render suits anyone who wants the closest thing to Heroku's dashboard and Git-push workflow. Its free Hobby workspace includes one 512 MB web service that sleeps after 15 minutes idle and takes about a minute to wake. An always-on web service starts at $7 a month, and paid Postgres from $6 a month.
The catch: Hobby includes only 5 GB of bandwidth, then $0.15 per GB, and free Postgres expires after 30 days, with deletion 14 days later.
Railway
Railway suits developers who like usage-based billing. New accounts get a one-time $5 credit for 30 days, then a Free plan with $1 of credit a month and no custom domain. Hobby is a $5 monthly minimum that includes $5 of usage.
The catch: usage above the included amount is added on top, and egress costs $0.05 per GB.
Fly.io
Fly.io suits apps that need to run close to users in several regions. There's no free tier: new accounts get $1 of credit for 7 days, and bills under $5 are waived once a card is on file. The smallest always-on machine is about $2.19 a month in its US regions.
The catch: managed Postgres starts at $38 a month, and nearly everything happens in a terminal.
DigitalOcean App Platform
DigitalOcean suits people who want a big, established provider. Three static-site apps are free, with 1 GiB of transfer each. Paid apps start at $5 a month for one shared CPU and 512 MiB of memory, and a dev Postgres database is $7 a month.
The catch: the free tier is static sites only, and DigitalOcean asks for a payment method to verify your identity at sign-up.
Northflank
Northflank suits teams who want a free tier that doesn't sleep. Its Sandbox is free with no card: two services, two jobs and one database, up to about $20 a month of resources, "always on, no sleeping." Paid compute plans start at $12 a month.
The catch: it's more technical than Render, and egress is $0.06 per GB.
Where The Front End Can Go Instead

The static parts of your app don't need any of those platforms. A built front end or marketing site can sit on a static host for free or a few dollars a month, and keeps calling your API wherever it ends up.
Cloudflare Pages has the strongest free tier: unlimited static bandwidth and custom domains. Netlify's Free plan allows commercial projects, but deploys and bandwidth spend from 300 monthly credits, and sites pause when they run out.
OxyPages is the one I run. Free hosts one site with HTTPS and 5,000 page views a month, but it's personal, non-commercial use only, with no custom domain. A business site needs Lite, $5 a month or $48 a year, which adds custom domains and commercial use, with no bandwidth bills. It builds React, Vue, Vite and Astro output from GitHub.
The limit, plainly: OxyPages can't run your Rails or Node server, your workers, your scheduled jobs or your database. No static host can. For a React app specifically, the options for hosting a React app goes deeper.
Side By Side: Free Tier, Price And Catch
Every figure is from the vendor's pricing page, as of November 2026. Prices are monthly.
| Platform | Runs your app server? | Free tier | Cheapest always-on app | The catch |
|---|---|---|---|---|
| Heroku | Yes | None since Nov 2022 | Basic dyno, $7 | Sustaining engineering since Feb 2026 |
| Render | Yes | 1 sleeping web service, 5 GB bandwidth | $7 web service | Free Postgres deleted after 30 + 14 days |
| Railway | Yes | $1 credit a month after trial | $5 minimum, usage on top | Egress metered at $0.05/GB |
| Fly.io | Yes | None ($1 trial, bills under $5 waived) | About $2.19 machine | Postgres from $38, CLI-driven |
| DigitalOcean App Platform | Yes | 3 static apps, 1 GiB each | $5 container | Card used to verify identity |
| Northflank | Yes | 2 services + 1 database, always on | $12 plan | More technical, $0.06/GB egress |
| Cloudflare Pages | Front end only | Unlimited static bandwidth | Free | Server code means learning Workers |
| OxyPages | Front end only | 1 non-commercial site, no custom domain | $5 Lite | No servers, functions or databases |
Picking A Heroku Alternative For A Real App
Here's a typical setup. Say a freelancer built your tutoring company a booking app in 2020. The Resources tab shows a Basic web dyno running Rails ($7), a Basic worker dyno sending reminder emails ($7), Heroku Postgres Essential-0 ($5), and the marketing site on its own Basic dyno ($7). That's $26 a month.
That's one file server and three pieces of code and data. Here's the order I'd move them in:
- Move the marketing site first. It's the lowest risk. Put it on a static host, check every page, then point the domain at it.
- Pick one platform for everything else. The web dyno, worker and database should move together, ideally to one provider, so they share a private network.
- Copy the config vars. Heroku stores passwords and API keys as config vars. Each one needs re-entering on the new platform, or the app won't start.
- Rehearse the database copy. Postgres has standard dump and restore tools that work between any two providers. PostgreSQL's guide to SQL dumps Do a test copy and time it.
- Do the real switch in a quiet hour. Put the Heroku app in maintenance mode, dump the database, restore it, start the new app, then move the domain.
- Keep Heroku for a week. Scale the old dynos down, but don't delete the app until you're sure nothing is missing.
The marketing site alone saves $7 a month, and it no longer goes down when the app does.
What To Do Next
Start with the Resources tab and the seven-item list above. Label each dyno and add-on "files" or "code", and send that list to whoever maintains the app.
If the app server is the reason you're moving, Render is a Heroku alternative that will feel the most familiar, and Railway or Fly.io suit a developer who wants more control. If a dyno only serves files, it doesn't need to be a dyno. Put the static front end on a static host and keep your server budget for the code that needs it.
FAQ
Is Heroku Shutting Down?
No shutdown date has been announced. On 6 February 2026 Heroku moved to a sustaining engineering model, focused on stability and security rather than new features, and stopped offering Enterprise contracts to new customers. Card-paying customers, new and existing, saw no change.
Is There Still A Free Heroku Plan?
No. Heroku ended its free dynos and free databases from 28 November 2022. The cheapest plan is Eco at $5 a month for a shared pool of 1,000 dyno hours, and it's limited to personal apps.
What Is The Easiest Alternative To Heroku For A Non-Developer?
Render feels the most familiar: a dashboard, Git-connected deploys and managed Postgres in one place. Moving the database is still a job for whoever built the app. Your part is knowing which pieces exist and where they should go.
Can A Static Host Run My Heroku App?
Only the parts that serve files, such as a marketing site or a built React front end. Anything that runs code when a visitor arrives, like a Rails or Node server, a worker or a database, needs an app platform. A static host can't run those on any plan, so it's a Heroku alternative for your front end only.