
Use to summarize this article

Cloudflare’s January 2026 acquisition of the Astro team changes very little for a marketing site today. Astro stays MIT-licensed, open-governed and deployable on any host. What shifts is the odds: funding risk falls, Cloudflare becomes the best-supported home for Astro, and the roadmap now sits with one company.
On January 16, 2026, Cloudflare announced it was bringing The Astro Technology Company, the team behind the Astro framework, in-house. Within hours, forums asked the same two questions: will Astro stay open, and will it still run anywhere other than Cloudflare?
10 months is long enough to stop guessing. Astro has shipped two major versions since. Cloudflare has launched a CMS built on top of it. And at least one change has landed that can only be called Cloudflare-shaped.
In this blog we discuss how this acquisition affects your marketing website. Is the site you’re paying for still on safe ground? Has anything about hosting, cost or SEO changed? And what should you do this quarter?
Important events and updates since Cloudflare’s Astro acquisition
Astro has seen several updates within the 10 months after Cloudflare acquired it. The table below lists down the most important ones that you need to know.
Cloudflare acquired The Astro Technology Company, and the full-time Astro staff became Cloudflare employees.
Although the deal terms weren’t disclosed, the public commitments were consistent across both announcements: MIT license, open governance, a public roadmap, portability across clouds, and continued support for the Astro Ecosystem Fund alongside partners including Webflow, Netlify, Wix and Sentry.
There were changes within the company and the people who decide what gets built next. While the code remains free to use or fork, the priorities are now set inside one company.
How Astro renders pages, the HTML your visitors and crawlers receive, the license on released versions, and any requirement to host in a particular place still remain the same.
Why did Cloudflare want Astro?
Open-source frameworks struggle to fund themselves. Astro’s CEO said publicly that joining Cloudflare lets the team focus on the framework instead of on monetizing it.
For Cloudflare, the logic is distribution: Workers and its storage services only grow if developers build on them, and a framework is the front door.
Cloudflare is also a heavy Astro user itself. Its developer documentation site, with more than 8,000 pages, was one of the benchmark sites in Astro’s own release post.
The obvious precedent is Vercel and Next.js: a company stewards a popular framework, keeps it open, and builds the smoothest path to its own platform. We read Cloudflare as aiming for the same shape, with a stronger open-source reputation to protect.
What does Cloudflare acquiring Astro mean for your marketing site?
Here’s what changed for your marketing site after Cloudflare acquired Astro and what stays as it is.
Nothing really changes for a marketing site. In fact, things seem to have gotten better.
Astro 7 and 7.4: What marketing teams need to know?
Astro 7 is a speed release. The .astro compiler was rewritten in Rust, the default Markdown and MDX pipeline moved to a Rust-based processor called Sätteri, queued rendering became the default engine, and the build tooling moved to Vite 8 with the Rolldown bundler.
In Astro’s own benchmarks, run on an Apple M4 Pro laptop, builds were 15 to 61% faster. The marketing site astro.build (about 308 pages) dropped from roughly 63 seconds to 24. Cloudflare’s developer docs went from about 387 seconds to 262.
Astro 7 also added Advanced Routing (a src/fetch.ts file for full control of the request pipeline), stable route caching, and agent-friendly development features such as a background dev server and structured JSON logs. Those matter to your developers more than to you.
What changes with an upgrade?
- Stricter templates: The new compiler no longer silently repairs your HTML. Unclosed tags and unterminated attributes now produce errors.
- Whitespace changes: Spacing between inline elements now follows JSX rules, so some text can render without the space it used to have. Budget visual QA, especially on pages with inline links and buttons.
- Markdown pipeline: Sätteri is the default. Sites with custom remark or rehype plugins must switch to Astro’s unified-based package to keep them.
- Runtime and tooling: Node 22 and Vite 8. Most custom Vite plugins keep working, but test them.
- Matched versions: Since 7.4, the Cloudflare and Markdoc integrations require Astro 7.4 or later, so upgrade them together.
- Removed features: Astro DB’s command-line login and link commands are gone, which matters only if you used them.
- Coming from Astro 5? You also inherit the Astro 6 changes: Astro.glob() removed and Cloudflare bindings accessed through direct imports instead of Astro.locals.runtime.
How is Astro 7.4 different?
Astro 7.4 comes with a timings flag that shows where a build spends its time. The release also allows different image services for prerendered and on-demand pages, adds a notFound() handler for custom entry points, and warns about font settings a provider can’t serve.
Astro 7.4 introduces two experimental features: parallel prerendering across worker threads and custom redirect pages for static builds.
It also raises the minimum Node 22 patch version, so update Node before updating Astro.
Should you upgrade?
Vite 8 landed right after Astro 6 and Vite majors typically force an Astro major. Whatever the cause, plan for it: put an upgrade window on the roadmap twice a year. Skipping upgrades won’t save you the operating cost. In fact, it will make each hop more expensive.
Pages versus Workers: How does this Cloudflare change impact your website?
Astro’s Cloudflare adapter now targets Workers, not Pages. That affects server-rendered sites, not static ones.
What changed
- Astro 6 rebuilt the Cloudflare adapter so that development, prerendering and production all run in Cloudflare’s real Workers runtime
- Astro’s documentation now states the adapter no longer supports deployment on Cloudflare Pages, and tells existing users to migrate to Workers
- Cloudflare itself recommends Workers for new projects
The table below shows how this affects various site setups.
EmDash: What Cloudflare’s CMS tells you?
On April 1, 2026, Cloudflare announced EmDash, an MIT-licensed, TypeScript CMS built as an Astro integration and pitched as a spiritual successor to WordPress. A CMS roundup reports version 1.0 on September 28. It requires Astro 6 or later, server output and React, and stores content in SQLite or Cloudflare D1 with media in R2.
What it means for you?
EmDash is worth watching, but a CMS that just arrived may not be a default recommendation for a marketing team. However some of the best headless CMS with host-neutral Astro integrations remain the safer content layer.
Amazon Signage came to us with a product that needed a conversion-focused website at enterprise scale. We rebuilt it in Webflow across 20+ pages, and content updates are now 10x faster. The lesson for any framework decision is the same: the speed of your content operations matters more than which tool renders the pages.
Risk analysis for Cloudflare’s Astro acquisition
The table here shows various possible risks associated with Cloudflare buying Astro and how you can deal with them.
Note: None of these is a reason to leave Astro but to build carefully.
How does Cloudflare acquiring Astro affect its SEO, performance, and AI visibility?
Here’s how Cloudflare buying Astro affects its overall performance, SEO, and AI search visibility:
Rankings
Google doesn’t rank frameworks. It rewards crawlable HTML, useful content, speed and a clean experience. Astro’s static-first output is unaffected by the deal, and Astro 7’s build speed is not a ranking factor.
Performance
Core Web Vitals on Astro sites are usually decided by implementation: image handling, font loading and, above all, third-party scripts such as tag managers, chat widgets and session recording. Those slow a fast framework far more often than the framework slows itself.
AI visibility
Static, server-rendered HTML is easy for crawlers that don’t run JavaScript, which is a real advantage for getting cited. The risk is in the layer in front of your site.
- Cloudflare began blocking known AI crawlers by default for new domains in July 2025
- In July 2026 it announced a finer model that classifies crawlers as Search, Agent or Training
- From September 15, 2026, training and agent crawlers are blocked by default on pages that show ads, for new domains, new sites from existing customers and free-tier customers, while search crawlers stay allowed
A B2B marketing site without ads may not be hit by that default, but don’t assume. Check the AI-crawler settings in your Cloudflare dashboard and your robots.txt, confirm how the AI products you care about are classified, and make sure you haven’t blocked the systems you want citing you.
The portability test
There’s an important question that you must ask: could we redeploy this site on a different host within a week? If you can answer yes to most of these, the acquisition stops being your problem.
- Content lives outside the framework. A headless CMS or Markdown in Git, not content tangled into templates.
- Static by default. Server rendering only on pages that truly need it.
- Platform bindings are isolated. KV, D1, R2 or Durable Objects sit behind a thin service layer, not scattered through page files.
- Redirects, headers and forms are defined in code, not only in a dashboard someone configured two years ago.
- Images use a standard pipeline, not a vendor-only transformation URL scheme.
- You own the accounts. The Cloudflare account, DNS and registrar are in your company’s name, not your agency’s or a former employee’s.
- Builds are reproducible. Pinned Node version, a lockfile, and a staging deploy on a second host to prove it.
- Analytics, consent and tag management are independent of the host.
- The deployment path is documented. Everyone knows whether production deploys to Workers or Pages, and the CI configuration matches reality.
Keep, build, or migrate: What should you do?
Based on your current situation, there can be different ways you deal with this acquisition and upgrades. The table below helps you understand what’s the best.
Make sure any decisions are well thought rather than being in a haste of migrating.
Conduct a review every quarter using this checklist. If more than 3 turn negative together, that is the moment to reassess.
Build better with Flowtrix
Astro remains a very good bet for content-led B2B SaaS marketing sites, provided the site is built so that Astro and Cloudflare are both replaceable parts. We would rather see a team on Astro 7 with a tested exit plan than on a “safer” stack nobody can ship changes on.
Want more details on what should be your next step after this acquisition or want to build on Astro for better results? We are all ears. Let’s connect!














