A Render Alternative For Your Front End And Your API

Render cut Hobby bandwidth to 5 GB in April 2026. A Render alternative for each half of a small SaaS, the front end and the API, priced as of November 2026.
The OxyPages Team · · 8 min read
You opened your Render invoice, saw a bandwidth line you didn't expect, and started looking at other hosts. Or you got the email that your free services were suspended for the rest of the month, API included, because a static site used up the pool.
Both come from the same change. On 23 April 2026 Render moved to new plans, and the free Hobby workspace now includes 5 GB of bandwidth a month, then $0.15 per GB. Static sites draw on that same pool.
I've used Render myself. Our own API ran there until September 2026, when we moved it onto a server we were already paying for, because that had become the cheaper option.
So before you hunt for a Render alternative for everything, look at the split. A small SaaS on Render is usually a static front end, a web service for the API, and Postgres. Those three halves have different needs, and the cheapest fix is often moving one of them, not all three.
This post covers why people leave, who should stay, six alternatives with real prices as of November 2026, and a worked example.
TL;DR: Render's April 2026 plans removed per-seat fees (Pro is now $25 a month flat) but cut Hobby bandwidth to 5 GB, then $0.15 per GB, shared by static sites and services. Free web services still sleep after 15 minutes and free Postgres expires after 30 days. Teams running several services should probably stay. A solo developer can often move just the front end to a static host with free or flat-priced bandwidth and keep the API where it is. For the API itself, Railway, Fly.io, Northflank and DigitalOcean App Platform are the main options.
If all you run on Render is a static site, a static hosting comparison across every option lays the whole field out. This post is about a front end with an API behind it.
Why Are People Leaving Render In 2026?
Mostly because of bandwidth and the free tier's limits, not because the platform got worse. Here's what changed on 23 April 2026, from Render's changelog and pricing page:
- Seat fees went away. The old Professional plan was $19 per member a month; Pro is now $25 a month flat with unlimited seats, plus compute.
- Hobby bandwidth dropped to 5 GB a month, then $0.15 per GB. Render's changelog only says the new plans include "less bandwidth than their legacy counterparts." Third-party commentators called it a 20x cut, from 100 GB.
- Legacy workspaces moved automatically to the new plans on 1 August 2026.
The older free-tier limits still apply too. A free web service spins down after 15 minutes without traffic and takes about a minute to wake. Free Postgres expires 30 days after creation and is deleted after a further 14 days. Render's own docs say free instances shouldn't be used for production.
Who Should Stay On Render
If you run a team, Render got cheaper this year. A five-person team on the old Professional plan paid $95 a month in seats before compute. On Pro it's $25.
Stay, too, if you use the things Render does well together: background workers, cron jobs, private networking between services, preview environments for the full stack, and managed Postgres in the same place. Rebuilding that across three vendors to save a few dollars is a bad trade.
The people with a real reason to move are solo developers on Hobby whose front end is eating the bandwidth pool, and anyone who keeps getting caught by the free tier's sleep and expiry rules.
Where Your Render Bandwidth Actually Goes

