Render Alternatives in 2026
8 places to move a small app when idle services, previews or the $25 workspace fee add up
If your Render bill is mostly services that sit idle, the cheapest Render alternative for a small app with an API and PostgreSQL is Light Cloud at $5 a month, with a preview of the frontend and API for every branch included. Railway is the closest like-for-like move at $5 plus usage, and it keeps the cron jobs and private networking you may rely on today. Google Cloud Run, Heroku and DigitalOcean land between about $8 and $12. Vercel, Koyeb and Fly.io cost more for this app but solve different problems. The same app on Render is $13.30, or $38.30 once you want previews with a database.
We make Light Cloud, the first row below, so here is the method first. Every number links to the vendor's own page, and you can redo the table in about twenty minutes.
Why people look for a Render alternative
Render is a good platform, and nothing in this post says otherwise. People leave it for a few specific reasons, and they are the reasons I ranked on.
The first is idle cost. A paid Render service is a fixed instance: the smallest is $7 a month for 512 MB (pricing), billed whether or not anyone calls it, and Render's scaling docs describe no way to scale a paid service to zero. That is a fair deal for a busy API and a poor one for a staging copy that gets ten requests a day.
The second is the free tier's edges. Free web services spin down after 15 minutes without traffic and take "about one minute" to wake, and a free Postgres database expires 30 days after it is created (free tier docs). Render itself says not to run production on it.
The third is previews. On the plans Render introduced in April 2026, full-stack preview environments with services and databases need the Pro workspace, $25 a month flat, and the preview resources are billed like normal services (preview docs). The free Hobby workspace gets a preview of one service per pull request, without a database.
How we ranked
The reference app is the one most small teams run on Render: a static frontend, one API web service, a small PostgreSQL database and a custom domain, at about 1,000 API requests a day. It is the same app as in where to host a SaaS app, so the two posts agree on every number.
Every price is a list price from the vendor's own pricing or docs page, checked on 2026-10-13, in US dollars, smallest sensible tier, no trial credits. Rows are ordered by that monthly bill. Two columns show what decides the move for most people: whether the API costs anything while nobody calls it, and whether a pull request gets a preview of the frontend and the backend together without a plan upgrade. Whether that preview also gets its own database differs, and each entry says how.
Kept running all month, with no scale to zero, the same app gets the Always on prices in the table. Light Cloud comes seventh of eight there at about $56, because an always-on instance needs the $19 Starter plan and a Micro costs about $52 a month. Google Cloud Run can keep a minimum instance warm at its lower idle rate, about $5 a month at a quarter of a vCPU. Platforms that run the API only as functions have no documented way to keep it running, so they're listed last.
The ranking
1. Light Cloud
Best for: Render users who pay for services that sit idle most of the day.
The Lite plan is $5 a month and includes $5 of usage, a custom domain and one shared PostgreSQL database (pricing). My reference app uses about $4.33 of it: $4 for the database, about $0.20 for the API (1,000 requests a day at 0.2 s each is 1.7 instance-hours at $0.12), a few cents of build minutes and two cents per idle preview. Every container scales to zero by default, so a staging copy that nobody opens costs nothing, which is the line item Render can't remove. That is the case for hosting from $5 a month that bills by the hour a container actually runs.
Previews come on every plan, Free included: every branch you push gets the frontend and the API at their own URL, and pull request previews that nobody opens cost nothing to run. A preview uses the production database until you give it its own, so it is not the fresh database copy Render's Pro previews make. You can put a visitor password on any environment on any plan; the staging tutorial shows the five-minute setup. The database is Postgres next to your app, created in the same project; you copy its connection string into the app's DATABASE_URL.
Where it falls short of Render, plainly: there are no background workers, no cron jobs and no private networking, so services call each other over public HTTPS. The shared database tier runs in Belgium only. After an idle spell the first request waits for a container to start, 3.1 to 3.7 seconds when I measured it, which beats a free Render service's minute but is slower than an always-on instance. And an always-on instance, which needs Starter, costs about $52 a month, far more than Render's $7.
2. Railway
Best for: the closest like-for-like move, extras included.
Hobby is $5 a month and includes $5 of usage (docs). There are no fixed sizes: RAM is $10 per GB a month and CPU $20 per vCPU a month, billed for what the services actually use, and builds are free. If the API and Postgres average under about half a GB of RAM between them, the bill stays at $5. Postgres is a template service billed the same way.
What Render users will recognise: private networking, cron jobs and pull request environments that copy the whole app are on every plan (pricing), and you can set a hard usage limit from $10. Sleep is opt-in per service and kicks in 5 to 10 minutes after the last outbound traffic; Railway warns the first request may return a 502. Railway recommends Pro, $20 a month, for commercial apps. If your app depends on a nightly job or a queue worker today, Railway is the better move than us, and it costs the same.
3. Google Cloud Run, used directly
Best for: the lowest raw compute price, if you'll wire the rest up yourself.
Light Cloud's containers run on Cloud Run, so this is the do-it-yourself version of row 1. The free tier covers 180,000 vCPU-seconds and 2 million requests a month (pricing), which pays for the reference API many times over. For the database you'd use Cloud SQL, where the smallest shared-core instance is $0.0105 an hour, about $7.67 a month before storage (Cloud SQL pricing).
The work moves to you: a billing account, IAM, a Cloud SQL instance, and a custom domain, because Cloud Run's own domain mapping is in preview and Google calls it not production-ready. There are no pull request previews. Spend caps that pause Cloud Run at a budget became generally available on 2026-10-12 (release notes).
4. Heroku
Best for: the original git push workflow, with review apps.
An Eco dyno is $5 a month for 1,000 shared hours and sleeps after 30 minutes without traffic, but it is for personal apps only; Essential-0 Postgres is $5 (pricing). That is $10, or $12 with an always-on Basic dyno. Review apps can carry their own Postgres and are billed like normal apps.
The catch: a card is required before you deploy anything, and on 2026-02-06 Heroku moved to a sustaining engineering model, focused on stability and security rather than new features. Moving from Render to a platform that has stopped building is a choice to make with open eyes.
5. DigitalOcean App Platform
Best for: fixed monthly prices, close to how Render bills.
A 512 MiB container is $5 a month and a development database is $7, so $12 (pricing), with the static frontend on the free tier. Components in one app talk over a private network, and scheduled jobs are billed only while they run. Of the platforms here, it is the one that bills most like Render.
The development database has no backups by default and is deleted with the app, so a real product moves to managed Postgres at about $15. Scale to zero exists but is a private preview you request, and a sleeping service is still billed at 10% of its price. Previews per pull request are a GitHub Actions workflow you maintain, and you need a payment method to create anything.
6. Vercel
Best for: moving a Next.js frontend and its API routes.
A commercial app needs Pro, $20 a month per deploying seat with $20 of usage included (Pro plan), because the fair use guidelines keep Hobby to non-commercial use. Functions bill nothing between requests, previews come on every plan, and Postgres comes from a Marketplace partner such as Neon or Supabase, billed by them.
If your Render setup includes a worker that runs all day, Vercel is the wrong move, and Vercel says so: its own guide suggests that processes that must run continuously stay on Render, Railway or similar. A shared password on staging is $20 per project a month on Pro since the September 2026 change.
7. Koyeb
Best for: private networking, workers and basic auth on one paid plan.
Since Koyeb announced it is joining Mistral AI on 2026-02-17, new users must pick a paid plan with a card. Pro is $29 a month with $10 of compute included (pricing). A nano instance is $2.68 a month, and the smallest Postgres is $0.04 an hour while it is awake; it sleeps after 5 minutes without activity, and its compute is not billed while it sleeps. So the reference app is $29 plus whatever usage passes $10.
It has a lot of what Render users want: a private mesh between services, workers, scale to zero (public preview) with a 1 to 5 second cold start (docs), and HTTP basic auth from the CLI. Previews per pull request are a GitHub Actions tutorial from 2023, and there are no spend limits yet.
8. Fly.io
Best for: apps that need to run close to users in many regions.
The smallest always-on machine is $2.19 a month (pricing), and machines can stop when idle so you pay only for their disk. Postgres is the expensive part: Managed Postgres starts at $38 plus $0.28 per GB (docs), so about $40 for this app. Fly's self-managed Postgres is about $2 but officially unsupported.
Private networking between machines is on by default, in every region. There is no free tier for new accounts, preview apps come from a GitHub Action that deploys one app without a database, and Fly says it doesn't support billing alerts yet.
Where the others beat us
If you are on Render for background workers, cron jobs or private networking between services, we have none of the three, and Railway, DigitalOcean, Heroku and Koyeb have them today. Railway does it at our price. If your services are busy all day, Render's fixed $7 instance beats our scale-to-zero billing, and our always-on instance at about $52 a month can't compete with it. Need a fresh database for every preview? Railway and Render's Pro workspace make one. And if your users are spread across continents, Fly's regions are the better answer.
Where we come out ahead is the bill for things that sit idle: staging copies, previews nobody has opened since Tuesday, an API that is quiet at night. Render charges a fixed price for each of them; on Light Cloud each costs nothing until someone calls it, every branch gets its preview on the free plan, and the password on staging is one setting. If that is most of your Render invoice, you can deploy from GitHub, run both for a month and compare the two bills. The preview tutorial shows the setup in about ten minutes.
Which line on your Render invoice made you start looking?
