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.
innova.co is WordPress on a single rented server, with Cloudflare in front smoothing it over. That one design is the root of nearly everything fragile and high-maintenance about it.
One design choice drives it all: an always-on machine that rebuilds pages on demand, for a site whose pages barely change. Remove the machine, remove the fragility.
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:
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.
The pivot of the whole argument: we're not adopting a new platform — we're finishing a move that's already most of the way done.
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.
Delivery is a network problem, not horsepower — so the question is "which edge network," and we're already on Cloudflare: it caches our pages, guards them, and runs our brochure viewer today.
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.
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.
On the new setup, what attackers hunt for isn't there: no WordPress, no plugins, no database, no login. What's left is static files behind a network that already blocks 140,000 attacks a month.Holes to exploit: effectively zero.
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.
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.
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.
Build every page once, ahead of time, and serve the finished pages from Cloudflare's edge — with no origin server in the middle.
Same content, no origin server. Each site stands on its own — one site's spike can't drag the others down.
Each content type goes where it's cheapest and fastest — all on Cloudflare, no origin server:
| Content | Where it lives | Why |
|---|---|---|
| Text pages | Cloudflare Pages (built by Astro) | Trivial — this is what static delivery is best at |
| Images | Cloudflare Pages, auto-optimized | Astro converts them to modern, lighter formats at build time |
| Small docs & datasheets | Converted to native web pages | Faster, searchable, and indexed by Google — unlike a PDF |
| Video | Cloudflare Stream (embedded) | Purpose-built for video delivery, still no server of ours |
| Heavy brochures / PDFs | Cloudflare storage + the brochure viewer | The exact system we already run in production today |
| Forms & redirects | Tiny edge functions | Run only on submit, cost pennies, scale to zero |
Content becomes files in one place, not an admin panel. Word/Drive docs convert over automatically — Drive and Word stay for writing. Want a friendly editor? We add one on top; the output stays 100% static.
Almost never. The question isn't "do we have a backend" but "does the public site need an always-on machine?" Forms, a locator, a calculator run only on click, then stop — what edge functions do best, at no idle cost. A real server is only for things innova.co doesn't do (live accounts, heavy processing).
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's edge — pennies, still no server. We keep that door open by design.
The biggest win isn't money — it's the team's time. Today a real share of it just keeps the server alive: patching WordPress and ~40 plugins, chasing the next vulnerability. On the new setup, most of that disappears.
Those hours don't become a "savings" line — they get pointed at growth: image and product work, conversion, new pages, the games. Same team, aimed at growing instead of keeping the lights on.
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.
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, domains. New stack estimated below.
| Today | New setup — Cloudflare | |
|---|---|---|
| Servers (DigitalOcean) | ~$4,700/yr ($391/mo, real May invoice) — prod + replica + staging + backups | $0 — no servers |
| WordPress hosting (Bluehost) | ~$120/yr hosting + ~$22/yr domain (real invoices) | $0 — no WordPress |
| Jetserver | On top — not counted above | $0 |
| Software licenses | ~$400–700/yr (page builder, security) | $0 — none needed |
| Maintenance | Ongoing hours + incident risk | Minimal — nothing to patch |
| New-stack item | Estimated / year |
|---|---|
| The sites — Cloudflare Pages | $0 (free tier) |
| Cloudflare plan (WAF, analytics) | ~$240 |
| Workers — brochure viewer + forms | ~$60 |
| R2 storage — the PDFs | ~$12 |
| Stream — video, only if used | ~$60–180 |
| Domains | renewals — the same on any stack |
| Estimated total | ~$300–500 / yr |
Not zero — but the server side drops from over $5,000 a year across three vendorsto a few hundred. And the real case is still the hours reclaimed and therisk removed — the bill is just the easiest part to see.
A pitch with no downsides is a sales pitch. Here are the real trade-offs — each small, each already solved.
Nothing here is a guess. Sources, so any number can be checked.
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.