Skip to content
← All articles

Comparisons

Next.js vs Astro for a SaaS in 2026: marketing site, app, or both

Astro or Next.js for a startup: where each one fits, real-user speed data, SaaS starters, hosting costs and security in 2026, and the common setup that uses both.

Vas 14 min read
Ask AI about this article ChatGPT Claude Perplexity .md

A startup usually needs two things: a site that explains the product and an app where customers log in and work. Astro and Next.js are the two names that come up most often for both. This article is about that choice: what goes on the main site, what goes into the app, and when one framework is enough for everything.

If you only need a company website, a landing page or a blog, read our comparison of Astro and Next.js for a company website: it covers that case in more detail. Here we focus on products with a user account.

A word on honesty first: we sell Astro templates, and this site itself runs on Astro, so we have an interest. Where a statement is our own judgment rather than a fact from a source, we mark it “our assessment”.

Current as of November 14, 2026. The latest versions are Next.js 16.4.6 and Astro 7.4.12. The speed figures are from HTTP Archive data for October 2026. Versions and prices change often, so check the date.

In short

  • Astro suits sites that mostly show content: landing pages, blogs, documentation, catalogs.
  • Next.js suits products with a user account, where people click a lot and work with data.
  • For a startup, both are often used together (our assessment): Astro for the main site and Next.js for the app on a separate subdomain.
  • Speed in real-user data: in October 2026, about 72% of Astro sites and about 37% of Next.js sites passed Google’s Core Web Vitals on mobile.[5] That is a correlation, not proof: the two are used for different kinds of sites.

What these technologies are

Next.js and Astro are frameworks: sets of ready-made tools that developers use to build websites. A template buyer usually does not write code from scratch but picks a template built on one of these technologies. The choice affects site speed, hosting cost, and how easy it is to add a user account later.

  • Next.js is made by Vercel and built on React, the most popular library for building interfaces. In the Stack Overflow Developer Survey 2025, 20.8% of respondents said they had done extensive development work with Next.js in the past year.[1]
  • Astro has belonged to Cloudflare since January 2026. The Astro team announced that Astro stays open source and MIT-licensed, that its staff will continue to work on it full time, and that it remains a platform-agnostic framework.[2] In the same survey, 4.5% of respondents named Astro.[1]

Both projects are open source, and both can be used for free.

The main difference: a page or an application

Imagine two ways of sending a document. Astro sends a ready printed page: you can read it right away, and nothing else is needed. Next.js sends the page together with a small “program” that brings it to life in the browser. The page becomes interactive, but the browser has to download and run that program.

  • Astro by default sends ready HTML and adds no JavaScript. Interactive pieces (a form, a calculator, a slider) are separated out as “islands” and load code only for themselves.[3]
  • Next.js builds the site as a React application. Server Components are prepared on the server, and interactive parts are “hydrated” in the browser with JavaScript.[4] Newer versions can prepare the static parts of a page in advance, but the baseline amount of code in the browser stays larger (our assessment).

Almost all other differences follow from this.

Speed: what real-user data shows

Google measures three indicators of real visits, the Core Web Vitals: loading speed, responsiveness and layout stability. HTTP Archive combines this data with the technologies it detects on each site. We calculated the share of sites that pass all three indicators on mobile:[5]

Month (2026) Astro Next.js
July 69.8% 33.9%
August 71.0% 35.1%
September 71.1% 35.7%
October 72.2% (38,350 of 53,101 sites) 37.2% (154,449 of 414,664 sites)

What is important to know about these numbers:

  • This is a correlation, not proof. Astro is more often used for simple content sites, while Next.js is also used for heavy online stores and applications (our assessment).
  • A well-configured Next.js site can also pass the check. Astro makes this easier by default, because it sends less code (our assessment).
  • The data describes public websites. It says nothing about the speed of an app’s screens behind a login (our assessment).

For the main site, where visitors arrive from search and ads, this difference matters. For the app itself, other things usually matter more: how fast the data loads and how the interface responds (our assessment).

Content and SEO

Astro is built around content. Its content collections store articles, products and documentation pages as files or load them from a CMS, and Astro checks that the required fields are filled in.[6] There are ready-made solutions for the sitemap and RSS.[7] Astro’s own documentation and Cloudflare’s developer documentation are built on it, and Astro 7 (June 2026) made builds 15–61% faster in the Astro team’s benchmarks.[8]

Next.js also works with blogs and a CMS. It can update pages on a schedule without a full rebuild and generate images for social networks.[9] It has no built-in layer for storing content like Astro’s collections; one is connected separately (our assessment).

For SEO, both frameworks provide the necessary tools. The difference is that Astro puts less code on the page, which helps the speed indicators.

A site with a user account (SaaS)

Here the picture changes. A product needs sign-in and registration, payments, user roles, a dashboard, work with a database, and often several customers (“tenants”) inside one system.

