Expert Guide

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.

Product links may be affiliate links. How we rate 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 now sells credits instead of seats: Pro is one flat monthly fee for the whole team. 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.

Key facts5 tools compared: Cloudflare Workers, Vercel, Netlify, Fly.io, Render
  • Updated: September 25, 2026
  • Top pick: Cloudflare Workers (best for: Edge logic, APIs and anything where bandwidth is the risk)
  • Top pick price as of September 25, 2026: Cloudflare Workers: From $5/mo minimum per account; free tier (100,000 requests/day)
  • 5 tools compared: Cloudflare Workers, Vercel, Netlify, Fly.io, Render
  • Vercel (best for: Next.js teams that want the best deployment experience available): From $20 per user/mo (Pro); Hobby free forever; Enterprise custom
  • Netlify (best for: Front ends that are not tied to one framework): From $9/mo (Personal); Pro from $20/mo with unlimited members; free plan
  • Fly.io (best for: Long-running processes close to users, without Kubernetes): From roughly $1.94-$2.02/mo (shared-cpu-1x, 256MB)

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 Sep 2026
ToolPricingBest for
Cloudflare WorkersFrom $5/mo minimum per account; free tier (100,000 requests/day)Edge logic, APIs and anything where bandwidth is the risk
VercelFrom $20 per user/mo (Pro); Hobby free forever; Enterprise customNext.js teams that want the best deployment experience available
NetlifyFrom $9/mo (Personal); Pro from $20/mo with unlimited members; free planFront ends that are not tied to one framework
Fly.ioFrom roughly $1.94-$2.02/mo (shared-cpu-1x, 256MB)Long-running processes close to users, without Kubernetes
RenderFrom about $7/mo per instance; free for static sites and small servicesTeams that want Heroku's simplicity with current pricing

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

Lowest published monthly priceCloudflare Workers$5Vercel$20Netlify$9Fly.io~$2.02Render~$7
Lowest monthly figure each vendor publishes, checked Sep 2026. A tilde marks a figure the vendor states approximately. Per-seat and usage charges can sit on top of it. Every tool here publishes a monthly price.

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

PricingFrom $5/mo minimum per account; free tier (100,000 requests/day)

+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 →
2

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

PricingFrom $20 per user/mo (Pro); Hobby free forever; Enterprise custom

+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 →

Best for: Front ends that are not tied to one framework

PricingFrom $9/mo (Personal); Pro from $20/mo with unlimited members; free plan

+Framework-agnostic, so it does not push you toward one stack
+Mature build plugin ecosystem
+Straightforward for static and hybrid sites
−Credits cover bandwidth, compute and deploys, so a traffic spike drains the monthly pool
−The free plan stops at 300 credits, and a zero balance pauses the team's projects
Visit Netlify →
4

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

PricingFrom roughly $1.94-$2.02/mo (shared-cpu-1x, 256MB)

+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 →
5

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

PricingFrom about $7/mo per instance; free for static sites and small services

+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 developer seat per month is perfectly reasonable for five people and an argument at fifty, regardless of how much traffic you serve. Netlify moved the other way: its credit-based Pro plan includes unlimited members, so headcount no longer moves that bill.

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.

Pricing

Cloudflare, Vercel, Netlify, Fly.io and Render all publish an entry price, and Cloudflare, Vercel, Netlify and Render publish a free tier. Vercel Enterprise and Netlify Enterprise are the only custom quotes. The cheapest credible paid entry is Fly.io, at roughly $1.94 to $2.02 a month for a shared-cpu-1x with 256MB in some regions.

Cloudflare's paid minimum is $5 a month, and Render's instances start at about $7 a month. Costs jump with headcount on Vercel, where Pro is $20 per developer seat per month with usage on top; Netlify Pro charges one flat monthly fee for unlimited members and meters usage in credits.

The bill also jumps on Cloudflare's per-million overages and on Fly.io support and Kubernetes, which sit apart from the small machine price.

PlanPriceBest for
Cloudflare Workers FreeFree100,000 requests/day, 10ms CPU per invocation
Cloudflare Workers Paid$5/mo minimum per account10 million requests, no egress or bandwidth charges
Cloudflare Workers requests$0.30 per additional millionAfter the 10 million requests included
Cloudflare Workers CPU$0.02 per additional millionAfter 30 million CPU-milliseconds included
Vercel HobbyFree foreverHobby plan, free forever
Vercel Pro$20 per user per monthMatching usage credit included, usage billed on top
Vercel EnterpriseCustom quoteEnterprise plan at a custom price
Netlify FreeFree300 usage credits a month, hard limit
Netlify ProFrom $20/moUnlimited members, 3,000 credits a month and up
Netlify EnterpriseCustom quoteEnterprise plan at a custom price
Fly.io shared-cpu-1xRoughly $1.94-$2.02/mo256MB machine in some regions
Fly.io volumes$0.15/GB/moVolume storage, per GB per month
Fly.io Standard support$29/moStandard support plan
Fly.io Premium support$199/moPremium support plan
Fly.io Enterprise supportFrom $2,500/moEnterprise support plan
Fly.io Kubernetes$75/mo per clusterFly Kubernetes, billed per cluster
Render freeFreeStatic sites and small services
Render instancesFrom about $7/moPaid instances, per month
Render Pro$25/mo + computeFlat workspace fee with unlimited seats
Mistakes to avoid
×Picking a per-seat platform for a large team serving little traffic. At Vercel Pro's per-seat price, a twenty-person team pays $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 alternative whose Pro plan does not charge per member.

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 charges $20 per developer seat with usage on top, while Netlify Pro is one flat monthly fee for unlimited members, with usage billed in credits. 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.

Sources

Prices and plan details come from each vendor's own pricing page, re-checked by the Toolradar pricing tracker.

Related guides

Some offers on this page may be paid placements or contain affiliate links.

Get the Devshot brief

Free daily newsletter, read in 5 minutes.

Subscribe free