Launch from a working stack
Start from a deployed Next.js, Vercel, Neon, Clerk, and Stripe slice instead of wiring the same foundations again.
A reusable starting line
Launch the experiment. Keep the foundation.
ZET is a production-shaped SaaS template with auth, data, billing, content, and release habits already working—so the next idea starts with the useful questions.
Ship in hoursFail-closed authStripe sandbox
Launch manifest
Example workspacezstack Experiment Template
A working product surface, before product-specific code.
Signals12Illustrative data
Open learnings4Illustrative data
- Clerk Managed account accessReady
- Neon Serverless product dataReady
- Stripe Checkout and portalSandbox
Next.js App RouterNeon PostgresClerk authStripe BillingSmoke checksSEO and feeds
Foundation
The common work is already done.
A small set of reusable slices, composed from the zstack design system and kept deliberately free of product-specific assumptions.
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.
Operating model
A shorter path from idea to evidence.
ZET stays useful by making the repeatable parts obvious and leaving the experiment itself easy to change.
- 01
Fork a proven boundary
Keep auth, billing, data, content, and release behavior separate from the product idea.
- 02
Test one real loop
Use the included signal-capture demo to verify a write, read, and review flow end to end.
- 03
Ship with evidence
Run the same type, test, build, smoke, and release checks before every experiment goes live.
Ready to inspect it?
Use the working slice before you fork the template.
The demo proves the database loop while keeping submitted content out of public view.