For twenty years, hosting a website meant renting a server: a box in one data center that you size, patch, and pay for whether anyone visits or not. We have looked after thousands of those servers. When we rebuilt seahawkmedia.com, we did not put it on one. It runs on Cloudflare Workers, and for most new sites we now think that is simply the better way to host.
What “server” and “serverless” actually mean
Traditional hosting (shared hosting, a VPS, a dedicated or cloud server) gives your site a computer that is always on. It lives in one location. It has a fixed amount of CPU and memory. When traffic doubles, it slows down until someone upgrades it. When traffic is zero at 3am, you still pay for it.
Serverless means you upload your code and the platform runs it on demand, only when a request arrives. There are still servers, of course. They are just not your problem. You never pick a size, install an operating system, or apply a security patch.
Cloudflare Workers is serverless taken further. Your code runs in every Cloudflare location, more than 300 cities worldwide, so each visitor is answered by the data center nearest to them, not by one machine on the other side of the world.
The comparison
| Factor | Traditional server | Cloudflare Workers |
|---|---|---|
| Where your site runs | One data center | 300+ cities, nearest to each visitor |
| Scaling | Upgrade the plan, or go down under load | Automatic, from zero to a traffic spike, no config |
| Cold starts | Always on, but sized for peak | Isolates start in milliseconds, no warm-up |
| Paying for idle time | Yes, 24/7 | No: billed per request and CPU time actually used |
| Bandwidth | Often capped or metered | No charge for egress or bandwidth |
| Static files (pages, images, CSS) | Served by your server | Free and unlimited on every plan |
| Security patching | OS, web server, PHP, every plugin | Cloudflare patches the runtime |
| DDoS protection | Add-on, if at all | Built in, it is Cloudflare’s network |
| Deploys | FTP, SSH, or a control panel | One command, live worldwide in seconds |
| Runs WordPress (PHP) | Yes | No |
We come back to that last row below. Everything above it is why we moved.
Why Workers is faster
Speed on the web is mostly distance. A visitor in Sydney hitting a server in Virginia waits for every request to cross the Pacific and back. A CDN caches the static parts, but anything dynamic (a form, a search, a logged-in page) still makes the trip.
On Workers, the dynamic parts run in Sydney too. There is no origin server to go back to.
The other half is how Workers starts your code. Most serverless platforms boot a container for each function, which is where the dreaded “cold start” comes from. Workers runs code in V8 isolates, the same sandboxing technology Chrome uses for browser tabs. Cloudflare’s own documentation says an isolate starts around a hundred times faster than a Node process in a container, using an order of magnitude less memory. In practice, there is no warm-up to notice.
Why Workers is cheaper
These are Cloudflare’s published prices, not ours:
- Free plan: 100,000 requests a day.
- Paid plan: $5 a month, including 10 million requests and 30 million CPU milliseconds. After that, $0.30 per extra million requests and $0.02 per extra million CPU milliseconds.
- Static assets: free and unlimited on both plans.
- Bandwidth: no egress or bandwidth charges at all.
A typical small business site is mostly static pages, which cost nothing to serve, plus a few forms and dynamic routes. That fits comfortably inside the $5 plan, and often inside the free one. Workers bills CPU time, not the clock, so time spent waiting on a database or an API is free. A server, by contrast, is sized for your busiest day and billed for every hour of every quiet one.
Why Workers is safer and easier to run
Most of the WordPress emergencies we handle start on the server: an outdated PHP version, an unpatched plugin, a full disk, a compromised account with shell access. On Workers there is no operating system for you to patch, no disk to fill, and no server for an attacker to log into. Each Worker runs in its own isolate, walled off from every other Worker on the machine, and sits behind the same network that absorbs some of the largest DDoS attacks on record.
Deploys are a single command. A new version is live worldwide in seconds, and rolling back is just as fast.
Where a traditional server still wins
We said we would be honest about the last row of the table.
- WordPress needs PHP. Workers runs JavaScript, TypeScript, WebAssembly, and Python, not PHP. If your site is WordPress and staying WordPress, it needs a server. Put Cloudflare in front of it for caching and protection, and keep it well maintained.
- Some native code will not run. Node.js libraries with native binaries, and code that writes to the local file system, need reworking. Cloudflare Containers covers the cases that truly need a full Linux environment.
- Long, heavy jobs need a different shape. A Worker request gets up to five minutes of CPU time and 128 MB of memory. That is plenty for a website, but big batch jobs belong in Cloudflare’s Queues and Workflows, or on a server.
None of these are reasons to start a new site on a server. They are reasons a few existing ones stay there.
So which should you choose?
Choose Workers if you are building a new site, rebuilding an old one, or your WordPress site is mostly pages and posts that rarely use plugins. Astro and EmDash both run on Workers natively, so you get a modern CMS, a fast front end, and hosting that costs little to nothing. Our guides to WordPress vs Astro and EmDash vs WordPress cover the CMS side of that decision.
Stay on a server if your business runs on WordPress plugins (WooCommerce, memberships, bookings) and rebuilding them is not worth it yet. Then the job is keeping that server fast and patched.
For everyone else: stop renting a box in one city. Run your site everywhere.
Next step
Em Workers builds EmDash and Astro sites that run on Cloudflare Workers, at prices set for small businesses. Tell them what your current site does, and they will tell you plainly whether it belongs on Workers, scope the move, and look after it afterwards. Start with Em Workers.