Expert Guide Editorially reviewed

The Best Serverless Platforms in 2026

The per-seat platforms bill you for your team. The usage-based ones bill you for your traffic. Pick the one whose surprise you can absorb.

Louis CorneloupFounder, Dupple · 810,000+ readers · Updated Aug 2026

Independently researched. No pay-for-placement. 5 tools compared

TL;DR

Cloudflare Workers is the cheapest way to run code at the edge, $5 a month minimum with 10 million requests included and no egress charges. Vercel is the best experience for Next.js and bills $20 per user. Netlify is the same shape at $19 per member. Fly.io and Render are the picks when you want a long-running process rather than a function, from roughly $2 and $7 a month respectively.

Serverless stopped meaning one thing years ago. It now covers edge functions that run in milliseconds, full application platforms that deploy a framework, and container hosts that keep a process alive. They compete for the same deployments and bill in completely different shapes.

That billing shape is the decision.

Per-seat platforms scale with your team, usage-based platforms scale with your traffic, and the wrong choice is only visible once one of those grows.

Top Picks

Based on features, real-world fit, and value for money.

Best Serverless Platforms in 2026: 5 tools compared, updated Aug 2026
Tool	Pricing	Best for
Cloudflare Workers	Free tier: 100,000 requests/day, 10ms CPU per invocation. Paid from $5/mo minimum per account, including 10 million…	Edge logic, APIs and anything where bandwidth is the risk
Vercel	Hobby free forever; Pro $20 per user per month with $20 of included usage credit; Enterprise custom. Usage billed on…	Next.js teams that want the best deployment experience available
Netlify	Free Starter plan; Pro from $19 per member per month; Enterprise custom. Usage-based bandwidth and build minutes on top.	Framework-agnostic front ends and JAMstack sites
Fly.io	Pay per machine: a shared-cpu-1x with 256MB runs roughly $1.94-$2.02/month in some regions. Volumes $0.15/GB/mo…	Long-running processes close to users, without Kubernetes
Render	Free tier for static sites and small services; instances from about $7 per month; Professional workspace pricing above…	Teams that want Heroku's simplicity with current pricing

Pricing read from each vendor's own published pricing page, checked Aug 2026. Every vendor here publishes a price.

Lowest monthly figure each vendor publishes, checked Aug 2026. A tilde marks a figure the vendor states approximately. Per-seat and usage charges can sit on top of it. 2 of 5 do not publish a comparable monthly price and are left out rather than estimated.

Cloudflare Workers

Top Pick

Best for: Edge logic, APIs and anything where bandwidth is the risk

PricingFree tier: 100,000 requests/day, 10ms CPU per invocation. Paid from $5/mo minimum per account, including 10 million requests then $0.30 per additional million, and 30 million CPU-milliseconds then $0.02 per additional million. No egress or bandwidth charges. Checked 27 August 2026.

+No egress charges at all, which removes the least predictable line on the bill

+$5 a month covers 10 million requests

+Runs at the edge by default, so latency is a non-issue

−CPU time per invocation is capped, so heavy compute does not fit

−Its own runtime rather than plain Node, so some libraries do not work

Visit Cloudflare Workers →

Vercel

Best for: Next.js teams that want the best deployment experience available

PricingHobby free forever; Pro $20 per user per month with $20 of included usage credit; Enterprise custom. Usage billed on top.

+Best-in-class developer experience, particularly with Next.js

+Preview deployments per pull request that reviewers actually use

+Generous personal tier for side projects

−Per-user pricing grows with headcount rather than usage

−Usage charges sit on top of the seat price

Visit Vercel →

Netlify

Best for: Framework-agnostic front ends and JAMstack sites

PricingFree Starter plan; Pro from $19 per member per month; Enterprise custom. Usage-based bandwidth and build minutes on top.

+Framework-agnostic, so it does not push you toward one stack

+Mature build plugin ecosystem

+Straightforward for static and hybrid sites

−Per-member pricing has the same headcount problem as Vercel

−Build minutes and bandwidth metered on top

Visit Netlify →

Fly.io

Best for: Long-running processes close to users, without Kubernetes

PricingPay per machine: a shared-cpu-1x with 256MB runs roughly $1.94-$2.02/month in some regions. Volumes $0.15/GB/mo. Support plans Standard $29/mo, Premium $199/mo, Enterprise from $2,500/mo. Fly Kubernetes $75/mo per cluster. Checked 27 August 2026.

+Genuinely cheap for small always-on workloads, from roughly $2 a month

+Real containers, so no runtime compatibility surprises

+Multi-region deployment without an orchestration layer

−Pay-per-resource means the bill takes attention rather than a plan choice

−More operational surface than a push-to-deploy platform

Visit Fly.io →

Render

