See it live
See what your site looks like when it can't go down.
These are real Drupal and WordPress sites — captured and served 100% static on
Cloudflare's global edge. No origin server, no database, no PHP — nothing to hack
or crash. Same site your visitors see; none of the attack surface.
Pick your industry below and open the live, edge-served version in a new tab.
The transformation
An origin to attack & crash
Nothing to attack or crash
We take a live Drupal site, render every page, and publish the result as immutable files on the global edge. The dynamic stack — origin, database, PHP, admin login — is simply gone from the public internet. What's left is your site, everywhere, with no server in the request path.
Six live demos
LIVE
Halcyon International
Flight info, terminal maps, and travel alerts — the kind of high-traffic site that absolutely cannot go down, served static with no origin to overwhelm.
Open live demo → halcyon-airport.pages.dev (opens in a new tab)
LIVE
Calverton State University
Programs, admissions, and campus news — a sprawling .edu Drupal site with no live CMS to patch and no /user/login for attackers to find.
Open live demo → calverton-university.pages.dev (opens in a new tab)
LIVE
Linnaea Gardens
Exhibits, events, and visitor info for a botanical nonprofit — a content-rich site that stays fast and online on a small-org budget, with nothing to maintain.
Open live demo → linnaea-demo.pages.dev (opens in a new tab)
LIVE
Pinewood County
Services, departments, public meetings, and resident alerts — a county government site that has to stay reachable for the public, served static with no origin to breach or take down.
Open live demo → pinewood-county.pages.dev (opens in a new tab)
LIVE
Northwater Health
Services, providers, locations, and conditions for a regional health system — a trust-critical site that stays online and patch-free, with no live CMS to compromise.
Open live demo → northwater-health.pages.dev (opens in a new tab)
LIVE
The Copper Fern
Menu, story, hours, and contact for a farm-to-table restaurant — a WordPress
small-business site, captured and served static with no /wp-admin to attack
and no origin to crash.
Proof, not promises
The same site, measured two ways. As a live Drupal origin, every uncached request does real PHP + database work — so its first byte swings wildly depending on cache state. As a static edge capture, there's no render step and no server in the path — just a file, everywhere. Here's what we measured.
cold render — real PHP + DB work, every cache miss
median over the public internet — no render step, ever
Same site. The Drupal origin's first byte ranges from ~20 ms (cache hit) to ~1,100 ms the moment it has to actually render — which it does on every cache miss, deploy, and content edit — and it scored 84 on Lighthouse performance. The static edge copy holds ~105 ms with no render step to fall off of, scored 90, and has no origin to attack or crash in the first place.
| Live demo | Median TTFB | Lighthouse perf | Delivery |
|---|---|---|---|
| Halcyon Internationalhalcyon-airport.pages.dev | 105 ms | 90 | edge-cached static |
| Calverton State Universitycalverton-university.pages.dev | 139 ms | 72 | edge-cached static |
| Linnaea Gardenslinnaea-demo.pages.dev | 115 ms | 83 | edge-cached static |
| Pinewood Countypinewood-county.pages.dev | 116 ms | 86 | edge-cached static |
| Northwater Healthnorthwater-health.pages.dev | 169 ms | 86 | edge-cached static |
curl -w time_starttransfer); Lighthouse run
headless on each live URL. The Drupal figures are the same Halcyon site running locally as a
Drupal 10 origin — ~1,100 ms is its cold cache-miss render, ~20 ms is a
warm page-cache hit. These are fictional demo sites; your own site's numbers will
vary with content, network, and location. The point isn't the exact milliseconds —
it's that the static copy has no render cliff and no server to attack.
Want this for your site?
See what the public internet can see about your WordPress or Drupal site today — then picture it served like the demos above: unbreakable.
Questions about forms, lock-in, or how editing works? Read the FAQ — or see pricing.