Comparisons

Cheapest Full-Stack Hosting in 2026

React, an API and managed Postgres, priced on 8 platforms, and what each bill does when traffic grows 15 times

Cheapest Full-Stack Hosting in 2026
Published

The cheapest full-stack hosting for a React app, a Node.js API and a managed PostgreSQL database in 2026 is Light Cloud at $5 a month, with Railway at about $5.30 once the RAM and CPU it bills by are counted. Google Cloud Run with Cloud SQL is about $9.40 if you're willing to set it up yourself. Heroku, DigitalOcean and Render sit between $10 and $14, and AWS and Fly.io with a managed database land near $40.

We make Light Cloud, the first row. The method is below the fold and every price links to the vendor's page.

How we ranked

This is the stack from our four-platform comparison, repriced in October 2026 and widened to eight platforms: a React frontend, one Node.js API, a managed PostgreSQL database and a custom domain, at about 1,000 API requests a day. Prices are list prices from the vendors' own pages, checked on 2026-10-13 and again on 2026-11-02, in US dollars, smallest sensible tier, no trial credits. AWS is priced in us-east-1. Where a platform bills by usage, the price is the usage this stack generates, not the plan's starting fee, so no row hides its bill behind a "+".

"Managed" is the rule that decides the top of the table. It means the database is a product the vendor sells and supports, with someone else patching it. Without that rule, Fly.io's unsupported self-run Postgres would win at about $4, and I'd rather tell you that than hide it; it's in the last section.

Cheap today is half the question. So the second column repeats each bill at 15 times the traffic, 15,000 requests a day, which is roughly what a launch week or a mention in a newsletter does to a small app. Fixed-price platforms don't move. Usage-priced ones do, and you should know by how much.

Kept running all month, with no scale to zero, the same stack gets the Always on prices in the table. Light Cloud comes last 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.

The ranking

Cheapest first, with a managed Postgres databasePrices checked 13 Oct 2026
1
$5
The lowest all-in bill for a full-stack app that is quiet most of the day, with nothing to wire togetherPrice: all in, Lite plan
At 15,000 requests a dayAbout $7.30, billed per useManaged PostgresShared, $4, Belgium only
2
~$5.30
Free builds and cheap egress for about 30 cents more than us, if your services stay smallPrice: Hobby $5 + about $0.30 of usage
At 15,000 requests a dayAbout $6, billed by RAM and CPU usedManaged PostgresTemplate service, billed by use
3
~$9.40
The lowest price per request at volume, for teams who will set up Cloud SQL, IAM and the domain themselvesPrice: Cloud SQL + 10 GB SSD; domain via Firebase
At 15,000 requests a dayAbout $9.40, still in the free tierManaged PostgresCloud SQL, you set it up
4
$10-12
One dyno serving the API and the built frontend, on a platform in maintenance modePrice: Eco or Basic dyno
At 15,000 requests a day$12, unchangedManaged PostgresEssential-0, $5, 1 GB
5
$12
Fixed container prices with the frontend on a free static tierPrice: dev database
At 15,000 requests a day$12, unchangedManaged PostgresDev database, no backups by default
6
$13.30
Fixed per-service prices that stay flat as traffic growsPrice: Starter service + Postgres
At 15,000 requests a day$13.30, unchangedManaged Postgres$6 plus $0.30 per GB
7
~$40
Teams already on AWS who need its networking and compliance options more than a small billPrice: Fargate, load balancer, RDS
At 15,000 requests a dayAbout $40, unchangedManaged PostgresRDS db.t4g.micro, $11.52
8
~$40
Apps that need machines in several regions, or teams happy to run Postgres themselvesPrice: with Managed Postgres
At 15,000 requests a dayAbout $40, unchangedManaged PostgresManaged from $38, or $2 unsupported
List prices from each vendor's own pricing and docs pages, checked 2026-10-13, US dollars, smallest sensible tier, no trial credits. Reference app: a React frontend, one Node.js API, a managed PostgreSQL database and a custom domain, about 1,000 API requests a day. The second column repeats the bill at 15,000 requests a day. Light Cloud usage uses the pricing page's assumption of 0.2 s of instance time per request; AWS is priced in us-east-1. Usage-billed platforms are priced on the usage this stack generates, never on the plan's starting fee: on Railway that is about 250 MB of RAM for the API, which also serves the built frontend, and 200 MB for Postgres on average, 0.03 vCPU, a 1 GB volume and 1.5 GB of egress. Cloud SQL gets 10 GB of SSD storage and the domain goes through Firebase Hosting. At 15,000 requests a day, metered compute grows by the same 0.2 s per request on every platform, and bandwidth stays out of every row. The Always on view keeps the API running all month with no scale to zero, at each platform's cheapest documented way to do that.

