A decision brief for leadership · July 2026

A website that can't crash.

Today, innova.co is fast and online largely because Cloudflare already sits in front of itand carries most of the load — while a single aging server quietly does the one job that keeps the site fragile and holds the team back. This is the case for finishing that move ontoAstro + Cloudflare: a site with no server to crash, built with AI, that gives the team its hours back for growth. Every claim below is backed by a real number from our own systems.

The page you're reading is itself built on the proposed stack — prebuilt, served from Cloudflare's network, with no server.
01

The uncomfortable truth about speed

The site feels fast — but only because Cloudflare hands out a saved copy. Behind that copy, the server is slow. We timed the same pages both ways:

Cloudflare's saved copy
37 ms
Home, from the server
975 ms
Contact, from the server
1,514 ms
Docs, from the server
3,522 ms

When the saved copy isn't ready — a new page, an edit, a form — a real buyer waits on that slow server. We pay to keep it alive just so Cloudflare has something to copy.

Remove the server, and the fast copy is all that's left — instant, every time.
02

Security in the age of AI

The argument that matters most — and it's forward-looking: the target keeps growing, attacks are automated, and we can't predict what's next.

11,334
New WordPress holes in 2025
up 42% in a year — the patch list never stops growing
~92%
Aimed at plugins & themes
of WordPress attacks target add-ons — we run ~40
140,193/mo
Automated attacks on us
bots scanning us non-stop — wp-login/xmlrpc guessing, PHP-file probes
Unknown
The next threat
AI launches new attacks faster than anyone can patch — can't pre-fix the unknown

Today we stay safe by patching — racing to close each hole before a bot finds it. AI makes that race worse: attackers now exploit weaknesses at machine speed, for almost nothing. Winning it every day, forever, isn't a strategy — it's a standing risk.

The only defense that doesn't depend on winning the race is not having the holes at all.

On the new setup, what attackers hunt for isn't there: no WordPress, no plugins, no database, no login. What's left is prebuilt pages behind the same Cloudflare network that already blocks those attacks. Holes to exploit: effectively zero.

03

Who visits — and why the stakes are high

Not a high-volume consumer site — a considered-purchase B2B site: fewer visitors, each one worth a great deal, and the audience is growing fast.

756
1,629
3,128
1,359
5,668
12,701*
JanFebMarAprMayJun

Monthly pageviews, 2026 (GA4) — traffic is climbing fast: the last three months drew 3.6× the pageviews of the three before.

* Note: June includes a one-day bot spike. It inflated the visitor count, not the pageviews shown (added ~530 of 12,701), so the trend is real. Tracking began Jan 2026 — no prior-year comparison.

~4,500
Real visitors last quarter
GA4, Apr–Jun 2026, one bot day set aside
4m 22s
Average time on the site
studying products, not glancing
72%
On a desktop
research-the-purchase, work-computer — classic B2B

The expensive event here isn't a lost click — it's the site stalling or breaking while a serious buyer is evaluating us. And buyers land on the slowest pages: the 3.5-second docs page drew 584 visits last quarter, contact pages over 1,200. As traffic climbs, so does the cost of staying fragile.

04

We're already two-thirds on Cloudflare

Here's the good news — and the pivot of this whole case: we're not adopting a new platform. We're finishing a move that's already most of the way done.

64% · Cloudflare
36% · server
Served straight from Cloudflare — never touches our serverThe fragile part that's left

The fast part and the safe part already live on Cloudflare. Only the page-building server is left — the part that crashes, gets attacked, and costs us. Move it over, and there's nothing left to babysit.

"Why Cloudflare and not somewhere else?"

Delivery is a network problem, not horsepower — so the question is "which network," and we're already on Cloudflare: it already caches our pages and guards them today.

05

What we'd build instead

Build every page once, ahead of time, and serve it from Cloudflare's network worldwide — with no server in the middle to crash, slow down, or be attacked.

