next-supabase-stripe-starter

See the demo

Introduction

Bootstrap your SaaS with a modern tech stack built to move quick. Follow the guide to get started.

What's included

• Supabase - Postgres database & user authentication
• Stripe - Checkout, subscriptions, and customer portal
• React Email - Easily build emails and send them with Resend
• Tailwindcss - CSS framework
• shadcn/ui - Prebuilt accessible components
• Webhooks to automatically synchronize Stripe with Supabase
• Stripe fixture to bootstrap product data
• Supabase migrations to bootstrap and manage your db schema
• Responsive, performant, and accessible prebuilt pages
• Animated button borders! Now you can look cool without nerds saying you shipped too late

Getting started

1. Setup Supabase

1. Go to supabase.com and create a project
2. Go to Project Settings → Database → Database password and click reset database password then click generate a new password. (I know you already made one, but this fixes a bug with their CLI where it doesn't like special characters in the password)
3. Save this password somewhere, you can't see it after closing the box

2. Setup Stripe

1. Go to stripe.com and create a project
2. Go to Customer Portal Settings and click the Active test link button

3. Setup Resend

1. Go to resend.com and create an account
2. Go to the API Keys page and create an API Key
3. Add the Supabase Resend integration

4. Deploy

1. Next click the deploy button ⬆️
2. On the form create a new repo and add the Supabase integration
3. Add the environment variables that you have available. For the stripe webhook secret just put any value - we will come back to update this after configuring the webhook
4. Click Deploy
5. While you wait, clone your new repo and open it in your code editor. Then create a file named .env.local. Copy and pase the contents of .env.local.example into this file and add the correct values. They should be the same values you added in above.

5. Stripe Webhook

1. After deploying go to your Vercel dashboard and find your Vercel URL
2. Next go to your Stripe dashboard, click Developers in the top nav, and then the Webhooks tab
3. Add an endpoint. Enter your Vercel URL followed by /api/webhooks
4. Click Select events
5. Check Select all events
6. Scroll to the bottom of the page and click Add endpoint
7. Click to Reveal signing secret and copy it
8. Go to your Vercel project settings → Environment Variables
9. Update the value of the STRIPE_WEBHOOK_SECRET env with your newly acquired webhook secret. Press Save

6. Run Supabase Migration

Now we're going to run the initial Supabase Migration to create your database tables.

1. Run npx supabase login
2. Run npx supabase init
3. Open your package.json and update both UPDATE_THIS_WITH_YOUR_SUPABASE_PROJECT_ID strings with your supabase project id
4. Run npm run supabase:link
5. Run npm run migration:up

7. Run Stripe Fixture

Stripe fixtures are an easy way to configure your product offering without messing around in the Stripe UI.

1. Install the Stripe CLI. For Macs run: brew install stripe/stripe-cli/stripe
2. Run (make sure to update the command with your Stripe sk) stripe fixtures ./stripe-fixtures.json --api-key UPDATE_THIS_WITH_YOUR_STRIPE_SK

8. Last steps

1. Do a Search All in your code editor for UPDATE_THIS and update all instances with the relevant value (except for .env.local.example!)
2. Delete the delete-me dir

9. Check it out!

You did it! You should be able to look in your Stripe dashboard and see your products, and you should also see the same data has been populated in your Supabase database. Now let's test everything.

1. Run npm i
2. Run npm run dev.
3. Go to the app and click Get started for free - this will take you to the login page
4. We haven't configured auth providers, so for now click Continue with Email and submit your email address
5. Click the link sent to your email and you should be redirected back to your app - authenticated
6. Click Get Started on one of the plans. This will take you to a Stripe checkout page (In test mode)
7. Enter 4242424242424242 as your credit card number. Fill out the rest of the form with any valid data and click Subscribe
8. You should be redirect to the Account page where you can see your active subscription
9. Click the Manage your subscription button

That's the end of the setup. The following are guides to help you code in your new codebase.

---

Guides

Managing products

Your products and prices are managed via the stripe-fixtures.json file. You can delete your test data in Stripe on the Developers page, make the changes you'd like, and then run the fixture command from above. When changes are made in Stripe the webhook hits the api route at src/app/api/webhooks. The handler will synchronize the data sent from Stripe to your Supabase database.

The metadata field in your fixture is where we can store info about the product that can be used in your app. For example, say you have a basic product, and one of the features of the product includes a max number of team invites. You can add a field to the metadata like team_invites. Then update the Zod schema in src/features/pricing/models/product-metadata.ts

Then you can make use of it like this:

const products = await getProducts();
const productMetadata = productMetadataSchema.parse(products[0].metadata); // Now it's typesafe 🙌!
productMetadata.teamInvites; // The value you set in the fixture

Managing your database schema

Migrations are a powerful concept for managing your database schema. Any changes you make to your database schema should be done through migrations.

Say you want to add a table named invites.

First run npm run migration:new add-invites-table Then edit your file to include:

create table invites (
  id uuid not null primary key default gen_random_uuid(),
  email text not null,
);
alter table invites enable row level security;

Then run npm run migration:up and your table will be added.

Configuring auth providers

There are many auth providers you can choose from. See the Supabase docs for the full the list and their respective guides to configure them.

Styling

• Learn more about shadcn/ui components
• Learn more about theming with shadcn/ui
• Learn more about the Tailwindcss theme config

Emails

Your emails live in the src/features/emails dir. Emails are finicky and difficult to style correctly, so make sure to reference the React Email docs. After creating your email component, sending an email is as simple as:

import WelcomeEmail from '@/features/emails/welcome';
import { resendClient } from '@/libs/resend/resend-client';

resendClient.emails.send({
  from: 'no-reply@your-domain.com',
  to: userEmail,
  subject: 'Welcome!',
  react: <WelcomeEmail />,
});

File structure

The file structure uses the group by feature concept. This is where you will colocate code related to a specific feature, with the exception of UI code. Typically you want to keep your UI code in the app dir, with the exception of reusable components. Most of the time reusable components will be agnostic to a feature and should live in the components dir. The components/ui dir is where shadcn/ui components are generated to.

Going live

Follow these steps when you're ready to go live:

1. Activate your Stripe account and set the dashboard to live mode
2. Repeat the steps above to create a Stripe webhook in live mode, this time using your live url
3. Update Vercel env variables with your live Stripe pk, sk, and whsec
4. After Vercel has redeployed with your new env variables, run the fixture command using your Stripe sk

---

Support

If you need help with the setup, or developing in the codebase, feel free to reach out to me on Twitter @kolbysisk - I'm always happy to help.

Contribute

PRs are always welcome.

---

This project was inspired by Vercel's nextjs-subscription-payments.