// pillar
Why we build on Cloudflare and Astro
Because a website should be fast, secure, cheap to own, and entirely yours. Classic WordPress makes that hard. Here's how our approach works.
// the difference in approach
Dynamic site vs. static site
Classic WordPress (dynamic)
On every visit the server runs PHP, queries a database, assembles the page, then sends it. Every plugin adds slowdown and a new security risk. That's why it needs stronger (paid) hosting and constant upkeep.
Our approach (static, Astro)
We pre-build the site into clean HTML. Cloudflare serves it from the nearest of 300+ locations. No database, no PHP, no waiting. Faster, safer, cheaper.
// under load
Under a surge of visitors, there’s nothing to crash
WordPress under load
Every view runs PHP and a database query; cheap hosting ships a handful of workers. A surge — an ad, a sale, an event — exhausts them and the site goes down. The classic “our site crashed during our biggest sale.”
Our approach under load
Static pages are served from the edge (300+ locations) — thousands or millions of concurrent visitors are routine for a CDN, and the origin is never touched. The difference isn’t that we’re faster under load — there’s nothing to crash. The fast path is the default, there’s no slow origin; the only dynamic part is the small, serialized checkout, where 1–2 seconds goes unnoticed.
The crowd is static. The transaction is dynamic.
// three foundations
What this means for you
Our approach stands on three pillars. Each has its own page with all the details.
-
Free hosting
Cloudflare Pages serves your site with no hosting cost. For smaller sites you pay only the domain.
More -
Worry-free security
No database or plugins means nothing to hack. A static site has a near-zero attack surface.
More -
Everything is yours
Cloudflare, email and source code transfer to your name on handover. You are nobody’s hostage.
More
// the stack
What your site is made of
These are the same building blocks this very marketing site runs on.
- 01
Astro 6
Modern framework for blazing-fast sites with minimal JavaScript.
- 02
Cloudflare Pages / Workers
Hosting and dynamic functions at the edge of the global network.
- 03
R2
Storage for images, documents and video (played straight from Cloudflare).
- 04
D1
SQL database for apps and backend editors.
- 05
Resend
Reliable email delivery (inquiries, notifications).
- 06
Cloudflare One (optional)
Secure access for internal tools.
// efficiency
Millions of websites are doing more work than they need to.
WordPress is one of the greatest publishing systems ever built. For newsrooms, magazines, blogs and content-heavy sites it’s an excellent choice — multiple editors, revisions, workflows, plugins and a mature ecosystem make it incredibly capable.
Your website shouldn’t need a database just to display your opening hours.
Every day, millions of simple business websites start a PHP runtime, connect to a database, run plugins and background tasks, and consume computing resources — just to serve content that changes a few times a year.
A modern static website doesn’t remove features. It removes unnecessary work. Instead of generating every page on demand, it builds pages once and serves them straight from the edge — without a database, without PHP, without plugins.
- 300 page views / day
- ≈ 12 billion page requests / day
- Dynamic stack: PHP → database → plugins
- Millions of CPU-hours every year
…to display content that was already known yesterday.
When a website rarely changes, rebuilding it on every request is like starting a truck to deliver a single envelope across the street.
This isn’t an argument against WordPress — it’s an argument for using the right tool for the job.
Static websites don’t just load faster. They ask the internet to do less work.
How we estimated these numbers
A conservative thought experiment to illustrate scale, not a precise measurement. Assumptions: ~200 million active websites worldwide; ~43% use WordPress; roughly 40 million are simple brochure or company sites that could reasonably be served statically; each gets ~100 visitors/day viewing ~3 pages; dynamic page generation averages ~10 ms of server CPU per request after caching and background work. That yields ≈12 billion page requests/day, ≈120 million CPU-seconds/day, ≈12 million CPU-hours/year. Real numbers vary widely with traffic, caching, hosting and complexity. The point isn’t the exact figure — it’s that millions of sites perform dynamic work that many simply don’t need.
// frequently asked
Frequently asked questions
Is Astro/Cloudflare right for a small business?
Especially. Smaller businesses gain the most: a fast site, no hosting costs and no maintenance.
Can I have a blog and post regularly?
Yes. We build a backend editor where you publish posts yourself, manage keywords and upload images.
What if I need dynamic features (login, database)?
Handled with Cloudflare Workers and D1. → /en/web-applications/
Want a site on this technology?
Send an inquiry and get a free quote within 48 hours — no obligation.