Cloudflare Workers Paid

cloudflare.com

KEEP IT

The value is the network, the data or the infrastructure. Keep paying.

Code that runs at the network edge, close to whoever asked, with storage and a database beside it — sold as a platform rather than a server.

Promptfree, for everyone, and the only version there is
Do not build this. A network in hundreds of cities is the product.

You cannot rent points of presence, and the pricing here is below what running equivalent capacity would cost you. This is one of the few subscriptions where doing it yourself is more expensive.

WHEN THE EDGE IS ACTUALLY THE ANSWER
- Static assets, redirects, header rewriting, image resizing, rate limiting, and anything that answers without reading your database. Those genuinely belong close to the reader
- Denial-of-service absorption, which is the half nobody thinks about until a bad afternoon

WHEN IT IS NOT, AND THIS IS THE COMMON CASE
- **If the code reads your database, the edge is not helping.** Your database is in one place. A function in Sydney that queries a database in Frankfurt is slower than a server in Frankfurt doing the same thing, and it costs more. Running at the edge only helps when the answer is at the edge too
- So: one machine near your database, and the network in front of it for the static half. That is the shape almost everything should have

WHAT TO DO INSTEAD OF MIGRATING
- Put a delivery network in front of whatever you run. That is the cheap part and it is where the speed actually is
- Cache headers: hashed assets immutable for a year, HTML short with stale-while-revalidate. Measured, that does more than any platform choice
- A cache key that ignores tracking parameters, or one campaign fragments your cache into thousands of copies of the same file

WATCH THE MODEL, NOT THE PRICE
- Priced per request and per millisecond of processor time, which is cheap until a loop is not
- The storage and database products here are genuinely useful and genuinely lock you in: their query models do not port. Decide early whether you would ever need to leave, and keep an export running

THE ONE-LINE VERSION
Rent the network. Put your code next to your database — the edge only helps when the data is there too.

What you lose

  • Servers in hundreds of cities, which is the entire product and cannot be built
  • Cold starts measured in single milliseconds, which a container cannot match
  • Denial-of-service absorption at a scale no single machine survives
  • Storage and a database that live at the edge beside the code

If you would rather not build

  • A delivery network in front of one ordinary server, which is the shape most sites want
  • Deno Deploy or similar, if the edge model genuinely fits

The escape hatch

open source · no votes, no paid placement

Caddy

$0

Automatic TLS and a capable reverse proxy with caching.

caddyserver/caddyfree · open source

Varnish

$0

A caching layer to put in front of an origin you control.

varnishcache/varnish-cachefree · open source

Why this verdict

our own opinion · changed only by a person

14/100

Verdict no at 14: the network is unbuildable and cheap. The useful correction is that edge compute helps only when the data is at the edge, which for most applications it is not.

History

tracked since 14 Aug 2026 · nothing is ever overwritten

Interest · last 30 days

Nothing recorded yet. This chart fills in once the page has visitors, votes or prompt copies — it will not draw a flat line to look busy.

Questions about Cloudflare Workers Paid

answered from the record above

Is Cloudflare Workers Paid free?

No — the plan we track is $5 a month. Workers Paid at $5/month billed monthly, including a request allowance, with usage above it billed per million.

Can you replace Cloudflare Workers Paid by building your own?

KEEP IT. The value is the network, the data or the infrastructure. Keep paying. Replacement score 14 out of 100, build time longer than it saves. Read what you lose before you decide.

How much does Cloudflare Workers Paid cost?

$5 a month on Workers Paid — $60 a year. Recorded 14 Aug 2026.

What do you lose by replacing Cloudflare Workers Paid?

Servers in hundreds of cities, which is the entire product and cannot be built; Cold starts measured in single milliseconds, which a container cannot match; Denial-of-service absorption at a scale no single machine survives; Storage and a database that live at the edge beside the code. If any of those carry weight for you, keep paying.

Is there an open-source alternative to Cloudflare Workers Paid?

Yes: Caddy, Varnish. The prompt on this page is for when you want it your way instead.

Related entries

same category first, most replaced first

All 21 in Hosting & databases

Not sending yet

Every week, something stops being worth paying for.

New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click. Nothing is being sent yet — your address is kept here, and the first issue is the first thing it is used for.

free forever · no tracking pixel · stored here, never passed to anyone

Esc