Next.js is the most mature option for such a product (our assessment):

  • Ready-made SaaS starters. Popular paid starters come in Next.js versions: ShipFast is built on Next.js, Makerkit offers Next.js and TanStack Start, and Supastarter offers Next.js, Nuxt and TanStack Start. They include payments: Stripe in all three, and Lemon Squeezy or Polar as options in some.[10]
  • AI interface generators. Vercel’s v0 generates code with Next.js, React, TypeScript, Tailwind CSS and shadcn/ui.[11]
  • The React ecosystem. Libraries for sign-in, payments and interfaces are mostly written for React first (our assessment).

Astro can also work with sign-in, forms and a database. It has built-in Actions for forms and server calls and Sessions for storing user data between requests, and its documentation has guides for Better Auth, Clerk and Supabase.[12] This is enough for a small account: a profile, settings, a few pages (our assessment).

The boundary lies where the account gets a complex interface: for example, a dashboard with several panels, real-time data updates, and state that persists throughout the session. In Astro this usually turns into one big React component, that is, effectively a separate application inside the site. Then Astro’s advantage (almost no code on the page) disappears (our assessment).

For databases and payments there is no difference: Drizzle, Prisma, Stripe and other services work with both (our assessment). There are simply more ready-made templates in the Next.js ecosystem.

Hosting and cost

  • An Astro site without a server part is a set of files. It can be hosted almost for free on any static hosting. For pages built on request there are official adapters for Cloudflare, Netlify, Vercel and a regular Node server.[13]
  • Next.js runs with all features on any Node.js server or in a Docker container.[14] Since version 16.2 (March 2026) it has a stable adapter API for other platforms.[15] As of November 2026, the verified adapters are Vercel and Bun; Cloudflare and Netlify are working on verified adapters and, meanwhile, offer their own integrations.[14]

Vercel’s Pro plan costs $20 per month for a developer seat and includes $20 of usage credit; beyond that, you pay for actual usage.[16] This credit-based model has been in place since September 2025.[16] Spend Management sets a default on-demand budget of $200 for new teams, sends alerts as you approach it, and can pause all projects when the limit is reached.[16]

Our advice: if your app runs on a usage-based plan, set the budget and alerts on day one. The bill grows with traffic, not with the calendar (our assessment).

Security and updates

The best-known recent vulnerability is React2Shell (CVE-2025-55182), published on December 3, 2025, with a CVSS score of 10.0: an unauthenticated attacker could run code on the server through React Server Functions, and Next.js was among the affected frameworks.[17]

In 2026 the Next.js blog lists six security releases: scheduled ones on July 20, August 25, September 30 and November 3, and out-of-band updates on September 22 and October 14 for critical issues in upstream dependencies.[18] Security fixes are published for Next.js 16 and, until January 31, 2027, for Next.js 15; version 14 and older are not supported.[19]

Astro is not free of vulnerabilities either. GitHub’s advisory database lists, for advisories published in 2026:[20]

Package Critical High Medium Low Total
next 5 15 20 4 44
astro 1 3 8 5 17

Astro’s critical advisory (September 8, 2026) concerns image optimization: a flaw in the libheif library used by the default Sharp image service could lead to remote code execution when Astro processes an untrusted AVIF image. It was fixed in Astro 7.2.8.[20]

What this means in practice (our assessment):

  • A Next.js application has a larger server part, and therefore a larger attack surface. Update on the day fixes are released.
  • A static Astro site has little server part, so there is less to attack. Update it anyway, especially if it processes images from outside.
  • When buying a template, check the framework version. Old versions do not receive fixes.

These counts are not a ranking: projects with more users and a larger server part get more reports, and projects describe their problems in different detail.

Comparison in a table

Astro 7 Next.js 16
Principle A ready page plus “islands” of interactivity[3] A React application with Server Components[4]
JavaScript on the page by default None until you add an island[3] React for navigation and interactive parts[4]
Good Core Web Vitals on mobile, October 2026 72.2% of sites[5] 37.2% of sites[5]
Content and blog Built-in content collections[6] Via a CMS and additional libraries
User account Light: profile, forms, settings Any complexity: dashboards, real-time, roles
Ready-made SaaS starters Fewer (our assessment) ShipFast, Makerkit, Supastarter[10]
Interface libraries React, Vue, Svelte, Solid and others in one project[21] React
Owner Cloudflare[2] Vercel
Hosting Any; a static site is almost free[13] Any Node.js server or Docker; verified adapters: Vercel, Bun[14]
Security advisories in 2026 17, one critical[20] 44, five critical[20]
npm downloads, November 7–13, 2026 about 11.7 million[22] about 92.9 million[22]
Satisfaction (State of JS 2025) First among meta-frameworks[23] Losing satisfaction[23]

What to choose

A marketing site

A landing page, blog, documentation, catalog or portfolio.

  • Astro is a fit. Less code, better speed by default, cheaper hosting, a smaller server part to keep updated (our assessment).
  • Next.js is a fit if the marketing pages are closely tied to the product: a shared design with the app, personalization by account, or a team that already works in React (our assessment).

A SaaS product

