Provides a Next.js starter application on top of Basejump core, including a complete interface for personal accounts, team accounts, invitations, member and permission management, and subscription billing
basejump-next — Next.js Starter Template
By usebasejump
A Next.js and Supabase starter template that builds on Basejump core to provide personal accounts, team accounts, invitations, member permission management, and a Stripe subscription billing interface.
Explore the design
Compare the page layouts and mobile experience. Open any screenshot for a closer look.
Actual screenshot captured by the server browser.
All pages & views 3
Screenshots show visual appearance; interactive behavior may differ.
What stands out
A quick read of the recorded project description.
Users automatically receive a personal account after registering through Supabase auth; billing for personal accounts and team accounts can each be enabled or disabled separately, and team accounts can also be disabled entirely
Permissions are handled based on RLS, with convenience methods to restrict row-level access according to a user's account access and role within the account
Billing supports Stripe out of the box and can also integrate other providers; billing-related keys are configured in supabase/functions/.env
Provides a basic dashboard accessible only to authenticated users; authentication supports email/password and can be extended with other authentication methods supported by Supabase
Includes a testing toolkit that can be used to test your own Supabase functions and schema, and does not require the project to use Basejump
Template Details
Basejump Nextjs Starter layers a Next.js starter application on top of Basejump core, providing a complete interface covering personal accounts, team accounts, invitations, member and permission management, and subscription billing. The repository uses the MIT license, so the code may be used, modified, commercialized, and distributed free of charge, provided the copyright and license notices are retained; third-party assets such as demo images, fonts, and icons, as well as external services such as domains, hosting, databases, and payments, must be verified and paid for separately.
For the account system, users automatically receive a personal account after registering through Supabase auth, and billing for personal accounts can be enabled or disabled; team accounts are billing accounts that can be shared by multiple users, can likewise be disabled, and can also have their billing turned off. If only personal accounts are desired, team accounts can be disabled. Permissions are handled through RLS, consistent with Supabase usage, and Basejump provides convenience methods to restrict row-level access based on a user's account access and role within the account. Billing supports Stripe out of the box, and other providers can also be integrated.
The frontend includes a basic dashboard accessible only to authenticated users; authentication supports email/password and can be extended with other authentication methods supported by Supabase. For testing, Basejump itself has comprehensive tests and also provides a testing toolkit to facilitate testing your own Supabase functions and schema; this toolkit does not require using Basejump.
The quick start process is: run yarn install, run supabase start, create .env.local by referring to .env.example and fill in the Supabase configuration, then run yarn dev. When billing needs to be handled, a Stripe account must be created, and the Stripe keys must be written into the supabase/functions/.env file; the repository provides a copyable example file.
Is it right for your project?
Use Cases
- Quickly building an account system interface with personal accounts and team accounts for a SaaS product
- Supabase projects that want to use RLS to control row-level data permissions by account access and role
- Projects planning to integrate Stripe subscription billing and needing ready-made billing interfaces and edge function configuration examples
- Needing a testing toolkit for testing your own Supabase functions and schema
Suitable For
- Developers building multi-user SaaS applications with Next.js and Supabase
- Projects needing a basic interface for personal accounts, team accounts, invitations, and member permission management
- Projects preparing to integrate Stripe subscription billing and wanting to reference an existing implementation
- Teams that want to use, modify, and distribute the starter code under the MIT license
Getting started & customization
Use these recorded setup notes alongside the repository instructions for your chosen version.
- 1
Run yarn install, supabase start, and create .env.local by referring to .env.example and fill in the Supabase configuration, then run yarn dev
- 2
Before handling billing, create a Stripe account and write the Stripe keys into supabase/functions/.env; the repository provides a copyable example file
- 3
The code uses the MIT license; when distributing copies or substantial portions, retain the original author's copyright notice and the complete MIT license notice
- 4
Third-party assets such as demo images, fonts, and icons must be checked separately under their respective licenses; external services such as domains, hosting, databases, and payments may incur separate charges
License & source material
Usage conditions & limitations
Free to use · keep license noticeThis entry covers the free version in the public repository under the MIT license; the free scope is the code of this version and does not mean that external services or third-party assets are free.
Must comply with when using
- The code of this version may be used, modified, commercialized, and distributed free of charge.
- 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
- Using billing features requires registering a Stripe account and configuring keys yourself; Stripe is an external paid service and may incur charges.
- Before running, you must prepare your own Supabase configuration (project/keys); Supabase is an external service and may incur charges.
- Demo images, fonts, icons, and other third-party assets must be checked under their respective licenses and cannot be judged solely by the code's MIT license.
- External services such as domains, hosting, databases, payments, or AI may incur separate charges.
View Original Text Basis
Permission is hereby granted, free of charge
Original License Text
you'll need to set up a Stripe account and add your Stripe keys to your `supabase/functions/.env` file
Original README
https://github.com/usebasejump/basejump-next/blob/main/LICENSEhttps://github.com/usebasejump/basejump-next/blob/main/README.mdCreate a `.env.local` copy of the `.env.example` file with the correct values for Supabase
Original README
Compiled by DeepSeek based on repository license and README ·2026-10-02. 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 · 81 / 100
- Technologies
- Next.js · React
- Website type
- 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
- 2024-11-06
- Screenshot last checked
- 2026-10-02
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.
Automatically checked against source and license rules; no manual editorial review.
Inspect the recorded source material
SHA-256: 286c2d8a8a64e86e1ec46a95f3edf8af8bc2deca2251d890a6bf0ac5b803d967
2026-10-02T20:49:46.352Z
Source file / repository# Basejump Nextjs Starter Adds a Nextjs starter app on top of [Basejump core](https://github.com/usebasejump/basejump). This is a complete interface with support for personal accounts, team accounts, invitations, managing members/permissions and subscription billing. [Learn more at usebasejump.com](https://usebasejump.com). Ask questions [on X / Twitter](https://twitter.com/tiniscule)  ## Basejump Core Features - **Personal accounts**: Every user that signs up using Supabase auth automatically gets their own personal account. Billing on personal accounts can be enabled/disabled. - **Team accounts**: Team accounts are billable accounts that can be shared by multiple users. Team accounts can be disabled if you only wish to allow personal accounts. Billing on team accounts can also be disabled. - **Permissions**: Permissions are handled using RLS, just like you're used to with Supabase. Basejump provides convenience methods that let you restrict access to rows based on a user's account access and role within an account - **Billing**: Basejump provides out of the box billing support for Stripe, but you can add your own providers easily. If you do, please consider contributing them so others can benefit! - **Testing**: Basejump is fully tested itself, but also provides a suite of testing tools that make it easier to test your own Supabase functions and schema. You can check it out at [database.dev/basejump/supabase_test_helpers](https://database.dev/basejump/supabase_test_helpers). You do not need to be using Basejump to use the testing tools. ## Next Frontend Features - **Basic Dashboard**: A basic dashboard implementation restricted to authenticated users - **User Authentication**: Support for email/password - but add any auth provider supported by Supabase - **Personal accounts**: Every user that signs up using Supabase auth automatically gets their own personal account. Billing on personal accounts can be enabled/disabled. - **Team accounts**: Team accounts are billable accounts that can be shared by multiple users. Team accounts can be disabled if you only wish to allow personal accounts. Billing on team accounts can also be disabled. - **Billing**: Basejump provides out of the box billing support for Stripe, but you can add your own providers easily. If you do, please consider contributing them so others can benefit! ## Quick Start 1. Run `yarn install` 2. Run `supabase start` 3. Create a `.env.local` copy of the `.env.example` file with the correct values for Supabase 4. Run `yarn dev` When you're ready to work on billing, you'll need to set up a Stripe account and add your Stripe keys to your `supabase/functions/.env` file. There's an example file you can copy. ## Helpful Links - [Basejump Docs](https://usebasejump.com/docs) - [Creating new protected tables](https://usebasejump.com/docs/example-schema) - [Testing your Supabase functions](https://usebasejump.com/docs/testing) ## Contributing Yes please! Please submit a PR with your changes to [the basejump-next github repo](https://github.com/usebasejump/basejump-next). You can contribute in the following places: - [Basejump core](https://github.com/usebasejump/basejump) - [Basejump Nextjs](https://github.com/usebasejump/basejump-next) - [Basejump edge functions / billing functions](https://github.com/usebasejump/basejump-deno-packages) - [Supabase Test Helpers](https://github.com/usebasejump/supabase-test-helpers)
Explore similar templates
Compare previews and descriptions within the same stack and category.

