Very nice to see these dev tools get an exit. e.g. I love `uv` and friends but did consider that perhaps dev tools are just a bad business and then no one will go into making that kind of stuff. Good exits means more of these tools.

I have only used Astro for toy stuff but it seemed neat. Congrats to the team.

EDIT: To put paid to the sidebar discussion below, yes I meant "for instance, consider `uv`; they might do these nice things and go nowhere but now that companies like Bun and Astro have gotten acquired, it demonstrates a future for others; therefore we will get more things like Astral's `uv` and so on". Hope that clarifies.

I’ve used Astro on Cloudflare for a few years for my personal website (username.com). They’ve both been absolutely fantastic, I can’t say enough good things about both of them. My website has all 100s on PageSpeed/Lighthouse, and that’s because of the performance focus of both Astro and Cloudflare. No credit to me at all. It was mainly because Astro prioritised shipping 0 JS unless it was absolutely necessary and Cloudflare is exceedingly good at serving static HTML.

But I also see the difficulty that Astro faced here. Despite being happy with the framework, I never paid for it. The paid offerings didn’t strike a chord with me. And it was partly because whatever they offered, Cloudflare already offered on a very generous free tier.

I'm glad the team have got a second life within Cloudflare,. I'm happy for the people who've given me such excellent software for free for years. Thanks folks!

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.

I don't understand how Cloudflare's bottom line benefits:

Some here say they gain Astro users, that Cloudflare will become part of the default deployment. But given Cloudflare's current scale, how much are Astro's users worth? Is it even worth the distraction for Cloudflare? Companies lose energy to lots of small, low-value operations.

Most acquisitions begin with announcments that nothing will change, in order to retain customers and employees. They say '<acquistion> is so great, we don't want to interfere, and we're keeping existing management and letting them run things'. After the transition period - often 1 year - the old managers leave and the big changes happen, sometimes including shutting down the product because it was an acqui-hire all along or an IP acquisition.

It seems like Cloudflare must perceive some profit beyond what is announced.

> 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?

I agree a good exit for devtools is good for devtools. I'd like to understand it better.

The Astro claim is that astro developers will all continue full-time on it. So why acquire it instead of supporting it?

The reason given in complementarity (content and infrastructure), but doesn't that mean that Cloudflare is moving into content? Perhaps it's fair to say some content fits better with Cloudflare, or making it easier to just have static sites is beneficial to Cloudflare?

Is there a convention about announcements, for the acquired to announce happily first to bring customers, and then the acquirer to confirm their benign intentions? When can we expect Cloudflare's take?

Astro is my favorite framework for static sites. It's hard to describe but it just "makes sense". You don't need complex build setups and you can get the best of all worlds with great SSG capabilities + can easily express things with React when needed for example.

I wish there was another path to monetization besides joining a larger company but I'm happy that the team will get to continue building out an amazing framework!

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 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.

I love Astro - migrated my blog there (here it was a gradual improvement), migrated company website there (here a lot, to joy of everyone). In the times of vibe coding, there is much less reason to use WYSWIG website editors. In our company, a non-technical assistant, modified website with Claude Code.

I hope that this acquisition will go well. It would be sad to lose this great framework. At the same time, we deploy on Cloudflare. So their business is to keep Astro cool so that more people will use Claudflare, it would be a win-win!

I'm a little wary of this. I'd been using Gatsby for my static websites for a long time, until it got eaten up by Netlify and then sunset; I switched over to Astro at that point, but now I'm getting a sense of déjà vu.

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.

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...

Been running my technical knowledge base on Astro for about a year now (ketankhairnar.com). Congrats to the team on the acquisition - here's what stood out from a product/engineering perspective:

Content modeling that actually scales. Built a three-tier system: Concepts (foundational knowledge) → Deep Dives (series-based learning paths) → Systems (production case studies). Each concept tracks prerequisites, related topics, interview relevance by level (L5-L8), and links back to which deep dives use it. Zod validates everything at build time. This isn't a blog template - it's a knowledge graph with static output.

Islands architecture delivers on its promise. React hydrates only for search (Fuse.js across all content types) and a few interactive bits. Rest is zero-JS HTML. Coming from years of Next.js, the bundle size difference is stark. Users on flaky mobile connections notice.

Extensibility without framework lock-in. Wrote a custom Shiki transformer for ASCII diagram highlighting - ERROR renders red, FIX green, DECISION orange. Dynamic OG images generated at build via Satori+Resvg. No Lambda cold starts, no external services, just static assets. Infra cost: basically zero.

View Transitions shipped before others figured it out. One import, smooth page transitions. Small detail, big UX lift.

Where it gets tricky: Complex content relationships require multiple getCollection() calls and manual joins. Works fine, but a query builder would help for sites with heavy cross-linking. Also, the content layer is powerful but documentation assumes simpler use cases.

