The best Heroku alternative in 2026: six options compared
Heroku moved to a sustaining engineering model in February 2026 and no longer sells Enterprise contracts to new customers, but card-paying customers keep the same service and prices. If you are moving anyway: Render is the closest like-for-like, Railway bills by usage, Fly.io is the cheapest in dollars, DigitalOcean is the simplest flat price, Coolify runs on your own servers, and Livops fits apps whose users are in Uzbekistan, at 39 credits a month (39,000 so'm) for an app.
By Livops team, the people who build and run LivopsUpdated
Heroku is not closing, but in 2026 it said it would put maintenance ahead of new features, and that is enough for many teams to look around. This page says what actually changed, what an app leaving Heroku needs from its next home, and how six alternatives compare on each provider’s own prices, read on 20 November 2026 — including where each of them is better than Livops, which wrote the page. It ends with how a Heroku app moves to Livops, step by step.
What changed at Heroku in 2026?
On 6 February 2026 Heroku announced that it is moving to a sustaining engineering model, focused on stability, security, reliability and support, with an emphasis on quality and operations rather than introducing new features[1]. Applications, pipelines, teams and add-ons are unaffected[1], and the blog still posts platform updates, one of them for October 2026[1]. Enterprise Account contracts are no longer offered to new customers; existing Enterprise contracts are honoured and may renew[1]. Customers who pay by credit card, existing and new, can keep using Heroku with no change to pricing, billing, service or day-to-day usage[1].
So nothing forces a move. The reasons people move anyway are the ones they had before — price and the region — and now the stated emphasis on keeping the platform running over adding to it.
What does an app leaving Heroku need?
Process types from a Procfile
A Heroku app declares its processes in a Procfile, one <process type>: <command> per line; web is the only type that receives HTTP traffic, and release runs during the release phase[3]. The next platform has to run your web and worker processes, and give you somewhere for the release command — usually a migration.
Config vars as environment variables
Heroku’s config vars, $PORT among them, reach the Procfile’s commands from the environment[3]. Any platform does the same; what you check is that the app reads PORT, and that secrets can be hidden once saved.
A Postgres you can move
Heroku Postgres exports with heroku pg:backups:capture and pg:backups:download, as a pg_dump file in the custom format, which pg_restore loads[4]. PGBackups are meant for databases up to 20 GB[4]; past that, plan the move with more care.
Always-on processes and zero-downtime deploys
On Heroku, Eco dynos sleep after 30 minutes of inactivity, Basic dynos stay on, and preboot with zero-downtime deploys starts at Standard-1X[2]. Know which of those you rely on before comparing prices.
A region near your users, and a way to pay
The platform’s regions decide how far every request travels, and its billing decides who on your team can pay for it.
The options at a glance
| Option | What it is | Smallest paid always-on app | What you still maintain |
|---|---|---|---|
| Heroku (staying) | The original platform, in sustaining engineering | Basic: $7 a month, 0.5 GB[2] | Your code |
| Livops | A platform; servers in Uzbekistan; pay in so’m | 39 credits (39,000 so’m) a month | Your code |
| Render | A platform with native runtimes and Docker | $7 a month: 0.5 CPU, 512 MB[5] | Your code |
| Railway | A platform billed by usage | Hobby: $5 a month, including $5 of usage[8] | Your code |
| Fly.io | Virtual machines billed by the second | $2.19 a month: shared-cpu-1x, 256 MB[10] | Your code, and its Docker image |
| DigitalOcean App Platform | A platform with container instances | $5 a month: 1 shared vCPU, 512 MiB[11] | Your code |
| Coolify | Open-source platform on your own servers | Self-hosted: free; Cloud: $5 a month for 2 servers[12] | The servers: OS updates, SSH, firewall, DNS[13] |
Other providers’ prices are from each provider’s own page, read on 20 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.
Each option
Heroku: staying is a real option
If you pay by card, Heroku says nothing changes for you[1], and the platform you know keeps running. Basic is $7 a month for 0.5 GB and always on, Eco $5 and sleeps after 30 minutes[2]; Heroku Postgres starts at $5 a month for Essential-0[2]. Where it is still ahead of everyone here is breadth: dynos up to 126 GB of memory in Performance-2XL[2] and Private and Shield spaces[2]. Move when there is a reason, not because of the headline.
Livops
Livops runs bots, apps and sites from a GitHub push, on servers in Uzbekistan. From Tashkent the first byte arrives in 10-20 ms, against 80-100 ms from a server in Frankfurt. It reads a Procfile, runs PostgreSQL, Redis, MongoDB and MySQL with backups, and bills in credits bought in so’m through Payme or Click, with no card. Where it is worse: there are no regions abroad, so for users in Europe or America every request travels further than on Render or Railway; an app’s memory stops at 2 GB; you get no root; and there is no free tier for apps.
Render
The closest to Heroku in shape: native runtimes for Node, Python, Go, Rust, Ruby and Elixir, plus custom Docker containers[5]. The smallest paid instance is $7 a month for 0.5 CPU and 512 MB[5], the Hobby workspace is $0 plus compute and Pro $25 a month[5], and Postgres starts at $6 a month for 256 MB[5]. Regions are Oregon, Ohio, Virginia, Frankfurt and Singapore[7]. Better than Livops for users in those places, and for anyone who wants a free web service to start with[6].
Railway
Railway bills by the second for what a service uses — about $10 per GB of memory and $20 per vCPU a month — and Hobby, $5 a month, includes $5 of that[8]. A Hobby service can grow to 48 vCPU and 48 GB[8], far past Livops’s 2 GB. Regions are California, Virginia, Amsterdam and Singapore[9]. Payment is by card[8].
Fly.io
The lowest dollar prices here: shared-cpu-1x with 256 MB is $2.19 a month, 512 MB $3.69, 1 GB $6.70, billed by the second while running[10]. There is no free tier, but a personal organisation’s bill under $5 a month is waived[10].
DigitalOcean App Platform
A flat, predictable price: $5 a month for a fixed shared instance with 1 vCPU, 512 MiB and 50 GiB of transfer, limited to one instance[11]. A development database of 512 MiB is $7 a month[11]. Up to 3 static sites are free[11].
Coolify
Coolify is open source and self-hostable: it deploys apps from Git, a Dockerfile, Docker Compose or an image to servers you connect over SSH[13]. Self-hosted it is free; Coolify Cloud is $5 a month for two servers and $3 for each more, and either way you bring the servers[12]. So the bill is your servers plus, on Cloud, the subscription — and the operating system, SSH, firewall and DNS are yours to look after[13].
Which one should you choose?
- Users in Europe or America, card payment, least change: Render, or Railway if you prefer paying for usage.
- The lowest monthly dollar figure: Fly.io.
- One flat price per app, nothing to think about: DigitalOcean App Platform.
- Your own servers, no platform fee: Coolify.
- Users in Uzbekistan, paying in so’m: Livops.
- Large dynos, Private Spaces, or an Enterprise contract you already have: stay on Heroku.
Where can you run an app for free?
- Livops has no free tier for apps. On an account that has not paid yet, the first bot or app runs for 15 minutes on a zero balance, once. Static sites are free, and so is one 500 MB database per team.
- Heroku lists no free dyno; the cheapest is Eco at $5[2].
- Render gives each workspace 750 free instance hours a month; a free web service spins down after 15 minutes without inbound traffic, and a free Postgres expires after 30 days[6].
- Railway has a Free plan with $1 of usage a month that sleeps after 5 to 10 minutes without outbound traffic, and a $5 trial for 30 days with no card[8].
- Fly.io has no free tier: a $1 trial for 7 days, and a personal bill under $5 a month is waived[10].
- DigitalOcean App Platform is free for up to 3 static sites[11].
- Coolify self-hosted is free[12]; the server is not.
Moving from Heroku to Livops
- Connect the repository. In the cabinet, create a project from the GitHub repository Heroku deployed. Livops detects the framework; a
Procfileis read too — aweb:line is a server, aworker:line a process with no address, such as a bot. - Copy the config vars. Put each one under Variables; mark secrets as secret and their values are never shown again.
PORTis set by the platform (3000 unless you change it), as on Heroku. - Move the database. Run
heroku pg:backups:captureandheroku pg:backups:download[4]. In the project, add PostgreSQL (15, 16 or 17) under Databases;DATABASE_URLis written into the app’s variables by itself. Open Connect from your computer, start the SSH tunnel it shows, and load the file withpg_restorethrough it. Redis, MongoDB and MySQL are there too. - Replace the release phase. A
release:line is not run. Put the command in Pre-deploy command: it runs once before each new version starts, and if it fails, the old version keeps serving. - Replace scheduled jobs, pull request apps and staging. A scheduled job is a
cronservice with itsscheduleinlivops.json, on UTC. Pull request previews open an environment per PR, and astagingenvironment promotes its tested release to production without rebuilding. - Point the domain. Add it under Domains: a
CNAMEtocname.livops.appfor a subdomain, anArecord for the apex, and a TXT record to prove ownership. HTTPS is issued by itself.
To fix the commands rather than rely on detection, put livops.json in the root:
{
"kind": "web",
"build": "npm run build",
"start": "node dist/server.js",
"healthPath": "/healthz"
}
A new version takes traffic only once it answers on PORT; the old one keeps serving until then, and for 15 seconds after, before it gets SIGTERM. A crashed process is started again, and a failed build leaves the running version alone.
An app is 39 credits a month (39,000 so’m), a bot 19 credits, a static site free; a 1 GB database is 9 credits. One credit is 1,000 so’m, and a plan gives more credits than it costs. See Pricing, Databases and Environments.
Questions
Is Heroku shutting down?
No. On 6 February 2026 Heroku said it is moving to a sustaining engineering model focused on stability, security, reliability and support, and that it will no longer offer Enterprise contracts to new customers. Customers who pay by card keep using it with no change to pricing, billing or service. No end date has been announced.
Which Heroku alternative is closest to Heroku?
Render: native runtimes for the usual languages and Docker, managed Postgres, and a $7 instance with 512 MB beside Heroku's $7 Basic dyno with 0.5 GB. Railway is as easy but billed by usage. Livops is the closest for an app whose users are in Uzbekistan.
Which is the cheapest?
In dollars, Fly.io: $2.19 a month for its smallest machine, and a personal bill under $5 a month is waived. Coolify's software is free if you already pay for a server.
Does Livops read my Procfile?
Yes. A web line is a server and a worker line a process with no address, such as a bot, as on Heroku. A release line is not run: put that command, a migration say, in the project's pre-deploy command, which runs once before each new version and keeps the old one serving if it fails.
How do I move a Heroku Postgres database to Livops?
Take a backup with heroku pg:backups:capture and download it with heroku pg:backups:download; it is a pg_dump file in the custom format. Add PostgreSQL to the Livops project, open its SSH tunnel from your computer, and restore the file with pg_restore through it.
Can I pay Livops by card in dollars?
No. Livops sells credits in so'm through Payme and Click, Uzbekistan's payment services, and no card has to be linked. If you can only pay by international card, Render, Railway, Fly.io or DigitalOcean will suit you better.
Who wrote this comparison?
The Livops team, so read the Livops rows with that in mind. Every price and limit of another provider links to that provider's own page, with the day we read it, and each section says where that provider is better than us.
Sources
- Heroku — An Update on Heroku (6 February 2026) (heroku.com). Checked .
- Heroku — Pricing (heroku.com). Checked .
- Heroku Dev Center — The Procfile (devcenter.heroku.com). Checked .
- Heroku Dev Center — Importing and exporting Heroku Postgres databases (devcenter.heroku.com). Checked .
- Render — Pricing (render.com). Checked .
- Render — Deploy for free (render.com). Checked .
- Render — Regions (render.com). Checked .
- Railway — Pricing (railway.com). Checked .
- Railway — Deployment regions (docs.railway.com). Checked .
- Fly.io — Pricing (docs.fly.io). Checked .
- DigitalOcean — App Platform pricing (digitalocean.com). Checked .
- Coolify — Pricing (coolify.io). Checked .
- Coolify — Introduction (coolify.io). Checked .
Put your project online today
Connect GitHub or drop a folder. No card is asked for.
Move your app to LivopsRelated
- Node.js hosting in 2026: how to deploy an Express appA Node.js server in production needs one long-running process that listens on the port it is given, restarts when it crashes and exits cleanly on SIGTERM. On Livops you push a repository with package.json and it runs as a web app for 39 credits a month (39,000 so'm). Here is what Node needs, and how a VPS, Render, Railway, Fly.io, DigitalOcean and Heroku compare.
- Go hosting in 2026: how to deploy a Go appA Go web app compiles to one binary, so hosting it means building that binary, running it on the port it is given and shutting it down with http.Server.Shutdown. On Livops you push a repository with go.mod: it is built with CGO off into a static binary and runs as a web app for 39 credits a month (39,000 so'm). Here is what Go needs, and how a VPS, Render, Railway, Fly.io and DigitalOcean compare.
- Rust web app hosting: how to deploy an axum or Actix Web appA Rust web app is one release binary that binds 0.0.0.0 on the port it is given and shuts down on SIGTERM. The hard part is the build: a first release build takes minutes, so the host must keep its cache. On Livops you push a repository with Cargo.toml, it is built with cargo build --release and runs as a web app for 39 credits a month (39,000 so'm).
- Docker hosting: how to deploy a Docker container or a DockerfileTo host a container you need a host that builds or pulls the image, starts its CMD, sends traffic to the port it listens on and stops it with SIGTERM. On Livops a Dockerfile at the root of the repository is built on Livops's servers and runs for 39 credits a month (39,000 so'm); a public image from Docker Hub, GHCR or Quay runs without a build. Here is what a container needs, and how a VPS, Render, Railway, Fly.io, DigitalOcean and Heroku compare.
- Deploy from Claude Code: connect Livops over MCPRun one command, claude mcp add --transport http livops https://livops.uz/api/mcp, then sign in through /mcp. From then on Claude Code can list your projects, deploy, read the build log, explain a failure and roll back, as you and only in the team you picked.