1. Light Cloud

Best for: the lowest all-in bill for an app that is quiet most of the day.

The cheapest full-stack hosting here is one $5 plan. Lite includes $5 of usage, a custom domain and one shared PostgreSQL database (pricing). The app uses about $4.55 of it: the database is $4 plus 30 cents for a GB of storage, the API about 20 cents (1,000 requests a day at 0.2 s each is 1.7 instance-hours at $0.12), the static frontend and builds a few cents. With pay-as-you-go hosting the API is billed for the hours it actually runs, so a quiet night costs nothing.

At 15,000 requests a day the API's share rises to about $3.04, the figure our pricing page uses for a busy app, and the bill becomes about $7.30: still Lite, plus about $2.30 of usage on the next invoice. Nothing else changes. Frontend, API and PostgreSQL database hosting sit in one project, GitHub deploys ship each push, and the same console has built-in logs and metrics.

What you give up for $5: shared databases run in Belgium only, there's no private network between services, no cron and no workers. A container that has scaled to zero takes 3.1 to 3.7 seconds to answer its first request. An always-on instance needs the $19 Starter plan and runs about $52 a month, so a service that's busy around the clock belongs on a fixed instance somewhere else.

2. Railway

Best for: free builds and cheap egress, for about 30 cents more.

Hobby is $5 a month including $5 of usage (plans). Compute is metered by what services hold: $10 per GB of RAM a month, $20 per vCPU a month. Builds are free and egress is $0.05 per GB, both cheaper than ours. Postgres is a template service billed the same way, plus $0.15 per GB of volume storage. For this stack that's about $5.33: roughly $2.50 for a Node API averaging 250 MB that also serves the built frontend, $2 for Postgres at 200 MB, $0.60 of CPU, and cents for the volume and egress. The bill is the larger of $5 and the usage, so about $5.30, and the same always on, because 1,000 requests a day rarely leave the API idle long enough to sleep.

Because Railway bills RAM that a service holds rather than requests it serves, more traffic only raises the bill when the service needs more memory or CPU to handle it. Give each of the 14,000 extra requests a day 0.2 s of CPU, the same assumption our row uses, and that's about 65 cents more, so about $6 at 15,000 requests a day. That's a different curve from ours, and at this traffic a cheaper one. Railway recommends Pro, $20 a month, for commercial apps.

3. Google Cloud Run, used directly

Best for: the lowest price per request at volume.

Our containers run on Cloud Run, so this row is the do-it-yourself version of ours, and at volume it's cheaper. The free tier covers 180,000 vCPU-seconds and 2 million requests a month (pricing); even 15,000 requests a day at 0.2 s each is 90,000 vCPU-seconds, so compute stays at $0. Cloud SQL's smallest instance is $0.0105 an hour, about $7.67 a month, and 10 GB of SSD storage adds $1.70 at $0.17 per GB (Cloud SQL pricing): $9.37.