Today
Visitor
Cloudflare
hands out a saved copy — and hides the problem
One server
rebuilds every page on demand · runs all 3 sites · single point of failure · 1–3.5s
The new setup
Visitor
Cloudflare edge
prebuilt pages, served instantly from 330+ cities
No server
each site is its own files, delivered independently — nothing to crash or patch

Same content, no server of our own. Each site stands on its own — one site's spike can't drag the others down.

Every kind of content is covered

Every type of content we have gets a fast, low-cost home on Cloudflare — with no server to maintain:

ContentWhere it livesWhy it's better
Text & product pagesCloudflare edgeInstant to load, with nothing that can crash
ImagesCloudflare edge, auto-optimizedLighter and faster automatically — better on mobile
Docs & datasheetsTurned into real web pagesFaster, searchable, and found by Google — unlike a PDF
VideoCloudflare StreamBuilt for smooth video, still no server of ours
Brochures / PDFsOur own brochure viewerThe exact system we already run in production today
Forms & lookupsTiny functions, run on clickCost pennies, and only when someone actually uses them
And the future — puzzles & games

None of it brings a server back. Puzzles and games run in the visitor's browser, not on our machine. If a game saves a score, those few kilobytes go to Cloudflare — pennies, still no server. We keep that door open by design.

We wouldn't be the first — global brands already run on Astro

The exact stack this document argues for is proven at scale. A few names shipping on Astro today (each is a live link):

Source: Astro's official showcase (astro.build/showcase).

06

The money

It isn't zero — a Cloudflare plan and domains still cost something. But the server bill collapses from a fleet of machines to a small flat fee.

Today — DigitalOcean alone
~$4,700/yr
New — full stack (est.)
~$360/yr

DigitalOcean: $391/mo (real May invoice) = ~$4,700/yr — prod + replica + staging + backups + IPs. On top: Bluehost hosting ($359.64/3 yr + $22/yr domain), a Jetserver, licenses, and domains. The new stack is estimated at ~$300–500/yr.


07

Appendix — where every number comes from

Nothing here is a guess. Sources, so any number can be checked.

The numbers

  • Traffic & audience (~19,700 pageviews · ~4,500 real visitors · 3.6× prior-quarter pageviews · 4m22s avg · 72% desktop · 584 doc-page views): Google Analytics 4, innova.co property, quarter Apr–Jun 2026, pulled 2026-07-02. Growth is quarter-over-quarter within 2026 on the pageview metric (~19,700 vs ~5,500) — the metric the one-day Jun-22 bot spike did not inflate; tracking began Jan 2026, so no prior-year comparison is claimed, and the bot day is excluded from the visitor count.
  • Speed (37 ms cached vs. ~1s / 1.5s / 3.5s from the server): live measurement of innova.co on 2026-07-02 — cached responses vs. the same pages forced to the origin server.
  • Cloudflare: 64% served from cache · 140,193 attacks blocked in 30 days (266,596 in 90) · 6.4% of traffic daily · 2.2M requests/mo: Cloudflare analytics for the innova.co zone, pulled 2026-07-02.
  • Security treadmill (11,334 new WordPress vulnerabilities in 2025, +42% · ~92% target plugins/themes · ~40 add-ons): published 2025 industry vulnerability data + our own site's plugin count.
  • Cost ($391 DigitalOcean, May 2026 — prod + replica + staging + backups + reserved IPs · plus Bluehost WordPress hosting, a Jetserver, and domains · ~$400–700/yr licenses): real DigitalOcean invoice #546276003; Bluehost invoice #95323646 (WordPress Basic Hosting $359.64 / 3 yr + $21.99/yr .com domain). The new-stack figures (~$240/yr plan · ~$60 Workers · ~$12 R2 · Stream if used → ~$300–500/yr) are estimates from published Cloudflare pricing, not a bill.
  • Brochure viewer: runs on Cloudflare (Workers + R2) in production today — confirmed live 2026-07-02 against the production viewer.

Rebuilding innova.co — decision brief, July 2026. Built in Astro, served as a static site on Cloudflare — the same stack it recommends. The medium is part of the argument.