Cloudflare acquires Astro (astro.build)

Astro is amazing. I've been using it for a couple of years now. Initially only for static sites but now I'm building the UI of all my web projects with it.

I wonder if there will be some sort of collab between Hono and Astro given that Yusukue also works at Cloudflare.

This is cool, I use astro when I just want to spin up a quick site without having to fight the framework (looking at you, Nextjs) and the main thing I disliked was the initiatives around paid extras they had going

Astro and Tanstack are probably the best full-stack routers these days, and Astro wins in terms of the wide support for almost any client-side tech

Why does Cloudflare need a web framework? Most obvious would be they think they can make money from hosting astro sites (like Vercel and NextJS). I hope Cloudflare's impact on Astro will be tiny. But another great thing being swallowed by big tech...

Refreshing to see an acquisition (acquihire?) that just plainly says they were not able to monetize.

It would be good to understand what Cloudflare gets out of the deal. The article is very much just "Astro, but someone else pays the bills!" which is of course lovely for Astro.

Nice. I love astro and I love cloudflare. Most of my static pages are that stack.

I am very disappointed with Astro.

Who is this framework for?

It's been years, and they still don't support unit testing Astro Actions. They still don't support inter-island communication.

"Astro v6 is around the corner" - and the only changes are 1. refactored CLI (why? it's perfectly fine) 2. bumped zod to v4

It's great if you want to build a blog or something, but it's definitely far from great for building apps.

Don't know what they are thinking.

> In 2021, Astro was born out of frustration. The trend at the time was that every website should be architected as an application, and then shipped to the user’s browser to render.

Was it? Hot damn, I knew it'll eventually happen, but we truly are just running around in circles. Eventually these same people will do the same loop around, creating new frameworks because the current "server<>client" model suddenly doesn't make any sense anymore, and of course this should be rendered server-side.

Why are we doomed to repeat this, and why does it happen so quickly particularly in web development? We have each other's histories and knowledge right in front of us, what's missing for us to not continue just running around in circles like this?

Cloudflare: Astro Vercel: NuxtLabs, Next. All open source. What a strange competition.

Damn. What alternatives does HN recommend?

After Netlify acquired GatsbyJS, I am not very hopeful about the future of Astro. I hope to be wrong because Astro is a great framework.

Astro is great. It checks all of my checkboxes. I hope this is not the beginning of the end.

Astro is great and I hope they keep improving after the acquisition.

Given what agents can do, I feel a lot of the sites built on Webflow, Framer and so on will move to code and Astro is a great framework for this.

I like the idea behind Astro, I've used it for a couple websites here and there. I'm a bit worried about the complexity brought by Astro supporting all these different frameworks through its adapters, and how stable and maintainable those websites will be in the future.

For instance: I've been using Astro with Svelte to build static sites with some components that require client-side interactivity. I really like that Astro doesn't ship any JS by default and just outputs static HTML, and when I want some page to have an interactive JS component, Svelte is an option that produces a relatively small amount of client JS.

But: Using Svelte with Astro this way for static sites has been broken since August 2025. As soon as you have a conditionally rendered child component in Svelte, Astro fails to bundle the styles for it in the static output of the site, and it does that ONLY in production, which is really devious, you could build a whole site (using astro dev) without knowing and then it breaks when you deploy it.

The issue is here: https://github.com/withastro/astro/issues/14252

I don't want to be complaining about how quickly issues get addressed in an OSS project that I'm not paying for, I don't blame them for not keeping tabs on every framework integration, I just would love to build websites with the latest versions Astro and Svelte, and I unfortunately have the feeling I should have just gone with SvelteKit for a smoother experience.

Very unexpected but it's a great match. I have been using Astro with Cloudflare Pages and the dev UX is fantastic

I use Astro deployed on Cloudflare, blog-newsletter kind of site [1], moved over from Hugo. If this keeps Astro viable then it seems like a net win.

[1] https://cto4.ai

[flagged]

Perfect direction! Astro has been incredible for small static pages. CF workers are also really easy to impl

Tried Astro after being utterly confused with Hugo templating and found it rather over-engineered. Went with 11tty instead and don't regret it.

Another open source framework likely be dead soon, what are the alternatives ?

This sucks

Welp, I'm worried. I like Astro, but maybe it's time to make my own SSG, to not ever end up in the hand of a few big-sharks that consolidate and enshittify everything.

So this is what happens to open source now? It runs out of money and one of the big corpos gobbles it up. Lovely.

I think donating to the Apache Foundation is preferable.

Surprised this isn't in the article, but Cloudflare has been moving all their docs to Astro's Starlight docs framework. I'm guessing this is a way to prioritize features for Cloudflare:

> https://blog.cloudflare.com/open-source-all-the-way-down-upg...

I'm incredibly relieved they didn't join Vercel (which everyone else seems to be doing these days).