Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A full-stack Next.js SaaS starter with authentication, Stripe billing, and entitlements powered by Update, Supabase, and Stripe.
The Update + Next.js Template is a full-stack SaaS starter that combines Next.js's App Router with Update's authentication and entitlements, Supabase auth, and Stripe billing, giving developers a working subscription product base instead of a blank slate.
The Update + Next.js Template is a production-oriented boilerplate from Update (update.dev) that wires together Next.js, Supabase, and Stripe into one application. It takes API keys from the Update dashboard and Supabase project settings as input and produces a runnable web app with sign-in, subscription checkout, customer portal, and plan-based access control. The project is published on GitHub under the MIT license and is designed to be deployed to Vercel with a single click.
client.entitlements.check() that conditionally renders UI for authorized users.utils/update/client.ts for browser-side usage and utils/update/server.ts for server-side usage, so the same template works in the App Router, Middleware, Client, and Server contexts.SaaS founders who want a working subscription and auth setup without building it from scratch; Next.js developers who need a reference implementation of Update client/server utilities and entitlements; product teams that require plan-based, org-based, or role-based access control from day one.
utils/update/client.ts and utils/update/server.ts work together before customizing your own billing and auth flows.Set up locally by cloning the repository, running npm install, and copying .env.example to .env.local. Fill in the public key from the Update dashboard and the Supabase URL and anon key from Supabase project settings, then run npm run dev to view the app at localhost:3000. The Vercel deploy flow automates the same environment configuration.
Yes. The repository is released under the MIT license, so you can use it commercially and modify it freely. You will still need your own accounts for the third-party services it relies on: Update, Supabase, and Stripe.
You need three environment variables: NEXT_PUBLIC_UPDATE_PUBLIC_KEY from the Update dashboard, and NEXT_PUBLIC_SUPABASE_URL plus NEXT_PUBLIC_SUPABASE_ANON_KEY from your Supabase project's API settings. Without these, authentication and billing will not work.
Not yet. The README lists usage-based plans as coming soon. The current Stripe integration covers subscriptions, checkout, trials, failed payment recovery, and cancel/reactivate flows through the customer portal.
The README highlights the Update client setup, entitlements checks, and Stripe billing integration rather than a full page inventory. The template is a full-stack SaaS starter, so it includes the routing, middleware, and UI components needed to support auth and billing flows.
The template is Next.js-based, so it can be deployed to any platform that supports Next.js, but the provided one-click deploy button targets Vercel. The local development flow is the same on any machine with Node.js and npm installed.
