Full-stack AI SaaS launch system
ZShip gives you the production stack for launch: authentication, payments, credits, AI workflows, landing pages, blog, docs, and a dashboard already wired for delivery.
Email login, Google sign-in, session cookies, guest conversion, and billing-aware dashboard routes are already in the app.
What ships with ZShip
From authentication and payments to marketing surfaces and edge APIs — the monorepo wires opinionated defaults so you ship product logic instead of plumbing.
Authentication
Email login, Google sign-in, verification, password reset, and guest-to-user upgrade flows are already part of the web-nuxt app.
Payments and credits
Pricing, checkout hooks, credit accounting, and protected dashboard routes are already mapped into the product skeleton.
Marketing and content
You are not stitching separate repos together. ZShip ships the acquisition layer and the application layer in one stack.
Edge platform
Backend templates target Workers + Hono with bindings you can grow into: databases, cache, and object storage without replatforming.
Integrated account flow
The web-nuxt app already has auth pages, server proxy routes, cookie handling, email verification, password reset, guest conversion, and dashboard entry points.
01
The landing header now links straight to /auth/login, which renders the existing shared auth island.
02
Nuxt server endpoints under /api/auth/* proxy login, register, verify-email, guest-login, and logout to the auth service.
03
Successful auth writes the app cookie and unlocks the dashboard flow instead of stopping at a static form.
FAQ
Billing, deployment, and customization — straight answers so you can decide faster.
Yes. The template is built for Cloudflare Pages, Workers, D1, KV, and R2. You own the repo and can run wrangler against your account; nothing locks you to a proprietary host beyond your own infrastructure choices.
Checkout flows create or renew subscriptions and map webhook events into a credit ledger your dashboard reads. You can start with Stripe test mode, then flip keys for production when you are ready.
No. End-users only see what you ship. The dashboard is for operators and your customers who need billing or keys — you can hide routes or brand everything through the Nuxt layers.
Provider calls live behind service workers with a stable generate/status contract. Swap endpoints and keys in one place without rewriting the whole app, as long as you keep the same API shape.
Yes. web-nuxt ships with i18n routes, locale-aware links, and message files you can extend. Marketing and product surfaces share the same app so translations stay consistent.
Security fixes, dependency bumps, and documented merge guidance for the official template. You pull changes into your fork when you want — the monorepo layout keeps apps and packages separated for easier diffs.
Teams shipping with ZShip
Early teams using the stack for auth, billing, and AI workflows — anonymized roles, real workflows.
“We went from zero to Stripe + credits in a weekend. The hardest part was our product copy, not the integration.”
“Guest login and upgrade path actually worked out of the box. We only customized the theme and provider keys.”
“Having blog, docs, and dashboard in one Nuxt app cut our deployment surprises in half.”
“The Workers + Hono services matched how we wanted to scale regions. D1 for metadata was enough to start.”
“We ship in English first; i18n routing meant we could add Japanese later without a separate marketing site.”
“Honestly expected more glue code. Most days we are editing business logic, not fighting auth cookies.”
Launch faster
Start from a repo that already knows how your SaaS should behave in production, then ship your differentiated product logic on top.
