saas-starter

Sat, 23 Aug 2025 15:26:48 +0800

nextjs/saas-starter

Next.js SaaS Starter

This is a starter template for building a SaaS application using Next.js with support for authentication, Stripe integration for payments, and a dashboard for logged-in users.

Demo: https://next-saas-start.vercel.app/

Features

Marketing landing page (/) with animated Terminal element
Pricing page (/pricing) which connects to Stripe Checkout
Dashboard pages with CRUD operations on users/teams
Basic RBAC with Owner and Member roles
Subscription management with Stripe Customer Portal
Email/password authentication with JWTs stored to cookies
Global middleware to protect logged-in routes
Local middleware to protect Server Actions or validate Zod schemas
Activity logging system for any user events

Tech Stack

Framework: Next.js
Database: Postgres
ORM: Drizzle
Payments: Stripe
UI Library: shadcn/ui

Getting Started

1
2
3

git clone https://github.com/nextjs/saas-starter
cd saas-starter
pnpm install

Running Locally

Install and log in to your Stripe account:

`1`	`stripe login`

Use the included setup script to create your .env file:

`1`	`pnpm db:setup`

Run the database migrations and seed the database with a default user and team:

1
2

pnpm db:migrate
pnpm db:seed

This will create the following user and team:

User: test@test.com
Password: admin123

You can also create new users through the /sign-up route.

Finally, run the Next.js development server:

`1`	`pnpm dev`

Open http://localhost:3000 in your browser to see the app in action.

You can listen for Stripe webhooks locally through their CLI to handle subscription change events:

`1`	`stripe listen --forward-to localhost:3000/api/stripe/webhook`

Testing Payments

To test Stripe payments, use the following test card details:

Card Number: 4242 4242 4242 4242
Expiration: Any future date
CVC: Any 3-digit number

Going to Production

When you’re ready to deploy your SaaS application to production, follow these steps:

Set up a production Stripe webhook

Go to the Stripe Dashboard and create a new webhook for your production environment.
Set the endpoint URL to your production API route (e.g., https://yourdomain.com/api/stripe/webhook).
Select the events you want to listen for (e.g., checkout.session.completed, customer.subscription.updated).

Deploy to Vercel

Push your code to a GitHub repository.
Connect your repository to Vercel and deploy it.
Follow the Vercel deployment process, which will guide you through setting up your project.

Add environment variables

In your Vercel project settings (or during deployment), add all the necessary environment variables. Make sure to update the values for the production environment, including:

BASE_URL: Set this to your production domain.
STRIPE_SECRET_KEY: Use your Stripe secret key for the production environment.
STRIPE_WEBHOOK_SECRET: Use the webhook secret from the production webhook you created in step 1.
POSTGRES_URL: Set this to your production database URL.
AUTH_SECRET: Set this to a random string. openssl rand -base64 32 will generate one.

Other Templates

While this template is intentionally minimal and to be used as a learning resource, there are other paid versions in the community which are more full-featured:

headlamp

Sun, 06 Apr 2025 15:25:35 +0800

kubernetes-sigs/headlamp

NOTICE: We have recently moved the project under the Kubernetes SIG UI (and the repo under the kubernetes-sigs org). Container images are still at ghcr.io. Please bear with us while we may experience some broken links.

Headlamp is an easy-to-use and extensible Kubernetes web UI.

Headlamp was created to blend the traditional feature set of other web UIs/dashboards (i.e., to list and view resources) with added functionality.

Features

Vendor-independent / generic Kubernetes UI
Works in-cluster, or locally as a desktop app
Multi-cluster
Extensible through plugins
UI controls reflecting user roles (no deletion/update if not allowed)
Clean & modern UI
Cancellable creation/update/deletion operations
Logs, exec, and resource editor with documentation
Read-write / interactive (actions based on permissions)

Screenshots

Quickstart

If you want to deploy Headlamp in your cluster, check out the instructions on running it in-cluster.

If you have a kubeconfig already, you can quickly try Headlamp locally as a desktop application for Linux, Mac, or Windows. Make sure you have a kubeconfig file set up with your favorite clusters and in the default path so Headlamp can use it.

Accessing

Headlamp uses RBAC for checking users’ access to resources. If you try Headlamp with a token that has very limited permissions, you may not be able to view your cluster resources correctly.

See the documentation on how to easily get a Service Account token for your cluster.

Tested platforms

We maintain a list of the Kubernetes platforms we have tested Headlamp with. We invite you to add any missing platforms you have tested, or comment if there are any regressions in the existing ones.

Extensions / Plugins

If you are interested in tweaking Headlamp to fit your use-cases, you can check out our plugin development guide.

Get involved

Check out our:

Guidelines
Code of Conduct,
#headlamp slack channel in the Kubernetes Slack
Monthly Community Meeting

Roadmap / Release Planning

If you are interested in the direction of the project, we maintain a Roadmap. It has the biggest changes planned so far, as well as a board tracking each release.

License

Headlamp is released under the terms of the Apache 2.0 license.

Frequently Asked Questions

For more information about Headlamp, see the Headlamp FAQ.

RBAC on Producthunt daily

saas-starter

nextjs/saas-starter

Next.js SaaS Starter

Features

Tech Stack

Getting Started

Running Locally

Testing Payments

Going to Production

Set up a production Stripe webhook

Deploy to Vercel

Add environment variables

Other Templates

headlamp

kubernetes-sigs/headlamp

Features

Screenshots

Quickstart

Accessing

Tested platforms

Extensions / Plugins

Get involved

Roadmap / Release Planning

License

Frequently Asked Questions