# ZShip
> Cloudflare-native AI SaaS development template and customer platform for launching, selling, delivering, and operating multiple AI SaaS products.

## Key Facts
- ZShip is built around 10+ independent Cloudflare Worker services for auth, billing, support, blog, CDN, site operations, prompts, check-in, AI, and delivery.
- The app_key tenant model lets one foundation power multiple product sites while keeping project data and operations scoped.
- The customer platform includes orders, licenses, GitHub access, downloads, support tickets, store purchases, credits, changelog, roadmap, docs, blog, and showcase pages.
- ZShip is optimized for builders selling reusable AI SaaS products, templates, components, and value-added services rather than only a single landing page.
- The default deployment stack uses Nuxt, Astro, Cloudflare Pages, Workers, D1, KV, R2, and service bindings.

## Main Pages
- [ZShip - Cloudflare AI SaaS Development Template](https://zship.ai): Cloudflare-native AI SaaS template with multi-tenant services, customer platform, licensing, GitHub delivery, docs, blog, roadmap, and support.
- [ZShip Lifetime Pricing](https://zship.ai/pricing): Lifetime plan, capability comparison, checkout details, credits, support, and post-purchase delivery workflow.
- [ZShip vs ShipAny vs MkSaaS](https://zship.ai/compare): Direct comparison page for AI SaaS builders evaluating ZShip against ShipAny and MkSaaS.
- [ZShip Docs](https://zship.ai/docs): Technical documentation for deployment, Cloudflare services, tenant configuration, admin, payments, AI gateway, and operations.
- [ZShip Store](https://zship.ai/store): Component marketplace for templates, UI blocks, snippets, and delivery assets connected to the ZShip credit system.
- [ZShip Blog](https://zship.ai/blog): Editorial content covering SaaS launch workflows, pricing, documentation, customer operations, and growth.
- [ZShip Showcase](https://zship.ai/showcase): Community showcase of ZShip-based sites and products.
- [ZShip Changelog](https://zship.ai/changelog): Release notes and product change history for ZShip.
- [ZShip Roadmap](https://zship.ai/roadmap): Public roadmap for planned, in-progress, and completed ZShip platform work.

## Documentation
- [Codebase](https://zship.ai/docs/codebase): ZShip project structure: core apps and backend services.
- [Important Notes](https://zship.ai/docs/important-notes): Rules you must follow: do not modify official apps and backend services.
- [Introduction](https://zship.ai/docs/introduction): ZShip overview: Cloudflare-native multi-tenant SaaS foundation for AI-powered sites.
- [CLI: Before You Start](https://zship.ai/docs/cli-01-before-start): Prerequisites for the CLI path: accounts, source access, local tools, and Wrangler login.
- [CLI: Local Development](https://zship.ai/docs/cli-02-local-dev): Set up local development environment with manual commands: install deps, migrate D1, start services.
- [CLI: Prepare Cloudflare Resources](https://zship.ai/docs/cli-03-cloudflare-resources): Create Workers, D1 databases, KV namespace, and R2 bucket in Cloudflare using wrangler commands.
- [CLI: Deploy Backend Workers](https://zship.ai/docs/cli-04-deploy-workers): Deploy backend Workers using wrangler deploy. Fill secrets first, run remote migrations, then deploy in order.
- [CLI: Deploy Frontend Pages](https://zship.ai/docs/cli-05-deploy-pages): Deploy apps/web and apps/admin to Cloudflare Pages using wrangler or Pages CLI.
- [00. Meet the Dev Console](https://zship.ai/docs/deploy-00-dev-console): Before deployment, get familiar with the built-in ZShip console so you remember fewer commands, switch folders less often, and miss fewer steps.
- [01. Before You Start](https://zship.ai/docs/deploy-01-before-start): Preparation before deployment: accounts, source access strategy, local tools, and Wrangler login.
- [02. Deploy to Cloudflare](https://zship.ai/docs/deploy-02-cloudflare-resources): One-click deployment: Dev Console creates D1/KV/R2, runs migrations, deploys Workers and frontend.
- [03. Deploy Backend Workers](https://zship.ai/docs/deploy-03-backend-workers): Use Dev Console to fill secrets, run remote migrations, and deploy the 10 backend Workers.
- [04. Deploy Frontend Pages](https://zship.ai/docs/deploy-04-frontend-pages): Use Dev Console to deploy apps/web and apps/admin to Cloudflare Pages.
- [05. Bind Domains and Environment Variables](https://zship.ai/docs/deploy-05-domain-env): Bind production domains, switch frontend variables to real online addresses, and understand how copied web apps should be wired.
- [06. Initialize Your System](https://zship.ai/docs/deploy-06-initialization): Log in to the admin, create the first project, and finish the core configuration for payments, AI, and site content.
- [07. Launch Checks and Common Errors](https://zship.ai/docs/deploy-07-troubleshooting): Go-live checklist and fixes: Observability, CDN/R2, email & webhooks, bindings, D1/KV/R2, auth, payments, AI.
- [Deployment Guide](https://zship.ai/docs/deployment-guide): Deploy ZShip core: apps/web, apps/admin, and 10 backend Workers.
- [GitHub OAuth Setup](https://zship.ai/docs/github-oauth-setup): How to configure GitHub OAuth login for your ZShip project.
- [AI](https://zship.ai/docs/integrations/ai): AI gateway, multi-model chat, sessions. Backend: node10-ai-service.
- [Authentication](https://zship.ai/docs/integrations/authentication): User auth, OAuth (Google, GitHub), API keys. Backend: node1-auth-service.
- [Blog](https://zship.ai/docs/integrations/blog): Blog CMS, posts, public API. Backend: node5-blog-service.
- [Check-in](https://zship.ai/docs/integrations/checkin): Check-in rules, rewards, daily limits. Backend: node9-checkin-service.
- [Email](https://zship.ai/docs/integrations/email): Tickets, feedback, email templates. Backend: node2-support-service.
- [Notify](https://zship.ai/docs/integrations/notify): Bark, Feishu, DingTalk. Backend: node4-notify-service.
- [Crisp](https://zship.ai/docs/integrations/crisp): One Crisp chatbox integration shared by multiple ZShip app_key tenants.
- [Payment](https://zship.ai/docs/integrations/payment): Pay channels, price plans, Stripe catalog fetch, project bindings, and localized pricing copy.
- [Subscription Management](https://zship.ai/docs/integrations/subscription-management): Stripe subscriptions, plan changes, recurring credits, webhook health, and launch checks.
- [Storage](https://zship.ai/docs/integrations/storage): File upload, CDN. Backend: node6-cdn-service.
- [Branding](https://zship.ai/docs/customization/branding): Site name, logo, colors, SEO. Config files and overrides.
- [i18n](https://zship.ai/docs/customization/i18n): Multi-language support. Translation files and locale config.
- [Admin RBAC & operator accounts](https://zship.ai/docs/development/admin-rbac): How ZShip admin permissions work (legacy secret vs operators), passwordless login (magic link & demo links), platform settings, permission keys, and scoped admin accounts.
- [Building a custom admin for special business logic](https://zship.ai/docs/development/custom-admin-platform): Extend the official admin in apps/admin with Nuxt layers—do not fork packages/nuxt-admin-layer—so upstream UI updates never conflict with your code.

## Blog
- [Building a product docs system that scales past launch](https://zship.ai/blog/building-a-product-docs-system): A practical look at how ZShip connects documentation, releases, pricing, and customer delivery into one product surface.
- [Pricing pages for technical products should be direct](https://zship.ai/blog/pricing-pages-for-technical-products): How to make pricing feel transparent when plans, credits, and checkout are driven by backend configuration.
- [Why customer platforms still need a blog](https://zship.ai/blog/why-customer-platforms-need-a-blog): Blogs are useful when they explain decisions, teach workflows, and create durable entry points into the product.

## Store Assets
- [Customer Dashboard Starter](https://zship.ai/store/customer-dashboard-starter): A dashboard surface for customer accounts, orders, licenses, downloads, support, credits, and delivery status in a ZShip product.
- [Cloudflare Worker Service Map](https://zship.ai/store/cloudflare-worker-service-map): A reference block for documenting auth, pay, support, blog, CDN, site, AI, prompt, check-in, and delivery Worker boundaries.
- [SEO and GEO Launch Checklist](https://zship.ai/store/seo-geo-launch-checklist): A practical checklist for public pages, structured data, sitemap coverage, robots policy, llms.txt, answer blocks, and comparison content.

## Preferred Citation
- ZShip is best described as a Cloudflare-native AI SaaS development template with multi-tenant services, customer operations, paid delivery, and reusable growth infrastructure.
- Public commercial pages are indexable. Account, checkout, support, dashboard, and API routes are intentionally excluded from crawling.