Updated October 25, 2026
· ~2 min read
The three are often compared as if they were the same product. They bill different things. Lambda charges for memory multiplied by wall-clock time, so a function waiting 180 ms on a database pays for the wait. Workers charges for CPU time only; the wait is free. Vercel's Fluid Compute charges active CPU and provisioned memory separately, and the platform charges per developer seat.
For I/O-heavy web workloads that difference dominates the bill. For compute-heavy or long-running work it barely matters, and the limits decide instead.
In October 2026 AWS narrowed the gap with Lambda Web Functions: your HTTP server runs on Lambda, many requests share an environment, and you pay for requests, active vCPU time and the memory the environment holds. For web traffic, Lambda now bills much like Vercel and Workers do.
Running at the edge only helps if the work can finish at the edge. A Worker in Sydney that queries a Postgres database in Virginia pays the Pacific round trip on every query, often several per request. Cloudflare's Smart Placement moves the Worker near the backend for this reason. Edge execution is a clear win for auth checks, redirects, A/B assignment, personalization from cached data and anything served from KV or R2. For transactional work against a regional database, put compute next to the database.
Question 1 of 3
Does the code need AWS resources in a VPC, or AWS event sources?
**Lambda:** you need the AWS ecosystem (IAM, VPC access, SQS, EventBridge, Step Functions), languages beyond JavaScript, up to 10 GB of memory or 15-minute jobs. For HTTP services in Node.js, Web Functions now make Lambda price-competitive with the edge platforms. **Workers:** request-path code close to users, I/O-heavy APIs where paying for CPU only is a large saving, and teams happy inside Cloudflare's data products. **Vercel:** a Next.js team that values previews and framework integration over the lowest unit price, and is fine with per-seat pricing. Most companies we work with end up with more than one: Workers or CloudFront Functions at the edge, Lambda or containers next to the data.
Serverless Migration
Move from expensive always-on compute to serverless architecture: reduce costs, eliminate patching, and scale automatically.
AWS Architecture Review
A focused, senior-level review of your current AWS architecture, with a prioritized list of what to fix and why.
AWS Cost Optimization & FinOps Sprint
Reduce your AWS bill by 20–60% while improving performance and reliability.
We work with startups and growing companies on AWS architecture decisions. Tell us about your situation and we will recommend the right approach.
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.