Launch from a working stack
Start from a deployed Next.js, Vercel, Neon, Clerk, and Stripe slice instead of wiring the same foundations again.
Template foundation
Common SaaS work, made reusable.
ZET keeps the foundation deliberately generic. Product decisions remain local while the plumbing and operating checks are ready to use.
Next.js App RouterNeon PostgresClerk authStripe BillingSmoke checksSEO and feeds
Included
Six foundations, one coherent system.
Stable components and feature boundaries cover the repeated work without hiding ordinary React behind template-specific abstractions.
Included
Managed sign-in by default
Use Clerk for Google sign-in, email verification-code sign-in, persistent sessions, and local user sync.
Billing path included
Stripe Checkout, Customer Portal, webhook handling, and local entitlement fields are already shaped for SaaS reuse.
Neon-backed product data
Keep runtime data in Postgres with small migrations, lazy database clients, and build-safe fallback states.
Content and SEO starter
Publish database-backed content with RSS, sitemap, robots, and llms.txt so experiments are discoverable early.
Feature modules that scale
Keep product behavior in domain, service, repository, and action modules while routes stay thin.
Under the hood
Designed to be changed, not worshipped.
Each area is useful on its own, readable in the repository, and replaceable when an experiment needs something different.
Template Surface
Public pages that can become any SaaS
Home, Features, Pricing, Blog, Account, and Subscription routes give each experiment a polished starting point without locking it to one product idea.
- Generic placeholder copy
- Reusable page sections
- Dedicated pricing route
Auth And Users
Signed-in behavior without custom auth work
The template prefers managed auth, keeps private routes fail-closed, and syncs authenticated users into the local Postgres users table.
- Google sign-in ready
- Email code sign-in ready
- Local users table sync
Operations
Deployment and release habits baked in
Release logs, smoke checks, and setup runbooks make the template useful for repeated experiments instead of one heroic launch.
- Vercel build command
- Local and hosted smoke checks
- Secret-safe setup notes
Next step
See the foundation behave like a product.
Open the signal-capture loop or inspect the sample subscription surface.