Skip to content
BestSaaSWebDesigns

Next.js — 158 sites

158 SaaS websites built with Next.js

Next.js powers a huge share of modern SaaS marketing sites. These examples show how teams use it to ship fast, polished landing pages — from content-heavy marketing to app-like interactivity.

SaaS websites built with Next.js gallery

render.com/
Render landing page design — Infrastructure
RenderInfrastructure
retool.com/
Retool landing page design — Developer Tools
RetoolDeveloper Tools
loom.com/
Loom landing page design — Productivity
LoomProductivity
figma.com/
Figma landing page design — Design
FigmaDesign
notion.so/
Notion landing page design — Productivity
NotionProductivity
vercel.com/
Vercel landing page design — Infrastructure
VercelInfrastructure
stripe.com/
Stripe landing page design — Finance
StripeFinance
elevenlabs.io/
Elevenlabs landing page design — AI
ElevenlabsAI
raycast.com/
Raycast landing page design — Productivity
RaycastProductivity
granola.ai/
Granola landing page design — Productivity
GranolaProductivity
assurestor.com/
Assurestor landing page design — Infrastructure
AssurestorInfrastructure
neon.com/
Neon landing page design — Infrastructure
NeonInfrastructure
playerzero.ai/
PlayerZero landing page design — Developer Tools
PlayerZeroDeveloper Tools
eigenpal.com/
Eigenpal landing page design — AI
EigenpalAI
kiro.dev/
Kiro landing page design — Developer Tools
KiroDeveloper Tools
duckie.ai/
Duckie landing page design — Sales & Support
DuckieSales & Support
cline.bot/
Cline landing page design — Developer Tools
ClineDeveloper Tools
rollups.com/
Rollups landing page design — Other
RollupsOther
mastra.ai/
Mastra landing page design — Developer Tools
MastraDeveloper Tools
chroniclehq.com/
Chronicle landing page design — Productivity
ChronicleProductivity
clutch.security/
Clutch Security landing page design — Security
Clutch SecuritySecurity
fin.ai/
Fin landing page design — Sales & Support
FinSales & Support
factory.ai/
Factory landing page design — Developer Tools
FactoryDeveloper Tools
duckie.ai/
Duckie landing page design — Sales & Support
DuckieSales & Support
0cred.com/
0cred landing page design — Other
0credOther
morphllm.com/
Morphllm landing page design — Developer Tools
MorphllmDeveloper Tools
browserbase.com/
Browserbase landing page design — Infrastructure
BrowserbaseInfrastructure
magicpath.ai/
Magicpath landing page design — Design
MagicpathDesign
pencil.dev/
Pencil landing page design — Design
PencilDesign
zed.dev/
Zed landing page design — Developer Tools
ZedDeveloper Tools
onlook.com/
Onlook landing page design — Design
OnlookDesign
wonder.design/
Wonder landing page design — Design
WonderDesign
noon.design/
Noon landing page design — Design
NoonDesign
lunagraph.com/
Lunagraph landing page design — Design
LunagraphDesign
buildwithglue.com/
Buildwithglue landing page design — Design
BuildwithglueDesign
paper.design/
Paper landing page design — Design
PaperDesign

About Next.js

Next.js's appeal for a marketing site specifically (as opposed to the product app behind it) comes down to rendering flexibility — a team can statically generate the mostly-unchanging homepage and pricing page for near-instant load times, while server-rendering or incrementally revalidating pages that change more often (a blog, a directory like this one, or personalized content), all inside one framework rather than stitching together a separate static site generator and app. It's also the default choice for teams already building their product in React, since the marketing site and the app can share components, design tokens and even authentication state without a second toolchain. The tradeoff worth knowing: that same flexibility means a Next.js marketing site's performance is only as good as the rendering strategy chosen for each page — a site that server-renders everything on every request when it could have cached most of it will be slower than a simpler static site, so seeing 'built with Next.js' isn't itself a performance guarantee.

What makes a great one

  • Fast, near-instant page loads even on content-heavy pages
  • A visual system shared cleanly between marketing site and product app
  • Server-rendered or statically generated metadata for real SEO titles/descriptions
  • Smooth client-side navigation without a full page reload

Related

React sitesTailwind CSS sitesDeveloper tool designs

Frequently asked

Why do SaaS companies pick Next.js for their marketing site specifically?
Mainly to share code and design system with a React-based product app, and to mix static generation (fast marketing pages) with server rendering or ISR (dynamic content like a blog or directory) inside one framework.
Is a Next.js site automatically fast?
No — Next.js makes fast rendering strategies available, but a page that's server-rendered on every request instead of statically generated or cached can still be slow. The framework choice matters less than how each page actually uses it.
Does using Next.js help SEO?
Indirectly, by making it easy to do the things that do help SEO — fast static pages, server-rendered metadata, image optimization — but none of that is automatic just from choosing the framework; it still has to be configured deliberately.