What the website starter includes
The pages live in the (marketing) route group of the Next.js app, share one layout with the header and footer, and render at the root of your domain.
Landing page
/Hero, feature sections, and calls to action built from Server Components and Tailwind CSS 4.
Pricing page
/pricingRendered from the same billing configuration the checkout uses, so plans on the page match plans in Stripe or Lemon Squeezy.
Blog
/blogPost listing and post pages with categories and tags, fed by the CMS layer.
Documentation
/docsHierarchical docs with parent and child pages and ordering, for product help or a public API reference.
Changelog
/changelogRelease notes as a content collection, next to the blog and docs.
Contact form
/contactA contact page whose form sends email through the mailer you configure for the app.
FAQ
/faqA FAQ page you edit in code alongside the rest of the site.
Legal pages
/terms-of-serviceTerms of Service, Privacy Policy, and Cookie Policy pages in their own route group.
Content from files, WordPress, or your database
Blog posts, docs, and changelog entries go through one CMS interface. The default is Keystatic with local Markdoc files, so content is versioned in Git with your code and needs no configuration. Set CMS_CLIENT to wordpress to read from an existing WordPress site, or install the Supabase CMS plugin to keep content in Postgres.
Because pages call the interface, not the provider, switching CMS does not mean rewriting your data fetching. Sanity, Contentful, or Strapi need a custom client that implements the same interface; the docs walk through writing one.
Technical SEO that is already wired
- Page metadata through the Next.js Metadata API, with a title template and Open Graph defaults in the root layout.
- A sitemap route at
/sitemap.xmlthat adds blog posts and docs pages automatically, plus robots configuration. - A documented pattern for JSON-LD structured data on marketing pages.
- Locale-prefixed routes for translated marketing pages, through the kit's i18n setup.
Keyword research, writing, and links are still your job. The kit removes the setup, not the work.
Is this the right website starter for you?
Yes, if the site sells a product
The website is the front door to a SaaS. Sign-up, billing, team accounts, and the admin panel sit next to your pages from day one, in the Next.js SaaS starter kit.
No, if it is only a website
For a brochure site or a blog with no accounts, a plain Next.js template is lighter and cheaper.
Already have a site on Framer, Webflow, or WordPress? The kit documents how to keep an external marketing website and serve only the app from MakerKit. Details for the built-in pages are in the marketing pages docs and the SEO configuration guide.
A Next.js website starter that is also a working SaaS
This is not a standalone website template. The marketing site (landing page, pricing, FAQ, blog, docs, changelog, contact, and legal pages) lives in the same Next.js app as the signed-in product.Blog and docs content come from Keystatic, WordPress, or Supabase through one CMS interface. If you only need a brochure site with no accounts, a plain Next.js template is the lighter choice.
Authentication
Billing and Subscriptions
Customer Portal
Multi Tenancy
Super Admin
Shadcn UI and Tailwind CSS
Dark Theme
Blog
Documentation/Help Center
Mobile Friendly
Serverful/Serverless Stack
Strict code standards
E2E Testing with Playwright
Emails with React Email
Mailers
Plugins
You Own the Code
Documentation
SEO Basics
Swappable Providers
AI Agent Rules
MCP Server
Course
Realtime Notifications (Supabase)
Internationalization
Figma UI Kit
Support
Community
Guides
Continuous Updates
Maintained Full-Time
Since 2022
Rules and an MCP server for AI agents and IDEs: Claude Code, Codex, Gemini, and Cursor
Instruction files tell the agent where code goes and which patterns to reuse. The MCP server gives it structured access to the kit, so features land on the existing auth, tenancy, and billing instead of beside them.
A production-ready Next.js Website Starter, with the SaaS behind itThe setup, stack, and tooling are decided, so your first commit is a product feature.
AuthenticationPassword, magic link, passkey, and social sign-in, plus MFA, with the email flows that go with them.
Multi-TenancyPersonal and team accounts, invitations, and role-based access control, modeled in the database rather than bolted on in app code.
BillingSubscriptions with Stripe and other providers, including per-seat and metered billing, for personal and team accounts.
Admin PanelManage your users, organizations, and build your own internal tooling within the app.
Delightful UI, Built to ExtendScreens for every flow, built from the same Shadcn UI components you will use for your own features.
MarketingGet found by your target audience with blog, documentation, changelog, and more.
Monitoring and TestingComprehensive monitoring and testing tools to help you keep your SaaS running smoothly.
Support and CommunityAsk me and the MakerKit community on Discord about setup, kit-related issues, and how the codebase fits together.
The website is the small part
Marketing pages take a few hours. The product behind them, with accounts and payments, is the part a website template leaves to you. With AI coding tools, that is still 49-81 hours of senior developer time, including fixing the patterns AI got wrong.
Build once
Infrastructure every SaaS needs before its first feature
- Authentication (email, OAuth, MFA)6-10 hoursPre-built
- Stripe subscription billing5-8 hoursPre-built
- Teams, roles & invitations6-10 hoursPre-built
- Super admin dashboard4-6 hoursPre-built
- Transactional emails3-5 hoursPre-built
- Marketing pages2-4 hoursPre-built
- Blog & documentation3-5 hoursPre-built
- Project setup (monorepo, CI, TypeScript)2-3 hoursPre-built
- E2E tests (auth and billing flows)3-5 hoursPre-built
Maintain forever
Work that keeps coming after launch
- Refactoring AI-generated patterns15-25 hoursNot needed
- Next.js/React version upgradesEvery major releaseIncluded
- Security patches & fixesOngoing, unpredictableIncluded
- Dependency updatesOngoingIncluded
49-81 hours
With AI tools, including rework
Day 1
Start building your product immediately
$7,350-$12,150
In developer time and opportunity cost
Estimates for a senior developer building from scratch with Claude Code or Cursor at $150/hour, including 15-25 hours refactoring AI-generated patterns. Read the methodology
Get the website and the SaaS behind it
One-time purchase: lifetime license, continuous updates, unlimited projects of your own.
- Lifetime access to your stack of choice
- Build unlimited applications
- Continuous updates
- Access to the Discord community
- The best support in the SaaS Starter kits market, period.
- Community and Chat support
- Community-based feature requests and Request for Comments. You have a say in what Makerkit should build next.
- One-time payment, no subscriptions
- Includes access to our free Figma UI kit
Choose your Stack
Select the technology stack that best fits your project
Questions about licensing?
Read the MakerKit license terms and the MakerKit FAQ, or contact me.
A website starter with a product behind it
Choose it only if the website is the front door to a SaaS. For a site with no product, a free template is the better deal.
What is the MakerKit Next.js website?
The MakerKit Next.js website is the marketing site inside the MakerKit Next.js SaaS kit: landing page, pricing, FAQ, blog, documentation, changelog, and legal pages, in the same app as authentication, billing, and team accounts. Blog and docs content come from Keystatic, WordPress, or Supabase through one CMS interface.
Best for
- Founders who want the marketing site and the app in one codebase and one deploy
- Developers who want blog and docs content in Git (Keystatic) or in WordPress
- Products that need sign-in and payments soon after the site goes live
Not for
- Brochure sites, portfolios, or blogs with no product behind them
- Marketing teams that want a visual builder for every page
- Anyone looking for a free website template
Pages a SaaS needs
Landing page, pricing, FAQ, blog, docs, changelog, contact, and legal pages, already routed and styled.
One CMS interface
Keystatic, WordPress, or Supabase behind the same API, or your own client for Sanity, Contentful, or Strapi.
SEO plumbing
Per-page metadata, a sitemap route, and a documented JSON-LD pattern for marketing pages.
The app next door
Sign-in, billing, and teams live in the same Next.js app, so the pricing page links to a real checkout.
Built for AI coding agents
AGENTS.md and CLAUDE.md files at the root and in each package, rules for Claude Code, Cursor, Codex, and Gemini, and an MCP server your agent can call.
Lifetime license, continuous updates
Pay once, then pull new features, fixes, and framework upgrades into your repository with git. Maintained full-time since 2022.
With and without MakerKit
Next.js Website Starter FAQ
Is the Next.js Website Starter a standalone template?
No. It is the marketing site that ships inside the MakerKit Next.js SaaS kit: landing page, pricing, FAQ, blog, documentation, changelog, contact form, and legal pages, in the same Next.js app as the signed-in product. If you want a website with no accounts or billing, a free Next.js template is the better fit.
Where do the blog and documentation content come from?
From a CMS interface with three built-in implementations: Keystatic (local files or GitHub), WordPress, and Supabase. You can switch between them without rewriting data fetching, or write your own client for Sanity, Contentful, or Strapi.
What SEO work is already done?
Per-page metadata, a sitemap route, and a documented pattern for JSON-LD structured data on marketing pages. Keyword research, content, and backlinks are still your job.
Can I keep my marketing site on Framer, Webflow, or WordPress?
Yes. The kit documents a proxy configuration that sends marketing routes to an external website while MakerKit serves the application.
Why buy a SaaS kit if I only need a website today?
Only buy it if the website is the front door to a product. Then auth, billing, and teams sit next to your pages from day one, and the site and app share one design system and one deploy. If the site will stay a brochure, do not buy MakerKit.
Is MakerKit a one-time purchase or a subscription?
A one-time purchase. You get a lifetime license to the source code, continuous updates for the stack you bought, and unlimited projects for your own business, with no renewal fee. Building products for clients requires a Team license, and each client that receives the code needs their own license.
What support is included?
Discord support from me, Giancarlo, the founder who works on MakerKit full-time, and from the community. I help with setup, kit-related issues, and questions about the codebase. Team licenses add a private Discord channel for your team.
Can I evaluate MakerKit before buying, and can I get a refund?
Yes to the first: the documentation for every kit is public, and I can share code snippets or a demo on request. Refunds are generally not offered once repository access is redeemed, because you receive the full source code.
SaaS products built with MakerKit
A selection of products MakerKit customers have built on the kits.
I help founders launch faster - because life’s too short to write boilerplate code.
I am a software engineer with almost 15 years of experience writing code for both startups and enterprises.
My love for creating digital products inspired me to build Makerkit, a SaaS Starter Kit that helps you launch the SaaS you have always dreamed of.
My job is to help you achieve your goals, and I work hard to make it happen.
You can find me on Twitter, LinkedIn, and GitHub.
Launching a SaaS, not just a website? Start here.
You get the Next.js website and the product behind it in one codebase: pricing page, checkout, accounts, and teams. Buy it when the site is the front door to an app.