Compare platforms.

Prices checked

20 pairings put 43 shapes side by side, the cheapest $1.61/mo, checked .

4 shapes both sell

DigitalOcean App Platform vs Fly.io

Entry prices, free tiers and every size or tier both sell, side by side.

2 shapes both sell

DigitalOcean App Platform vs Heroku

Entry prices, free tiers and every size or tier both sell, side by side.

3 shapes both sell

DigitalOcean App Platform vs Koyeb

Entry prices, free tiers and every size or tier both sell, side by side.

6 shapes both sell

DigitalOcean App Platform vs Render

A cloud's app platform against a company that only does app platforms.

No shape in common

DigitalOcean App Platform vs Zeabur

Entry prices, free tiers and every size or tier both sell, side by side.

4 shapes both sell

Fly.io vs Koyeb

Two ways to buy a small always-on runtime, one a container and one a micro-VM.

No shape in common

Fly.io vs Railway

Metered compute on a subscription against a machine you size yourself.

3 shapes both sell

Fly.io vs Render

A machine of your own against a container somebody else keeps running.

No shape in common

Heroku vs Railway

The oldest bill in this market against one of the newest.

1 shape both sell

Heroku vs Render

The platform that invented the dyno against the one most people move to.

No shape in common

Heroku vs Zeabur

Entry prices, free tiers and every size or tier both sell, side by side.

2 shapes both sell

Koyeb vs Render

Entry prices, free tiers and every size or tier both sell, side by side.

2 shapes both sell

Netlify vs Railway

Entry prices, free tiers and every size or tier both sell, side by side.

2 shapes both sell

Netlify vs Vercel

The two frontend clouds, both priced as a seat with the compute metered on top.

3 shapes both sell

Netlify vs Zeabur

Entry prices, free tiers and every size or tier both sell, side by side.

2 shapes both sell

Railway vs Render

The two platforms people shortlist together when they want a container and a database in one place.

2 shapes both sell

Railway vs Vercel

The frontend cloud against the one that will also run your backend.

2 shapes both sell

Railway vs Zeabur

The challenger's ladder against the one it is priced against.

3 shapes both sell

Render vs Zeabur

Entry prices, free tiers and every size or tier both sell, side by side.

2 shapes both sell

Vercel vs Zeabur

Entry prices, free tiers and every size or tier both sell, side by side.

How we count

Two platforms at a time, on every shape they both sell: a runtime with the same stated memory, or a subscription at the same step of both ladders. A seat and a gigabyte are never put in the same row.

Pairings are chosen rather than generated, because several platforms here sell no runtime of a stated size at all. Each page puts the metered rates, the free tier and what happens when the app is idle beside the prices. A free tier is a limit rather than a price, so it is never the cheaper of two.

Frequently asked

How are these pairings chosen?
By hand: 20 comparisons people actually make. Some platforms sell no runtime of a stated size at all, so pairing every platform with every other would make pages with only their subscription ladders to compare.
What if two platforms sell nothing of the same shape?
Then the page compares what can be compared: the entry price, the free tier, what stops when the app is idle and what each one meters on top. 4 of the 20 pairings are like that today.

Where to go next