Next.js vs Remix (React Router) vs Astro: Which Framework Fits a Business Site?

For a marketing or content-heavy business site (services, blog, landing pages, docs), choose Astro: it ships static HTML with almost no JavaScript, so it is fast and cheap to host. For a site that is also a product (logins, dashboards, personalised pages, ecommerce logic), choose Next.js. Choose React Router v7, the successor to Remix, when your team wants web-standard forms and data loading, and prefers to avoid React Server Components complexity.

All three are open source, React-friendly and SEO-capable. The right pick depends on how much of your site is content versus application.

Key takeaways

• "Remix" now means React Router v7. The Remix team merged Remix v2 into React Router v7 "framework mode" and recommends it for new projects; Remix 3 is a separate, React-free effort.
• Astro is content-first. Zero JavaScript by default, islands for interactivity, first-class Markdown/MDX and content collections.
• Next.js is the broadest. Static, server-rendered and streaming pages, server actions and a massive ecosystem, with more concepts to learn.
• Hiring is easiest for Next.js. It is the most common React framework in job posts and agency portfolios, so handover risk is lowest.
• Performance is a discipline, not a framework feature. Any of the three can produce a slow site if you load heavy third-party scripts.

The three frameworks in one table

Astro: the content-site specialist

Astro's islands architecture renders each page to HTML at build time and hydrates only the components you mark as interactive. A services page with a hero, testimonials and a contact form might ship a few kilobytes of JavaScript for the form and nothing else. That is why Astro sites tend to pass Core Web Vitals without effort.

Why business sites like it:

• Content collections give you typed Markdown and MDX, so a non-developer can add a blog post through Git or a CMS without breaking layouts.
• You can mix component libraries. If your product team has React components, reuse them as islands.
• Static output costs almost nothing to host and survives traffic spikes.

Where it is weaker: complex authenticated areas, heavy client-side state and app-like navigation. Astro can do server rendering and API endpoints, but if half your site is a logged-in dashboard, you will be working against its grain.

Ownership note: The Astro Technology Company joined Cloudflare in January 2026. The team's announcement says Astro stays MIT-licensed, keeps supporting non-Cloudflare deployment targets, and keeps its open governance.

Next.js: the all-rounder for product companies

Next.js covers the widest range: fully static pages, server-rendered pages, Incremental Static Regeneration for large catalogues, React Server Components, server actions for forms, middleware for redirects and auth, and an image component that handles responsive images. It is on the 16.x release line as of October 2026.

Why business sites choose it:

• One codebase for the marketing site and the app, sharing design system and auth.
• A huge ecosystem: every headless CMS, commerce platform and auth vendor ships Next.js examples.
• Hiring and agency handover are straightforward.

Costs to watch:

• Concepts: server versus client components, caching layers and revalidation can confuse teams new to it.
• Bundle weight creeps up if every component becomes a client component.
• Hosting is smoothest on Vercel. Self-hosting works, but some features need extra configuration. See Vercel vs Netlify vs Cloudflare Pages for hosting trade-offs.
• Security releases are regular, so budget time each quarter to upgrade.

React Router v7 (formerly Remix): web standards first

Remix popularised a clean model: each route has a loader for reading data and an action for handling form submissions, built on the web's own Request, Response and FormData. In late 2024 that model moved into React Router v7 framework mode. The Remix team describes this as a stable, long-term platform for anyone who built on Remix v1 or v2.

Why choose it:

• Forms work without JavaScript and then progressively enhance, which is excellent for checkout, booking and lead forms.
• Fewer framework-specific concepts than Next.js; if you know HTTP, you know most of it.
• Shopify's Hydrogen documentation offers storefront templates built with React Router (alongside Next.js), so it is a natural fit for headless Shopify builds.

Watch-outs: smaller ecosystem than Next.js, and the Remix brand change confuses search results and hiring. When you post a job, ask for "React Router v7 framework mode (Remix)" experience.

From experience: On Shopify Plus and headless commerce work, the loader/action pattern makes cart and checkout-adjacent forms far easier to reason about than client-side state. For pure marketing pages around a store, a static-first approach is usually faster to build and to load.

Total cost of ownership over three years

The framework is free; the people and platform around it are not. When you compare options, price these four lines rather than licence fees:

• Build time. A content site in Astro usually needs fewer moving parts than the same site in Next.js, so the first version ships sooner. A product with logins and dashboards flips that, because Next.js gives you more built-in pieces.
• Hosting. Static Astro output can sit on a free or near-free static host. Server-rendered Next.js or React Router apps need functions or a Node server, which bills by usage.
• Maintenance. Budget a few days each quarter for framework upgrades and security patches. Next.js publishes security releases regularly; skipping them is how small sites get compromised.
• Handover. If an agency or freelancer builds the site, ask who will maintain it in year two. Choosing the framework your future team already knows is often the cheapest decision.

How to choose: a practical process

1. Map your pages. Count marketing/content pages versus logged-in or highly dynamic pages.
2. If over 80% is content, start with Astro. Add React islands for calculators, booking widgets or search.
3. If you have a meaningful logged-in product, choose Next.js so marketing and app share one codebase, or keep marketing on Astro and the app on Next.js under a subdomain.
4. If the app is form-heavy and your team values web fundamentals, consider React Router v7.
5. Pick the CMS next. Editors' needs often decide more than developers' preferences; see our headless CMS comparison.
6. Pick hosting last, once you know whether you need server rendering at all.

When you should not use any of them

If your team has no developers and edits the site weekly, a visual builder may serve you better. Compare Webflow vs WordPress vs Framer before committing to a code framework you cannot maintain.

Common mistakes on business sites

• Building a five-page brochure site as a full single-page app, then fighting slow first loads and SEO.
• Adding a chat widget, two analytics tools and a heatmap script that together outweigh the whole framework.
• Letting the agency host the site on its own account, so the business does not control its domain, code or deployments.
• Skipping a content model, so every new page needs a developer.

SEO and performance checklist for any framework

• [ ] Every indexable page returns full HTML on first response (check "view source", not dev tools)
• [ ] Unique title tag, meta description and canonical URL per page
• [ ] XML sitemap generated at build and submitted in Search Console
• [ ] Images sized, compressed and lazy-loaded below the fold
• [ ] Third-party scripts (chat, analytics, tag managers) audited and deferred
• [ ] Structured data (Organization, LocalBusiness, Article, FAQ where valid) added in JSON-LD
• [ ] 301 redirects mapped before migrating from an old site
• [ ] Core Web Vitals checked on real devices on a mobile connection
• [ ] Preview or staging environments blocked from indexing
• [ ] Framework upgrade and security patch routine scheduled

Next steps

• List your pages and classify each as content or application before discussing frameworks.
• Build the same landing page in Astro and Next.js in an afternoon and compare JavaScript shipped and Lighthouse scores.
• Decide who edits content day to day, then shortlist a CMS that suits them.
• Plan hosting with our hosting comparison.
• If you want help choosing and setting up a stack that ranks well, see our AI SEO consulting service.

Sources

• Remix blog, "Merging Remix and React Router": https://remix.run/blog/merging-remix-and-react-router
• Remix blog, "Wake up, Remix!": https://remix.run/blog/wake-up-remix
• Astro blog, "The Astro Technology Company joins Cloudflare": https://astro.build/blog/joining-cloudflare/
• Astro docs, Islands architecture: https://docs.astro.build/en/concepts/islands/
• Next.js blog (release line and security updates): https://nextjs.org/blog
• Cloudflare Workers Next.js guide: https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/
• Shopify Hydrogen docs: https://shopify.dev/docs/storefronts/headless/hydrogen

Keep reading