The move to Astro and islands architecture

Cloudflare acquired the Astro framework company on January 16. Netlify acquired Gatsby to integrate the Valhalla Content Hub into its platform. Gatsby raised a total of $46.8 million, including a $28 million Series B in 2020. Netlify maintains customers like Twilio, Mattel, and Verizon. Developers choose Astro for content-heavy sites because it ships zero JavaScript by default. Next.js keeps React running through the whole stack and treats interactivity as the rule. Next.js 16 has been the stable line since October 21, 2025, with version 16.3.3 being the latest stable release as of August 2026. This architectural decision affects bundle size, hosting cost, and Core Web Vitals. Astro’s 6.0 major release on March 10, 2026, introduced an experimental Rust compiler and a rebuilt dev server. The 7.0 release landed on June 22, 2026, and the framework reached version 7.3.3 by September 2026.

Performance and the islands approach

Astro uses islands architecture to deliver static HTML and hydrates only interactive components. It uses client directives like client:load or client:visible to control when JavaScript arrives. This method stops a single component from shipping hundreds of kilobytes of code that most visitors never execute. The 7.0 release also added Server Islands, which allow developers to mix static, cached HTML with dynamic, server-rendered fragments on the same page using the server:defer directive. While Next.js uses the "use client" directive to mark components as client-rendered, Astro allows developers to choose exactly when hydration happens through granular directives like client:load, client:idle, or client:visible to maintain a strict performance budget. Next.js is ranked number one in TechnologyChecker’s March 2026 domain census, while Astro holds the number two position. In the Next.js framework, components render on the server but the framework still streams a React runtime and a serialized component tree to the client so React can take over. Developers using Nuqs can also leverage key isolation to ensure components only re-render when their specific key changes. This feature works for React SPA, React Router, Remix, and TanStack Router, but Next.js remains an exception due to its internal use of a single URLSearchParams context. Nuqs version 2.5 added standardized schema generation for tools like tRPC or route schemas, and the 2.6 release added a processUrlSearchParams hook for developers to intercept and transform URLSearchParams.

Framework comparisons for teams

Performance benchmarks show the difference clearly. For content-first sites like blogs or documentation, Astro is 2 to 3 times faster and 50 to 80 percent cheaper to host than Next.js. In a June 2026 measurement, Astro’s docs shipped about 9 KB of JavaScript, whereas the Next.js docs shipped 463 KB. You should look at these numbers before deciding which runtime fits your project. Next.js has 39.1 million weekly npm downloads and 139,687 GitHub stars as of June 2026. Astro has 3.1 million downloads and 59,842 stars. For e-commerce with tens of thousands of product pages, Next.js’s native ISR is valuable because it can rebuild a single product page when a price changes without redeploying the whole site. Astro can reach similar outcomes with edge caching and server islands. In a typical React build, the framework ships hundreds of kilobytes of JS, spins up the virtual DOM, and waits before a button becomes clickable. Astro’s approach avoids this by sending static HTML immediately and hydrating only the targeted components. The Next.js 14.x line exited maintenance on October 26, 2025, which pushed users toward later versions.

Will the gap between these frameworks narrow as Next.js improves its Partial Prerendering?