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.

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!

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.

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?

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.

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

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?

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 wonder if there will be some sort of collab between Hono and Astro given that Yusukue also works at Cloudflare.

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.

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

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!

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

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.

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.

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.

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

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

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)

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

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.

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

My apologies friends, I could not resist!

Congrats Astro team!

[1] https://cto4.ai

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.

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/

Congratulations!

I think donating to the Apache Foundation is preferable.

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

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

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