On a small SaaS, the front end is usually the biggest user of bandwidth, not the API. The API sends small JSON replies. The front end sends the whole app on every first visit: JavaScript bundles, CSS, fonts and images.
Here's the rough maths. A typical React or Vue app weighs about 1.5 MB on first load. Five gigabytes is about 3,300 of those first visits a month before the meter starts. A month with 50 GB of front-end traffic costs 45 GB times $0.15, which is $6.75 on top of your plan.
That isn't ruinous. The real problems are that it's unpredictable, and that on a Hobby workspace with no card on file, going over the limit suspends every free service for the rest of the month. A busy launch day on your marketing pages can take your free API down with it.
Two fixes work on any host. Long cache lifetimes on hashed files mean returning visitors don't download them again, and MDN's guide to HTTP caching explains the headers. The other fix is moving the front end somewhere bandwidth isn't metered the same way.
Picking A Render Alternative For Each Half
The short answer: keep or move the API based on compute price, and move the front end based on how bandwidth is billed. Here are six options, checked on each vendor's own pages in November 2026. Prices are monthly.
| Host | Takes which half | Free tier | Real starting price | How bandwidth is billed |
|---|---|---|---|---|
| Railway | API + database | $1 of usage credit a month after a 30-day trial | Hobby, $5 a month minimum, includes $5 of usage | $0.05 per GB |
| Fly.io | API + database | None; $1 trial credit for 7 days | Smallest always-on VM $2.19 a month | $0.02 per GB in North America and Europe, up to $0.12 |
| Northflank | API + database | 2 services, 2 jobs, 1 database, always on | From $12 a month | $0.06 per GB |
| DigitalOcean App Platform | Both | 3 static-site apps, 1 GiB each | $5 a month for a small container, 50 GiB included | $0.02 per GiB over |
| Cloudflare | Front end | Unlimited static requests | Workers Paid, $5 a month, if you add server code | Static assets free and unlimited |
| OxyPages | Front end only | 1 non-commercial site on a subdomain | Lite, $5 a month or $48 a year | Not billed; monthly page-view quotas instead |
Railway
Railway feels closest to Render: services and databases in one project, deploys from GitHub, preview environments on every plan. Hobby is a $5 monthly minimum that includes $5 of usage, and builds are free. Egress is metered at $0.05 per GB, a third of Render's overage rate, but it applies from the first gigabyte.
Fly.io
Fly.io suits developers comfortable with Docker and a command line who want cheap always-on compute. There's no free tier, though a personal account's bill under $5 a month is waived with a card on file. Managed Postgres starts at $38 a month, so a lot of people pair Fly with a separate database.
Northflank
Northflank's free Sandbox stays on with no sleeping: two services, two jobs and one database, with no card required. That fixes Render's spin-down problem for a side project. Its pricing page doesn't address commercial use, so check the terms before you put paying customers on it.
DigitalOcean App Platform
DigitalOcean is the one that takes both halves at a fixed price. Three static-site apps are free, with a custom domain and 1 GiB of transfer each. A small container for the API is $5 a month with 50 GiB included, and a dev Postgres is $7.
Cloudflare
Cloudflare suits a front end that might get busy, because static asset requests are free and unlimited, and its terms carry no non-commercial clause. The API can stay on Render or move to Workers later. The confusing part is that Pages and Workers overlap, and Cloudflare tells new projects to use Workers.
OxyPages, For The Front End Only
We take the built front end and nothing else, on a flat price with no bandwidth bill. A SaaS is commercial use, so it starts at Lite, which covers 20,000 page views a month. We don't run web services, workers or databases, so the API stays on Render or goes to one of the platforms above. Custom domains connect by CNAME only, so put the app on a subdomain like app.yourdomain.com.
A Worked Example: Moving Only The Front End

Say you run a small invoicing tool. A Vite front end as a Render static site at app.yourdomain.com, an Express API on a $7 web service at api.yourdomain.com, and a $6 Postgres. The bandwidth line is the only thing bothering you. Here's the move.
- Leave the API and database alone. They're fine where they are.
- Copy the build settings. The build command and publish directory on Render, usually
npm run buildanddist, are the same on the new host. - Set the API address as a build variable, such as
VITE_API_URL, pointing atapi.yourdomain.com. - Turn on single-page app mode on the new host so deep links don't 404. fixing a 404 on refresh covers the rewrite on each major host.
- Add the new front-end address to the API's CORS allowlist while you test on the host's own subdomain.
- Switch the
appCNAME to the new host, check it on a phone, then delete the Render static site.
Render's bandwidth meter now only counts API replies, which for most small apps is a few hundred megabytes a month. Your Render bill becomes $13 of compute, and the front end sits on a free or flat-priced plan.
What To Do Next
Open the Render dashboard and check which service is using the bandwidth. If it's the static site, move only the front end and keep everything else.
If you'd like that front end on a flat price with no bandwidth meter, compare the plans. If your front end renders on the server, a static host can't take it; keep it on Render as a web service, or try Railway. And if you're still choosing a framework, the hosting options for a React app explains which builds can go static.
For a team with workers and cron, staying is often right. For a solo app, a Render alternative is usually partial: move the half that's costing you, and keep the half that works.
FAQ
Is Render Still Free In 2026?
Partly. The Hobby workspace is $0 and static sites are free to deploy, but bandwidth over 5 GB a month costs $0.15 per GB, and static sites count toward it. Free web services sleep after 15 minutes and free Postgres expires after 30 days.
What Is The Cheapest Place To Move An API?
Fly.io has the cheapest always-on compute, from $2.19 a month for its smallest machine, plus egress. Railway is $5 a month minimum with $5 of usage included. Northflank's free Sandbox runs an API and a database with no sleeping, if its terms suit your project.
Do Static Sites Count Toward Render's Bandwidth Limit?
Yes. Render's static site docs say static sites count against the workspace's monthly bandwidth and build minutes. On Hobby, that pool is 5 GB a month, shared with every web service in the workspace.
Should I Move My Whole App Off Render?
Not necessarily. Teams got cheaper on Pro at $25 a month flat, and Render handles workers, cron and Postgres well in one place. If bandwidth is the only complaint, any Render alternative you choose for the front end alone may fix it without touching the API.