The basics
What Next.js is, and what it means for your website
Next.js is an open-source React framework, the structural foundation that determines how your website is built, how it handles data, and what it can do. Think of it as the full-stack engine behind your digital presence.
What makes Next.js different from content-first frameworks like Astro: it was designed for sites that are write-heavy, not just read-heavy. Marketing pages, client portals, e-commerce storefronts, dashboards, and API integrations. All in one codebase, all managed by one team.
Next.js's core innovation is hybrid rendering: every page can be static, server-rendered, or dynamically generated depending on what it needs to do. A blog post gets pre-built for instant delivery. A dashboard renders fresh data on every visit. A product page regenerates in the background while serving cached content. One framework handles all three patterns.
This isn't a niche tool. Next.js is the most widely adopted modern React framework, used in production by Nike, Notion, Hulu, TikTok, the Washington Post, and thousands of mid-market companies. It was built for exactly the kind of ambitious, multi-capability website that outgrows simpler platforms.
Lynton builds its own client portal on Next.js. We use both Next.js and Astro, and recommend each where it fits.
Why it matters
Four business outcomes Next.js directly affects
These aren't theoretical advantages. They're measurable differences that show up in your capabilities, your hiring pipeline, and your ability to ship without hitting a ceiling.
One framework, no ceiling
Build anything without switching tools
Marketing pages, customer portals, e-commerce, dashboards, and API routes. All in one codebase. No "outgrowing" the framework. When your marketing site needs a client login area or a self-service portal, you don't need a second framework or a separate app. Next.js scales from a landing page to a full platform.
Better SEO with dynamic content
Server rendering meets search performance
Next.js can server-render personalized or dynamic pages so search engines see the full content, not a blank shell waiting for JavaScript to load. Dynamic content that also ranks well is Next.js's sweet spot. Combined with full control over meta tags, structured data, and URL routing, your SEO team gets the foundation they need.
Native AI integration
Built on the same language as every AI API
Next.js runs on JavaScript/TypeScript, the same language that powers every major AI API (OpenAI, Anthropic, Google). Vercel's AI SDK was built specifically for Next.js. AI features like chatbots, content generation, and personalization engines are native to the ecosystem, not bolted on through a plugin or marketplace app.
The largest React developer ecosystem
Hiring and maintenance are easier
Next.js is the most widely adopted React framework. That means more available developers, more battle-tested patterns, more libraries, and lower long-term maintenance risk. When you need to scale your team or hand off your site to a new agency, the talent pool is the deepest in modern web development.
Under the hood
How Next.js achieves this, explained simply
You don't need to understand the engineering to make the decision. But if your technical team asks "why Next.js specifically?", here's the 60-second version.
Hybrid rendering: static, server, or dynamic, per page
Unlike frameworks that force a single approach, Next.js lets each page choose its own rendering strategy. A blog post can be pre-built at deploy time for instant delivery. A dashboard can render fresh data on every visit. A product page can regenerate in the background while serving cached content. You get the right approach for each page without compromising on the others.
Server Components: less JavaScript, smarter architecture
React Server Components run on the server and send finished HTML to the browser, similar to how static-first frameworks work. Interactive elements get JavaScript only where needed. The result: pages that load fast by default, with rich interactivity exactly where it matters. This is React's answer to the "ship less JavaScript" problem.
Full-stack in one codebase
API routes, middleware, authentication, and database queries all live alongside your pages. No separate backend service. No third-party middleware layer. When your marketing site needs a contact form, a gated resource, a payment flow, or a client portal, the infrastructure is already there. One deploy, one team, one codebase.
Content and presentation are separated
Like Astro, Next.js pairs naturally with headless CMS platforms (Sanity, Contentful, Storyblok, TinaCMS). Your content team edits in a visual interface. Next.js handles how that content looks and what it can do on the website. If you ever want to redesign or switch frameworks, your content stays untouched.
The analogy for non-technical stakeholders
If Astro is a restaurant that prepares meals in advance for instant service, Next.js is a restaurant with both a prep kitchen and a live cooking station. Some dishes come out instantly (static pages). Others are made fresh to order (dynamic pages). The kitchen handles both, and the menu isn't limited by either approach.
The comparison
Next.js vs. the platforms you're comparing it to
An honest comparison. Next.js isn't the right choice for everything, but for sites that need dynamic capabilities alongside their marketing pages, the differences are significant.
| Next.js | Astro | HubSpot CMS | WordPress | |
|---|---|---|---|---|
| Best suited for | Full-stack websites: marketing + portals, e-commerce, personalization, authenticated areas | Read-heavy sites: marketing, blogs, directories, resource centers, AI-enhanced content | Teams already all-in on the HubSpot ecosystem | Simple sites with small budgets and minimal AI ambitions |
| Default page speed | Fast with Server Components and static generation. Requires intentional optimization for pure content pages. | Near-instant. 95–100 Lighthouse scores typical. Zero JS shipped by default. | Moderate. Platform overhead affects Core Web Vitals. | Varies widely. Plugin bloat often degrades performance. |
| SEO control | Full control. Server rendering means dynamic content is fully crawlable by search engines. | Full control over HTML, meta tags, structured data, URL routing, sitemap generation. | Limited to what the platform exposes. Some constraints on structure. | Good with plugins (Yoast, Rank Math). Plugin dependency. |
| Hosting cost | Moderate. SSR requires server compute. More than static hosting, far less than enterprise SaaS. | Very low. Static hosting from $5–20/month for most marketing sites. | Bundled into SaaS pricing. Starts at $360/year, scales with tier. | Moderate. Managed WP hosting $30–300+/month depending on quality. |
| AI integration | Native. Vercel AI SDK built specifically for Next.js. JS/TS ecosystem connects to any AI API. | Native. JS/TS ecosystem connects directly to any AI API. | Limited to HubSpot Breeze and approved integrations. | Plugin-based. Security and performance trade-offs. |
| Content portability | High. Headless CMS architecture. Framework is replaceable. | High. Content in headless CMS, framework is replaceable. | Low. Content and templates tightly coupled to HubSpot. | Moderate. Content exportable but theme-dependent. |
| Developer talent pool | Largest modern framework community. Hiring is easiest here. | Growing rapidly. Built on standard JS/TS — any web developer can learn it. | Small. HubL is proprietary to HubSpot. | Very large. Quality and modernity varies. |
| Dynamic capabilities | Full-stack: auth, API routes, middleware, database access, real-time features — all built in. | SSR mode, server endpoints, and React islands. Handles AI chat, search, and database reads — but not built for complex write workflows. | Limited to platform features. Custom logic requires workarounds. | Plugin-dependent. Each plugin adds complexity and security surface. |
When Next.js isn't the right choice
Read-heavy sites without complex write workflows. Astro handles AI chat, semantic search, database-driven directories, and interactive React components. It's not static-only. But if your site doesn't need authentication, multi-step forms, or transactional logic, Astro is lighter and faster. Don't use a full-stack framework when a content-first framework does the job better.
When Next.js is the clear winner
Sites where users write data back, not just read it. Client portals. E-commerce with cart and checkout. Authenticated dashboards. Multi-step workflows. Real-time collaboration. Anywhere the website is a two-way application, not a one-way publishing channel. Next.js is built for that job.
In production
Companies already running on Next.js
Next.js isn't a startup experiment. It's the most widely deployed modern React framework, running at enterprise scale across every industry.
Nike
Global e-commerce and brand marketing. Performance-critical at massive scale with complex product logic.
Notion
Web application + marketing site. The hybrid content/app pattern that Next.js was designed for.
Hulu
Streaming platform with content marketing. Dynamic personalization at scale.
Washington Post
Editorial content at scale. Server-rendered dynamic pages with real-time publishing.
TikTok
Consumer web application. High-traffic, dynamic content with complex interactivity.
Lynton
Our client portal. Migration management, AI analysis, and dynamic workflows. All on Next.js.
We build on both
Lynton uses Astro for our marketing site (content-first) and Next.js for our client portal (migration tools, AI analysis, dynamic workflows). We're not framework partisans. We recommend the right tool for the job, not the one we have a partnership with. When your project needs full-stack capabilities, Next.js is what we reach for.
The decision
How to know if Next.js is the right framework for your project
The framework recommendation in your proposal wasn't arbitrary. Here's the decision logic behind it. The same criteria we apply to every project.
Next.js is the right fit when:
- Your site needs authenticated areas, client portals, or user accounts
- You're building e-commerce with cart, checkout, or payment logic
- Personalization or dynamic content is a core requirement
- You need API routes, webhooks, or server-side integrations
- Your site will grow beyond marketing into application territory
- You want one framework that handles everything without a ceiling
Consider Astro instead when:
- Your site is read-heavy: blogs, directories, resource centers, landing pages
- Page speed and minimal JavaScript are your absolute top priorities
- You need interactivity (AI chat, search, filters) but not complex write workflows
- You want the lowest hosting costs with the best performance baseline
- Your dynamic needs are read-oriented (database queries, API fetches) not write-oriented (auth, CRUD, transactions)