Product observation: Astro found a real gap - content sites that need occasional interactivity but don't want SPA overhead. Most frameworks optimize for apps and retrofit content. Astro did the opposite and it shows.

Curious how Cloudflare integration plays out. Edge rendering + this content model could be interesting for personalization without sacrificing static performance.

Open source alone can’t sustain companies long-term. Eventually everyone needs a bigger, safer home.

I love astro, it's been such a pleasure to use and totally solved my need for a flexible platform. I managed to retire a bunch of Wordpress sites and I've never looked back. Hopefully I can still run it on netlify.

Astro on Cloudflare workers has been my goto stack for multiple years now. I am very happy with it, and hope this makes the integration stronger.

Now we just need Cloudflare to buy one of the DBaaS companies so they have a solid relational offering.

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

Astro to Cloudflare, Bun to Anthropic. Good trend seeing people toiling away at OS financially rewarded.

This news made my morning. I can't wait to see how they improve Astro build times and hosting on Cloudflare.

All wrongs in Gatsby have been gotten right in Astro. What will happen next remains to be seen, but currently Astro is amazing for a few specific cases it covers. The performance, developer experience and documentation are all great.

Cloudflare's goal is to become the default choice for anyone deploying an app to the cloud. It makes sense for them to support popular frameworks such as Astro, so that they can ensure that the frameworks work very well on their Workers platform.

This is a great news for Astro. It ticks all the boxes when being used to build heavy content and SEO driven websites. I've been using (Astro + Cloudflare workers/pages) as my go-to stack to build my Java gamedev resources website [1] and gaming portal [2], so far and the experience is very positive. Deploying static files to Cloudflare edges feels natural and frictionless.

Still a bit concerned that it might be too tempting to build an entire website infrastructure around cloudflare, which is a single point of failure. But there is really no better alternatives at the moment. I tried self-hosting but eventually resorted to cloudflare because of bad bots, ai, scrappers kept hammering on my sites.

[1] https://raizensoft.com/tutorials/ [2] https://ookigame.com

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

Hope that SSR remains first class as time goes on. I think Astro’s DX is superb overall, and am bullish on server-rendered components in MPAs with a sprinkling of hypermedia libs for better UX.

Some features of my SSR-based side project feel like I had to hack them on, such as a hook that runs only on app start (hacked in via middleware) or manually needing to set cache control headers for auth’d content.

All in all, really happy with it. And it isn’t next.js.

I have always liked Astro. It also works great with AI tools since its combination of markdown and code. Was able to vibe code a quick blog template and deploy to cloudflare in minutes with an existing headless backend - https://sleekcms-astro-blog.pages.dev/

Great for Astro..

About the download stats for open source frameworks and libraries.. I keep reading claims of "millions of weekly downloads" -- surely this is a noisy metric, right?

NPM just counts GET requests. A significant number of those must be from CI/CD pipelines, mirrors, build servers, etc.

It still signals popularity, but probably to a much lesser degree than implied.

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

Adobe could have benefited from doing this acquisition but they can be somewhat forgiven as they are already pushing Edge Delivery Services which is based in NextJS although it's a different approach. Combined with the Universal Editor they have a solid headless authoring setup for enterprise CMS.

But I really feel like Akamai is who dropped the ball here, this was a low hanging fruit for them and they're lacking offering this capability to offer their corporate clients as they transition to full headless. Now it's going to be their competition (Cloudflare, even Fastly through Adobe & the EDS push) who will try to take a portion of their cake.

I've been using Astro for a couple years and it's delightful. I actually started using it for my docs because I saw Cloudflare was using it. I hope they are a good steward of the tech!

Cloudflare is getting into static site hosting game, like Vercel.

Oh no. This isn’t good. I’m glad that the team gets a payout but as an Astro user I don’t love it being owned by CF and that the goals of the project (at least indirectly) goes from the best way to deploy it to the best way to deploy it using CF.

Wow, these are the same people behind Pika/Skypack and Snowpack. I can remember the day when they announced the Astro project, and now it's joining Cloudflare, incredible progress.

My favorite framework, and what has brought me much deeper into the world of web development. It's what I have used for me personal page https://bryanhogan.com/ . I'm happy to see it get funding, although I hope this doesn't introduce entshittification. So far I'm hopeful though.

It's the first framework I recommend to web dev beginners, after they have built something with plain HTML and CSS.

What's the next best/popular alternative to Astro?

Used this for a portfolio site and and not sure if this news is good or bad for its future.

Crossing fingers (but not holding breath) this doesn't lead to vendor lock-in or otherwise wreck Astro.

From a developer perspecive, I was going to go "Ahh shit here we go again"

But to be really honest, thinking more about it. atleast from an "AI" bubble perspective, Cloudflare is pretty rock solid and isn't involved in the AI bubble deals whereas vercel has

