Next.jsReactSaaSStarter

Hikari — Next.js SaaS Template

By coremvp

Hikari is an open-source SaaS starter template built on the Next.js App Router, integrating Supabase authentication and data management, Stripe subscription billing, and a documentation, blog, and testing toolchain.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

3 previews
Desktop homepage1 / 3
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 3

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-10-03View source

What stands out

A quick read of the recorded project description.

01

Built on the Next.js App Router, including common SaaS pages such as pricing, dashboard, documentation, and blog

02

Integrates Supabase authentication and PostgreSQL data access, and includes storage policies and browser-side image compression examples

03

Integrates Stripe Checkout, customer portal, and webhooks to synchronize pricing plans and subscription status

04

Uses TailwindCSS and shadcn/ui components, with Zod for data validation

05

Includes Jest, React Testing Library, and Playwright testing tools, plus ESLint, Prettier, Husky, and Commitlint development standards

06

Documentation and blog use Fumadocs' MDX compiler, and the README also provides tRPC integration guidance

Template Details

Hikari is published on GitHub by coremvp under the MIT license and is positioned as a starter template for SaaS subscription applications. It uses the Next.js App Router and pre-builds common SaaS modules such as user authentication, PostgreSQL data access, Stripe Checkout and customer portal, and subscription status synchronization, and includes pages for pricing, dashboard, documentation, and blog. The README explicitly notes that the project is still in public development (work in progress), so features and structure may continue to change.

The template's UI layer is based on TailwindCSS and shadcn/ui components, uses Zod for data validation, and integrates testing tools such as Jest, React Testing Library, and Playwright, as well as development standards tools including ESLint, Prettier, Husky, and Commitlint. The documentation and blog sections use Fumadocs' MDX compiler. The README also mentions Supabase storage policies and browser-side image compression, tRPC integration guidance, local Supabase and Docker development commands, Paraglide internationalization support, and the need to archive Stripe test products and switch to production environment variables before redeploying for launch.

Using this template requires preparing external services such as Supabase and Stripe yourself, and these services may incur costs; the licenses for third-party assets such as demo images, fonts, and icons must be verified separately.

Next.jsSaaSStarter

Is it right for your project?

Use Cases

  • Quickly building a SaaS project skeleton with subscription billing and user authentication
  • Next.js applications that want Supabase as the authentication and database backend
  • Starter templates that need to include marketing pages, pricing pages, dashboards, documentation, and a blog at the same time
  • Introducing unit testing, end-to-end testing, and code standards tooling early in a project

Suitable For

  • Developers familiar with the Next.js App Router and TypeScript
  • Teams planning to build subscription products with Supabase and Stripe
  • Personal projects that need reference SaaS page structures and toolchain configuration

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    The README notes that the project is still in public development, so features and structure may change; check the repository's latest status before use

  2. 2

    You must prepare Supabase and Stripe accounts yourself and configure the corresponding environment variables; these external services may incur costs

  3. 3

    Before launch, archive Stripe test-mode products, switch to production mode, update environment variables, and redeploy

  4. 4

    The licenses for third-party assets such as demo images, fonts, and icons must be verified separately and cannot be determined solely from the code's MIT license

  5. 5

    Local development involves Supabase, Docker, and custom commands provided by the repository; refer to the official Quick Start documentation for specific steps

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version under the MIT license in the public repository; the free scope applies to that version's code and does not mean external services or third-party assets are free.

Must comply with when using

  • You may use, modify, commercialize, and distribute this version's code for free.
  • When distributing copies or substantial portions of the code, retain the original author's copyright notice and the complete MIT license notice.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • The project is still in an ongoing public development state, so features and structure may change at any time, and it is not guaranteed to be stable or production-ready.
  • Before launch, you must archive Stripe test-mode products, switch to production mode, and update environment variables; otherwise subscription billing will not work properly.
  • Authentication and data management depend on the external Supabase service, which requires registering an account and configuring it yourself and may incur costs.
  • Subscription billing depends on the external Stripe service, which requires opening an account and configuring API keys yourself and may incur costs.
  • Local development requires Docker and a Supabase environment and depends on custom commands provided by the repository, so environment setup has some barriers.
  • Demo images, fonts, icons, and other third-party assets must be verified under their respective licenses and cannot be determined solely from the code's MIT license.
  • External services such as domains, hosting, databases, payments, or AI may incur additional charges.
View Original Text Basis

Permission is hereby granted, free of charge

Original License Text

This app is a work in progress. I'm building this in public.

Original README

Before going live, archive all test mode Stripe products. Switch Stripe from test mode to production mode and update your environment variables.

Original README