The price is your time: a billing account, IAM roles, a Cloud SQL instance, and a load balancer or Firebase Hosting for the domain, because Cloud Run's own domain mapping is not production-ready. Firebase Hosting is the cheap route: its no-cost quota is 10 GB stored and 360 MB served a day (Firebase pricing), which this app stays inside at 1,000 requests a day. The load balancer Google recommends is a monthly charge of its own. Spend caps that pause Cloud Run became generally available on 2026-10-12.

4. Heroku

Best for: one dyno serving the API and the built frontend.

Eco is $5 a month for 1,000 shared dyno hours, sleeps after 30 minutes and is for personal apps only; Basic is $7 and always on. Essential-0 Postgres is $5 with 1 GB of disk (pricing). So $10 or $12, and traffic doesn't change it until you need a second dyno, which on Heroku means Standard-1X at $25.

A card is required before you deploy, and since 2026-02-06 Heroku is in sustaining engineering mode: maintained, not developed.

5. DigitalOcean App Platform

Best for: fixed container prices with a free static tier for the frontend.

A 512 MiB container is $5 a month and a development database $7 (pricing); the React build goes on the free static tier. $12, flat. The catch is in the database: a development database is tied to one app, has no backups by default and is deleted with the app. Managed PostgreSQL that survives the app starts at $15 (database pricing), which makes it $20.

6. Render

Best for: fixed per-service prices that stay flat as traffic grows.

A Starter web service is $7 a month for 512 MB and the smallest Postgres $6 plus $0.30 per GB (pricing): $13.30, frontend free as a static site. Traffic doesn't change the bill until the instance runs out of headroom, and then the next step is a bigger plan you choose, not a meter. Render's free tier isn't an option for this app: free Postgres expires after 30 days.

7. AWS

Best for: teams already on AWS who need what only AWS has.

The managed container route is now ECS, since App Runner stopped accepting new customers on 2026-04-30. In us-east-1 the smallest Fargate task running all month is about $8.89, a public IPv4 address $3.60 and an Application Load Balancer $16.20 before usage charges (Fargate, load balancer). The cheapest RDS for PostgreSQL instance, db.t4g.micro, is $0.016 an hour, $11.52 a month. About $40 before storage and data transfer, and almost half of it is the load balancer.

ECS Express Mode, which AWS recommends instead of App Runner, has no extra charge and can share one load balancer across services, so the second and third service are cheaper than the first. For one small app, though, the fixed parts dominate.

8. Fly.io

Best for: apps that need machines in several regions.

Machines are the cheapest compute here, from $2.19 a month always on (pricing), and they can stop when idle. Managed Postgres starts at $38 plus $0.28 per GB (docs), so about $40 with a supported database. Fly's self-managed Postgres is about $2 a month for a development node, but it's officially unsupported.

Where the others beat us

Fly.io with its self-managed Postgres comes to about $4.20 a month, the only stack in this post under ours. If you're comfortable running and backing up your own database, that's the real cheapest. Cloud Run used directly gets cheaper than us as traffic grows, because its free tier keeps covering compute while our bill counts instance-hours. At 15,000 requests a day it's about $9.40 against our $7.30, and only Cloud SQL's fixed $9.37 with its storage keeps it behind; by my arithmetic, past roughly 25,000 requests a day the do-it-yourself version wins. Railway is already cheaper than us at that traffic, about $6. Render, DigitalOcean and Heroku don't move at all with traffic, and for a service that is busy around the clock, a $7 fixed instance beats our always-on price by a wide margin. Railway's free builds and $0.05 egress are cheaper than our $0.01 a minute and $0.20 per GB.

Where we're ahead is the all-in bill for a full-stack app before it's busy: frontend, API, a managed database and a domain on one $5 plan, with no load balancer, IAM role or second account to set up. Deploying a React app and adding Postgres to the API are the two tutorials that build this exact stack. If you've read the three-way bill, this is the wider version of it.

What would your app's bill look like at 15 times today's traffic?

More articles