Skip to content

Next.js158 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

riff.ai/
Riff landing page design — Other
RiffOther
pandadoc.com/
Pandadoc landing page design — HR
apollo.io/
Apollo landing page design — Sales & Support
ApolloSales & Support
incident.io/
Incident landing page design — Sales & Support
IncidentSales & Support
convex.dev/
Convex landing page design — Infrastructure
ConvexInfrastructure
hedra.com/
Hedra landing page design — Design
HedraDesign
manicule.dev/
Manicule landing page design — Other
honen.com/
Honen landing page design — Sales & Support
HonenSales & Support
promptwatch.com/
Promptwatch landing page design — Marketing
PromptwatchMarketing
tembo.io/
Tembo landing page design — Developer Tools
TemboDeveloper Tools
kombai.com/
Kombai landing page design — Developer Tools
KombaiDeveloper Tools
kleepay.ai/
Kleepay landing page design — Finance
KleepayFinance
usenotra.com/
Usenotra landing page design — Marketing
UsenotraMarketing
usepropane.ai/
Usepropane landing page design — Analytics
UsepropaneAnalytics
xata.io/
Xata landing page design — Developer Tools
XataDeveloper Tools
stacker.ai/
Stacker landing page design — AI
beside.com/
Beside landing page design — Sales & Support
BesideSales & Support
cntrl.site/
Cntrl landing page design — Design
CntrlDesign
reflexai.com/
Reflexai landing page design — Sales & Support
ReflexaiSales & Support
felix.so/
Felix landing page design — Infrastructure
FelixInfrastructure
readme.com/
Readme landing page design — Marketing
ReadmeMarketing
tidio.com/
Tidio landing page design — Sales & Support
TidioSales & Support
tennr.com/
Tennr landing page design — Other
TennrOther
firecrawl.dev/
Firecrawl landing page design — Developer Tools
FirecrawlDeveloper Tools
refold.ai/
Refold landing page design — AI
antimetal.com/
Antimetal landing page design — Developer Tools
AntimetalDeveloper Tools
creem.io/
Creem landing page design — Finance
CreemFinance
autostep.ai/
Autostep landing page design — Productivity
AutostepProductivity
tryreplicas.com/
Tryreplicas landing page design — Developer Tools
TryreplicasDeveloper Tools
tester.army/
Tester landing page design — Developer Tools
TesterDeveloper Tools
graphite.com/
Graphite landing page design — Developer Tools
GraphiteDeveloper Tools
polar.sh/
Polar landing page design — Finance
PolarFinance
usecardboard.com/
Usecardboard landing page design — Design
customer.io/
Customer landing page design — Analytics
CustomerAnalytics
mailwarm.com/
Mailwarm landing page design — Marketing
MailwarmMarketing
ellipsus.com/
Ellipsus landing page design — Productivity
EllipsusProductivity

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

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.