Features
Explore the authentication, billing, database, email, and content flows included in the standalone template.
Build on the included product flows
The template starts with the product paths that usually require the most cross-provider setup. Each feature stays inside the same Next.js application: browser code calls the same-origin Hono API, server-only services make trusted decisions, and repositories or providers own the final state.
Authentication
Supabase Auth sessions, email and password flows, OAuth, and protected routes.
Payments
Stripe lifetime purchases, subscriptions, webhooks, and the customer portal.
Database
Supabase Postgres with Drizzle models and repository-owned queries.
Supabase Auth emails with an optional Resend path for product email.
Documentation
Fumadocs pages, source-backed search, Blog content, and Copy Markdown.
Keep trusted work on the server
The browser should call the template's /api/* routes. Hono handles the HTTP
request and calls server-only services; repositories and provider clients then
read or write the final state. This keeps database credentials, Stripe secrets,
and privileged Supabase access out of browser bundles.
Use Project Structure for the file map, or choose a feature above for its setup and extension points.
Was this page helpful?