The main alternatives to a click-through app host are managed platforms in the classic PaaS style, newer developer clouds that deploy from a Git repo, and self-hosted tools that run on your own server. Start by checking what kind of free offer your app needs, because a free static site, a free serverless project and a free starter are three different deals.
Maybe your side project grew up, maybe your static site needs a backend now, or maybe you want your hosting somewhere else for your own reasons. Whatever the trigger, if you're leaving Render, the nine platforms below are the ones worth a look, and they split neatly by how much of the server you want to think about.
They're in no particular order and the list is alphabetical. Everything in the descriptions comes from each vendor's own website, and anything that reads like a promise is their promise.
Free isn't one thing on these platforms
This is where most people trip up. The home page of the platform you're probably leaving offers free static sites for good, but it doesn't describe running a web service as free there. So if your app has grown from a static site into something with a server and a database, check what that move means on your current plan before you assume you have to leave at all.
Then look at what the alternatives mean by free, because it isn't the same deal twice. Leapcell's page says you can deploy up to 20 projects free and are charged when requests come in (as of Nov 2026). Fly.io says you can start free and pay for the seconds your machines run. Scalingo's description simply says you can get started for free.
Those are three different models: a capped number of serverless projects, usage you pay for by the second, and a starter tier. A hobby API that sits idle most of the day fits one of them far better than the others. Work out how your app behaves across a normal week, then compare.
Who each platform suits
| Tool | Kind of platform | Who it suits |
|---|---|---|
| Clever Cloud | Managed European cloud | Teams that want hosting run for them |
| Dokploy | Self-hosted open-source PaaS | Developers happy to run their own server |
| Fly.io | VM-based app platform | Apps and agents on isolated machines |
| Heroku | Managed PaaS | Teams wanting a long-standing managed platform |
| Koyeb | Serverless app platform | Docker apps across GPUs and CPUs |
| Leapcell | Serverless PaaS | Side projects and APIs that sit idle |
| Railway | Developer cloud platform | Connecting a repo and shipping fast |
| Scalingo | European PaaS and databases | Teams who want hosting kept in Europe |
| Sevalla | All-in-one app platform | Apps, databases and storage in one place |
The nine platforms, one line each
Clever Cloud
Best for: Developers who want a fully managed European cloud that hosts, deploys and maintains their apps for them (vendor wording).
Dokploy
Best for: Running your own open-source PaaS on your own server, deploying with Nixpacks, buildpacks, a Dockerfile or Docker Compose.
Fly.io
Best for: Apps, agents and databases that need fast, hardware-isolated VMs, where the vendor says you pay only for the seconds machines run.
Heroku
Best for: Teams that want a long-standing managed PaaS with data services and managed inference sitting next to app hosting.
Koyeb
Best for: Git-push deploys of Docker containers or common languages without changes, across GPUs, CPUs and accelerators in many locations (vendor claim).
Leapcell
Best for: Side projects and APIs on serverless deployment, where the vendor says you're charged only when requests come in.
Railway
Best for: Connecting a repo and letting the platform work out the config, with instant previews, databases and automatic scaling (vendor claim).
Scalingo
Best for: European teams wanting PaaS and managed databases on what the vendor calls a sovereign cloud, with Git deploys and autoscaling.
Sevalla
Best for: Keeping apps, databases, storage and static sites on one platform instead of stitching several services together.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Managed, modern or self-hosted: how hands-on do you want to be?
Managed PaaS in the classic style. Heroku is the long-standing name here, now adding AI and data services as product pillars. Clever Cloud and Sevalla both aim to take the operations work off your plate, and the European platform named above suits teams who care where their data lives. You push code, the platform runs it, and you give up some control in return for not managing servers.
Modern developer platforms. Railway leads with connecting your repo and letting it work out the config. Koyeb deploys Docker containers or common languages by Git push, including on GPUs. The serverless and per-second options from the free section above also live here. These are quick to start and suit small teams who ship often.
Self-hosted. Dokploy is open source and runs on your own server, so you get a platform-style dashboard without handing your apps to someone else. The trade is that you're now the one keeping the server patched and backed up.
Your moving-day checklist
- List every service you run: web apps, background workers, cron jobs, databases and static sites.
- Export your environment variables and secrets, and keep them somewhere safe outside the old dashboard.
- Take a full database backup and test a restore on the new platform before you switch traffic.
- Check how the new platform builds your app: buildpacks, a Dockerfile or its own detection.
- Lower the DNS time-to-live a day ahead, so the switch takes effect quickly.
- Keep the old service running until the new one has handled real traffic for a few days.
My advice if you're switching app hosts
Move one service first, ideally something small that real users touch, and watch it for a week before you move the rest. Deploy speed is easy to compare on day one. What matters more is how the platform behaves when a build fails, a database fills up or you need help at the weekend, and you only learn that by running something real.
If you'd like a wider view, my list of Vercel alternatives covers platforms built for front-end work, my roundup of cloud server hosting suits apps that have outgrown a PaaS, and my guide on how to choose a hosting provider has the questions to ask any host.
Do you make app hosting or deployment platforms? Tool makers can ask to be considered for a featured place on this list.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What is a PaaS?
A platform as a service runs your app for you. You push code, and the platform builds it, runs it and scales it, so you don't manage the servers underneath.
Is self-hosting a PaaS worth it?
It can be if you're comfortable running a server. A self-hosted platform gives you control and keeps your apps on your own machine, but patching, backups and uptime become your job.
Can I move a database from one host to another?
Yes. Take a full backup, restore it on the new platform, test your app against it, then switch over. Plan a short freeze on writes while you make the final copy.
What's the difference between serverless and a VM-based platform?
Serverless platforms run your code when requests come in and can scale to nothing when idle. VM-based platforms keep a machine running for you, which suits apps that need to stay warm.
Do I need Docker to move my app?
Not always. Many platforms detect your language and build it for you. A Dockerfile makes your app easier to move between hosts, though, so it's worth adding if you plan to switch again.
Which host is best for a side project?
Look for a free offer that matches how your app runs. A static site, an idle API and an always-on server each fit a different kind of free tier.