Secure user management and authentication with [Supabase](https://supabase.io/docs/guides/auth)

Original README

Seamless integration with [Stripe Checkout](https://stripe.com/docs/payments/checkout)

Original README

Develop locally with Supabase, Docker, and a set of custom commands

Original README
https://github.com/coremvp/Hikari/blob/main/LICENSEhttps://github.com/coremvp/Hikari/blob/main/README.md

Compiled by DeepSeek based on repository license and README ·2026-10-03. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
More documented · 96 / 100
Technologies
Next.js · React
Website type
SaaS · Starter
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2026-10-03
Screenshot last checked
2026-10-03

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Next.js as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Review declaration: [email protected] · 2026-10-04

Inspect the recorded source material

SHA-256: a1546b56b8ce135a5f2a70a5db329b6f4446a83742df7ae26ed06837653d1631

2026-10-03T15:03:34.203Z

Source file / repository
# 🚀 Complete Next.js Subscription Starter Template

The all-in-one starter kit for building high-performance SaaS applications using Next.js, TailwindCSS, and Supabase.

> **Warning**: This app is a work in progress. I'm building this in public. Follow the progress on Twitter [@antoineross\_\_](https://twitter.com/antoineross__). Check out the features below.

## 🎉 Features

- 🔐 **Complete Auth Package**: Secure user management and authentication with [Supabase](https://supabase.io/docs/guides/auth)
- 🛠️ **Data Management**: Powerful data access & management tooling on top of PostgreSQL with [Supabase](https://supabase.io/docs/guides/database)
- 💳 **Stripe Integration**: Seamless integration with [Stripe Checkout](https://stripe.com/docs/payments/checkout) and the [Stripe customer portal](https://stripe.com/docs/billing/subscriptions/customer-portal)
- 🌐 **Pricing & Subscriptions**: Automatic syncing of pricing plans and subscription statuses via [Stripe webhooks](https://stripe.com/docs/webhooks)
- 🌈 **TailwindCSS & Tailwind UI**: Customized and flexible UI components with Tailwind UI
- ⚛️ **React 18**: Enjoy the latest features and improvements with React 18
- 📘 **TypeScript**: Strongly typed programming for better development experience
- 🎨 **Shadcn/ui**: Beautiful and customizable UI components
- 🔍 **Zod Validation**: Schema validation to keep your data safe and sound
- 🧪 **Testing Tools**: Integrated unit and e2e testing with Jest, React Testing Library, and Playwright
- 🧑‍💻 **Developer Experience**: ESLint, Prettier, Husky, and Commitlint for maintaining code quality and consistency
- 📀 **Supabase storage** - Included are setting up policies, and handling image compression in the browser.
- ⼬ **tRPC** - Included a guide on how to add a very lean trpc router for your api. You just need to add 3 folders, and 1 file.
- ⚙️ **Local Development**: Develop locally with Supabase, Docker, and a set of custom commands
- 📚 **Documentation & Blog**: Utilize MDX compiler from the open-source project Fumadocs for documentation and blog content.

## 🎬 Demo

[Live Demo](https://hikari.antoineross.com/)

**Hero Section:** ![Screenshot of demo](./public/hikari-landingpage.png)

**Dashboard View:** ![Screenshot of dashboard](./public/hikari-dashboard.png)

**Pricing Table:** ![Screenshot of pricing](./public/hikari-pricing.png)

**Documentation:** ![Screenshot of documentation](./public/hikari-documentation.png)

**Blog:** ![Screenshot of blog](./public/hikari-blog.png)

## 📄 Quick Start Guide

Get up and running quickly by following the [Quick Start Guide](https://hikari.antoineross.com/docs/quick-start).

## 🚀 Going Live

### **1. Archive Testing Products**

Before going live, archive all test mode Stripe products. Switch Stripe from test mode to production mode and update your environment variables.

### **2. Redeploy**

After updating environment variables, redeploy your application through Vercel.

## 📚 Additional Features

- 📈 **Analytics Ready**: Easy integration with analytics tools like Google Analytics
- 🌐 **I18n Support**: Built-in internationalization with Paraglide
- 🔥 **Lighthouse Performance**: Achieve a perfect score with optimized performance, accessibility, and SEO

## 🤝 Contribution

To contribute:

1. Fork the repository.
2. Create a new branch.
3. Make your changes and commit them.
4. Push to the forked repository.
5. Create a pull request.

## ❤️ Support

If you like the project, consider leaving a star. 🌟
[![Star History Chart](https://api.star-history.com/svg?repos=antoineross/Hikari&type=Date)](https://star-history.com/#antoineross/Hikari&Date)

Made by [Antoine Ross](https://antoineross.com).
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.