If you were to use cloudflare workers say the past few months, you would've noticed some serious UI/UX improvements and its projects highlighted astro template was one of the first things (I think second was sveltekit iirc)

Anyways thinking about it now, I am sure that cloudflare must have been in talks with them for quite some time and they had the astro deployments on cloudflare workers so they must have seen its usage and other data we have no idea about to justify this purchase

That being said, I had been part of astro community almost exactly the time they had partnered up with turso (It was my holidays so I wanted to build a website from scratch, I sadly lost it but it was really cool and it had BMO from adventure time's pixel art that I lost oof :<)

So I was in their discord when they had just joined turso for astro DB and at that point, you couldn't host it locally (some tried with wasm) not sure what's the reality now though. But its interesting to see this because cloudflare offers a turso (serverless sqlite) alternative as Cloudflare D1, So we might see Astro shift to d1?

Once again, I have not been part of community for almost around 1-2 years so I don't know the current state of Astro aside from tweaking around making my own custom editor in bun for some astro templates (astro templates are really cool)

Perhaps, we are gonna see astro templates website + cloudflare workers to create an instant deployment of astro templates on cloudflare workers as a first class citizen. Honestly I would love that because cf workers/pages are free/cheapest in the whole market.

I hope that Astro still stays local first and still its serverless features can benefit everybody and not just cloudflare (looking at you vercel for nextjs)

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

Congrats! I love Astro and published an i18next plugin https://github.com/gutenye/astro-i18next

I hope they maintain a clear path to delay separately too.

With these sort of combinations the deploy to cloudflare button gets ever bigger than over time. And then features get added that only work with CF and eventually it’s still open source but only half the stuff works standalone etc

That said - good for them.

Is that a good deal for the employees of Astro? They're now Cloudflare employees, which I guess looks good on your CV.

But do such acquihires usually result in higher salaries for regular (non-leadership) employees or? Also, what about NSOs?

Astro is my favorite way to build websites (at least, of the kind its great at) and I'm happy for the team; Cloudflare is a super cool place to work. Excited to see in what directions this will develop. They have a real shot at being the next Next.

I hope they've got rewarded astro...nomically well lol!

My apologies friends, I could not resist!

Congrats Astro team!

Makes perfect sense. I use Astro with Cloudflare for all my frontend projects.

Only mildly surprising - Astro + CF Pages/Workers have been my go-to for when I want to spin up a static site or do anything else and it does feel like they've been really working on the integration between the two.

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

undefined

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.

Congrats to Fred and team! Developing and maintaining a complex framework takes lots of funding, and I’m glad Astro found a new home that provides that.

With [Mastro], we have a different approach. The name originally stood for "minimal Astro", and we’re staying true to that. At just ~700 lines of TypeScript, Mastro will always be easily maintainable – even if by just a single person. And it's amazing how much you can do if you're very deliberate in your API's design.

[Mastro]: https://mastrojs.github.io/

Love Astro and it is exactly my stack with Cloudflare but wow, the "Forward-Looking Statements" disclaimer is longer than the press release itself

I’ve been expecting this for a while - their last few releases have all had big features included for their cloudflare adapter

I don’t want a framework that’s coupled to a hosting provider.

undefined

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.

This is great news for the Astro team. Cloudflare has been doing a lot of good things for the open source community lately.

Damn. What alternatives does HN recommend?

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

I hope CLoudflare or another tech company buy deno. Deno is great, its lacking a big brand sponsorship.

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

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

ITT People arguing about how cloudflare is gonna unfairly favor their own platform and lock people in by making easier to deploy astro sites as if you can't already do it just by connecting a git repo to cloudflare pages with 1 click.

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.

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

I knew it was too good to last hah

Congratulations!

This spam LLM account "MarkusAllen" (towards the very end) could be used by an adversory to discredit books / courses /"youtube channel" they link to. This is reverse psychology attack vector made possible by an LLM.

i'd personalloy love a quick video demo on the home screen, with someone walking through the experience of using the app; other than that, looks interesting;

undefined

Astro is life!

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

Vercel 2.0

Awesome!

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.

This sucks

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.

I found that Vite does a great job of deploying static websites. All I had to do was add Vite as a dev dependency in my pacakge.json and make sure all the page routes in vite.config.js.

I've been skeptical about trying Astro because it seems to have unnecessary complexity. Also, I don't see any evidence that Cloudflare is going to prioritize making Astro easier to use.

> Now Astro is downloaded almost 1,000,000 times per week [...]

Are these numbers supposed to provide any sense of the popularity if you're not often looking at npm trends?

Did they just break Cloudflare?

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

is astro any good ? havent tried it yet

[dead]

[dead]

[flagged]

[dead]

Vercel buys frameworks. Cloudflare does the same.

We all lose while they all tell us we're winning.

Oh wow, Cloudflare enschitification is practically in real time right now.