Sign-in, payments, a dashboard, teams and roles.

  • Next.js is a fit. Ready-made starters, a mature ecosystem, more specialists. You need to follow versions and update them.
  • Astro is a fit for a small account with a few pages. If the account grows into a complex application, it will have to be moved out separately (our assessment).

Both at once

A common setup (our assessment): the main site example.com on Astro (marketing, blog, documentation) and the app app.example.com on Next.js, with shared colors and fonts kept in one place. The advantage is that each part uses the technology that suits it. The drawback is two projects, two deployments and two sets of updates.

One Next.js project for everything is more convenient for a small team that wants a single codebase.

What to consider when choosing a template

  • An Astro template usually means a fast marketing site with good speed indicators. Ready-made sign-in and payments are usually not part of such templates (our assessment).
  • A Next.js template (a SaaS starter) usually includes sign-in, payments and pricing plans.[10] In return, you need to follow security updates.
  • Look at the framework version in the template and at the date of its last update.
  • Moving from one framework to another is possible, but it is a separate project, not a setting (our assessment).

If you are building the marketing side of a SaaS on Astro, look at our Astro templates for SaaS or the whole catalog. How to adapt a template with an AI assistant is in our guide to customizing an Astro template with Claude Code.

Read next:

Frequently asked questions

Can I build a SaaS on Astro alone?

For a small account, yes: Astro has Actions and Sessions, and its documentation has guides for Better Auth, Clerk and Supabase.[12] If the account grows into a complex dashboard with real-time data, Next.js is usually the better fit (our assessment).

Is Next.js slower than Astro?

In real-user data, a larger share of Astro sites pass Core Web Vitals on mobile: 72.2% against 37.2% in October 2026.[5] That does not mean every Next.js site is slow: the two are used for different kinds of sites, and a well-configured Next.js site can pass too (our assessment).

Can I host Next.js outside Vercel?

Yes. Next.js runs with all features on any Node.js server or in Docker.[14] For other platforms there is an adapter API; Cloudflare and Netlify are working on verified adapters and offer their own integrations in the meantime.[14]

Does Cloudflare owning Astro tie Astro to Cloudflare?

The Astro team says Astro stays MIT-licensed and platform-agnostic.[2] Astro still has official adapters for Netlify, Vercel and a Node server.[13] How the ownership affects the project in the long run is hard to assess for now.

What remains uncertain

What we could not check.

  • The speed figures are a correlation. We calculated them from HTTP Archive’s open data and did not look at how each site is configured.
  • The advisory counts depend on reporting. Projects publish their vulnerabilities in different detail, so the numbers are not a measure of code quality.
  • Stories about large Vercel bills are not included. Many of them are published by Vercel’s competitors, and we could not check them.
  • The effect of Cloudflare’s ownership on Astro is hard to assess for now. So far it shows up as closer integration with Cloudflare.
  • SaaS starters and prices change often. We checked the vendors’ pages on November 14, 2026.

Sources

Pages checked on November 14, 2026.

  1. Stack Overflow, Developer Survey 2025: Technology (web frameworks and technologies, all respondents)
  2. Astro, “Astro is joining Cloudflare” (January 16, 2026)
  3. Astro Docs, Islands architecture
  4. Next.js Docs, Server and Client Components
  5. HTTP Archive, Core Web Vitals Technology Report: public API data for Astro and Next.js (all regions and ranks, July–October 2026; shares calculated by us) and API documentation
  6. Astro Docs, Content collections
  7. Astro Docs, @astrojs/sitemap and Add an RSS feed
  8. Astro, “Astro 7” (June 22, 2026; build benchmarks include docs.astro.build and developers.cloudflare.com)
  9. Next.js Docs, Incremental Static Regeneration and opengraph-image
  10. Vendor sites: ShipFast, Makerkit, supastarter
  11. v0, FAQs
  12. Astro Docs, Actions, Sessions, Authentication and Supabase & Astro
  13. Astro Docs, On-demand rendering (official adapters)
  14. Next.js Docs, Deploying (updated August 6, 2026) and Deploying to platforms (updated March 30, 2026)
  15. Next.js, “Next.js Across Platforms: Adapters, OpenNext, and Our Commitments” (March 25, 2026)
  16. Vercel, pricing, “Included Pro usage is now credit-based” (September 9, 2025) and Spend Management
  17. React, “Critical Security Vulnerability in React Server Components” (December 3, 2025)
  18. Next.js blog: July, August, September 22, September 30, October 14 and November 2026 security releases
  19. Next.js, Support policy
  20. GitHub Advisory Database, npm advisories published in 2026 for next and astro (counted on November 14, 2026), and GHSA-26w7-cxv4-gfx2 (September 8, 2026)
  21. Astro Docs, Front-end frameworks
  22. npm download counts API: next and astro (November 7–13, 2026; counts include CI servers and bots)
  23. State of JavaScript 2025, Meta-frameworks
All templates →

From the blog

Keep reading

All articles

Ready when you are

Launch your next site this week.

Pick a template, pay once, download instantly. Every page is already designed. You bring the words.