Skip to main content

Trends, tech news, and tool comparisons.

Next.js vs Astro for a SaaS marketing site: a decision rule

· 6 min read
Dealpuffin
Proof points and live coupons for early adopters

Pick Astro if your marketing site is mostly content (landing page, pricing, blog, docs) and lives apart from your app. Pick Next.js if the marketing pages share components, auth state or server logic with your product, or if you already run the app in Next.js and want one codebase. Both can produce fast static pages, so the deciding factor is how much your marketing site has to do beyond showing content.

This comparison sticks to what the Astro and Next.js documentation says, read on 11 November 2026. I did not benchmark either framework, so I make no speed claims.

What each framework says it is for​

Astro's Why Astro page states that Astro was designed for building content-rich websites, aimed at sites where the content is the product, such as blogs, docs and storefronts, rather than logged-in applications. It lists server-first rendering, with client-side JavaScript added only where needed, and describes its "islands" architecture and zero JavaScript by default as features. It is UI-agnostic and supports React, Preact, Svelte, Vue, Solid and others.

Next.js is a full-stack React framework. Its deployment page lists four ways to ship it: a Node.js server, a Docker container, a static export, or an adapter for a platform. Node.js and Docker support all features. A static export supports a limited set.

Astro starts from content and adds interactivity where you ask for it. Next.js starts from an application and can also produce static pages.

Side by side​

QuestionAstroNext.js
Designed forContent-rich sites such as blogs, docs and storefrontsFull-stack React applications
Default client JavaScriptZero by default, added through islandsReact is part of the client model; static export still ships JavaScript for hydration
UI librariesReact, Preact, Svelte, Vue, Solid and moreReact
Static outputCore use caseAvailable through output: 'export'
Server features on static outputNot the main pathSeveral unsupported (see below)
Shares code with a Next.js appOnly via packages or copySame project or monorepo

The one claim in the table I should flag: Next.js docs say a static export generates an HTML file per route and "can avoid loading unnecessary JavaScript code on the client-side." They do not say it ships none. Compare the two on your own pages with a real build before relying on either description.

What you lose with a Next.js static export​

If you choose Next.js and export statically, the static export guide lists features that are not supported because they need a Node.js server or dynamic logic: dynamic routes without generateStaticParams(), route handlers that rely on the request, cookies, rewrites, redirects, headers, proxy, Incremental Static Regeneration, image optimisation with the default loader, Draft Mode, Server Actions and intercepting routes.

Some of those matter for marketing sites. If you rely on redirects for old URLs, you need to handle them at your web server or CDN. If you use next/image, you need a custom image loader. If you want a signup form that posts to a Server Action, you need a separate endpoint.

What you keep is also worth knowing. Server Components run at build time and render to static HTML, and Client Components work for interactive parts.

You avoid that list by running Next.js as a server or in a container, as covered in how to deploy Next.js on a single VM with Docker. The price is that you now run and patch a Node process for pages that rarely change.

A decision rule​

Answer these four questions in order and stop at the first yes.

  1. Does the marketing site need logged-in state, such as showing the user's name or plan in the header? Choose Next.js, and run it as a server.
  2. Do you want one repository and one set of React components for app and marketing? Choose Next.js.
  3. Is the site mostly written content, updated by a person or a content tool, with a handful of interactive widgets? Choose Astro.
  4. Is your team comfortable with a framework other than React? If not, choose Next.js. If yes, Astro's UI-agnostic design means you can still drop in a React component where you need one.

If none of these gives a clear answer, choose the one your team already knows. A fast site shipped this week beats a theoretically better one next month.

A worked example​

Take a founder with a product dashboard already built in Next.js and a marketing site of five pages: home, pricing, a changelog, a blog and a docs section.

The dashboard needs auth and server logic, so it stays on Next.js. The marketing pages are content. Under the rule above, question 1 is no, question 2 is a maybe, and question 3 is yes, so Astro fits well for the marketing site, hosted separately from the app at the root domain with the app on a subdomain.

Now change one fact: the pricing page must show the visitor's current plan and a personalised upgrade button. Question 1 becomes yes. Keep those pages in the Next.js app and skip the second framework.

Costs of running two frameworks​

Splitting marketing and app means two builds, two deploys and two places to update shared design tokens and copy. It also means analytics and consent have to work across both. That overhead is small for a one-person team if the marketing site rarely changes, and larger if three people edit both weekly. For measurement across the two, see PostHog vs Plausible vs GA4 for early-stage SaaS.

Who should pick what​

Choose Astro when content leads and your app lives elsewhere. Choose Next.js when marketing and product overlap, when you want one codebase, or when you need server features on your public pages. Choose a Next.js static export only if you can live with the unsupported list above.

Frequently asked questions​

Is Astro better than Next.js for SEO?​

Both can output crawlable HTML, so the differences come from your content, page speed and how well you handle redirects and metadata. Astro's content-first design makes the static path the default one.

Can I use React components in Astro?​

Yes. Astro's docs list React among the UI frameworks it supports, so you can render a React component inside an Astro page and hydrate it only where it needs to be interactive.

Does a Next.js static export work with a blog?​

Yes. Server Components run at build time and render static HTML, and dynamic routes work if you provide generateStaticParams(). You lose the features on the unsupported list, such as redirects and Incremental Static Regeneration.

Should I switch an existing site?​

Only if you have a concrete problem, such as maintenance cost or a feature you keep working around. Switching frameworks for a small site rarely pays back quickly.