Next.js SaaS Starter
The official Next.js SaaS starter template, integrating email/password authentication, Stripe Checkout subscriptions, a dashboard with user/team CRUD, basic Owner/Member RBAC, and activity logging.
Next.js · SaaS

Next.js Commerce
Vercel's officially maintained Next.js App Router ecommerce starter with deep Shopify integration, offering a complete product catalog, cart, and checkout flow. Core logic is modular for swapping backends, and community provider versions exist for BigCommerce, Medusa, and Saleor.
Next.js · E-commerce

Next-js-Boilerplate
A developer-first Next.js 16 starter with Tailwind CSS 4 and TypeScript, supporting both App Router and Page Router.
Next.js · Starter

tailwind-nextjs-starter-blog
A Next.js and Tailwind CSS blog starter template using Contentlayer for Markdown/MDX, with built-in SEO, code highlighting, and tags. It targets personal technical blogs and migration from Jekyll/Hugo to React, and supports one-click Vercel deployment.
Next.js · Blog

next-forge
next-forge is a Turborepo-based Next.js template maintained by Vercel, positioned as a starting point for SaaS products.
Next.js · Starter

SaaS-Boilerplate
SaaS-Boilerplate is an open-source SaaS starter template built with Next.js App Router, React 19, TypeScript, Tailwind CSS, and Shadcn UI.
Next.js · SaaS