Best for: Teams that want Heroku's simplicity with current pricing

PricingFree tier for static sites and small services; instances from about $7 per month; Professional workspace pricing above that.

+Simplest path from repository to running service

+Managed Postgres, cron and background workers included in the model

+Predictable per-instance pricing

−Free instances sleep, which surprises people the first time

−Fewer regions than the edge platforms

Visit Render →

What it is

A serverless platform runs your code without you provisioning a server.

In practice there are three families: edge runtimes that execute small functions close to the user, application platforms that build and host a framework with previews and CDN included, and managed container hosts that run an ordinary long-lived process without you touching Kubernetes.

The families overlap enough that a single project could ship on any of them, which is why the pricing model tends to decide it rather than the technology.

Why it matters

Egress is where serverless bills go wrong. Cloudflare charges nothing for bandwidth on Workers, which removes the single most unpredictable line from the invoice. Platforms that meter bandwidth can hand you a bill shaped by one popular post.

The second trap is per-seat pricing on a large team.

Vercel Pro at $20 per user per month and Netlify Pro at $19 per member are perfectly reasonable for five people and an argument at fifty, regardless of how much traffic you serve.

Key features to look for

Pricing model

Per-seat, per-request, or per-instance. This decides whether your bill tracks your team, your traffic or your uptime, and it is the only choice here that is hard to reverse later.

Egress charges

Whether bandwidth is metered. Cloudflare charges none on Workers; most others meter it, and it is the line most likely to produce a bill nobody predicted.

Cold starts and runtime limits

How long a function may run and how quickly it wakes. Edge runtimes start almost instantly but cap CPU time; container hosts have no cap but keep a process alive and charge for it.

Long-running processes

Whether the platform can host a websocket server or a background worker at all. Edge functions cannot; Fly and Render are built for exactly this.

Preview deployments

A URL per pull request. Standard on the application platforms and the main reason teams accept per-seat pricing.

Free tier shape

What you can run at zero. Cloudflare gives 100,000 requests a day, Vercel and Netlify give a personal tier, Render covers static sites and small services.

Mistakes to avoid

×Picking a per-seat platform for a large team serving little traffic. At $19 to $20 per person, a twenty-person team pays around $400 a month before a single request, which a usage-based platform would bill at a fraction of.

×Ignoring egress until the invoice. Bandwidth is metered almost everywhere and is the line that moves when something of yours gets shared widely. Cloudflare not charging for it is a real structural difference, not a marketing point.

×Putting a long-running process on an edge runtime. Workers cap CPU per invocation by design. A websocket server or a queue consumer belongs on Fly or Render, and finding that out in production is expensive.

Expert tips

→Work out whether your cost driver is people or traffic before comparing anything. That single answer eliminates half this list immediately.

→Run the free tiers in parallel for a week with the same project. Cloudflare's 100,000 requests a day and Render's free services are enough to compare real deploy times rather than documented ones.

→Read the overage rate, not the plan price. Cloudflare's $0.30 per additional million requests is the kind of number that decides your bill at scale, and it sits well below the headline.

The bottom line

If your code fits an edge runtime, Cloudflare Workers is the most economical serious option available: $5 a month, 10 million requests, and no bandwidth charge at all.

If you ship Next.js and value the workflow more than the invoice, Vercel is worth its $20 per seat, with Netlify as the framework-agnostic equivalent at $19.

For anything that has to stay running, Fly.io is remarkably cheap at roughly $2 a month for a small machine, and Render is the easiest on-ramp if you want managed databases and cron in the same place.

Frequently asked questions

What does serverless actually cost?

It depends entirely on the model. Cloudflare Workers starts at $5 a month for 10 million requests with no egress charge. Vercel and Netlify charge per person, $20 and $19 respectively, with usage on top. Fly bills per machine, from roughly $2 a month for a small instance, and Render's instances start around $7. Figures checked 26 to 27 August 2026.

Which serverless platform has the best free tier?

Cloudflare's is the most useful for real work: 100,000 requests a day, every day, with no bandwidth charge. Vercel and Netlify's personal tiers are generous for side projects but not licensed for commercial use in the way teams often assume. Render's free services sleep when idle, which is fine for a demo and not for an API.

Can I run a websocket server on serverless?

Not on an edge function runtime, which caps CPU time per invocation by design. You want a container host: Fly.io and Render both run long-lived processes normally, and Fly's per-machine pricing makes a small always-on service genuinely cheap.

Is per-seat or usage-based pricing better?

Per-seat is predictable and punishes headcount; usage-based is cheap while you are small and unpredictable when something takes off. A five-person team serving heavy traffic usually wins on per-seat; a twenty-person team serving modest traffic almost always loses on it.

Get the Devshot brief

Free daily newsletter, read in 5 minutes.

Subscribe free