# Introduction URL: https://ship-and-scale.vercel.app/docs Your starting point for a production-ready SaaS. Ship & Scale is a Next.js SaaS starter with Auth, workspaces, subscriptions and a customizable interface already connected. Start with the infrastructure your product needs and focus on what makes it worth using. You get the source code and run it on your own provider accounts. Kickstart handles the initial service setup. The example app is called **Forma**; replace its brand and features with your own. [Start with Tech stack](/docs/build/codebase), then follow Setup → Accounts → Configuration → Kickstart. ## Who it's for [#who-its-for] * Founders building their first SaaS with a coding agent or developer. * AI builders who want an established architecture and documentation their agent can use. * Indie hackers launching multiple products without rebuilding the same infrastructure. ## How Kickstart works [#how-kickstart-works] Three credentials connect your project to Supabase, Stripe and Resend. Kickstart checks access, then creates the services behind your app. ### Add your credentials [#add-your-credentials] After cloning and installing the starter, add `SUPABASE_ACCESS_TOKEN`, `STRIPE_TEST_SECRET_KEY` and `RESEND_API_KEY` to your local `.env`. Accounts and Configuration cover the required permissions. Keep secret values out of chats and source control. ### Check access and provision [#check-access-and-provision] `npm run kickstart:check` runs read-only checks. Then `npm run kickstart` creates your hosted Supabase project with its schema, permissions, Auth, storage and functions. It publishes five Resend email templates, configures Stripe test products, prices, webhooks and the billing portal, and saves generated settings to `.env`. ### Run your app [#run-your-app] Run `npm run dev` and test signup, email and billing. Next.js runs locally against your hosted services. The [Kickstart guide](/docs/start/project-kickstart) covers checks and recovery; [deployment](/docs/start/deployment-kickstart) follows with GitHub, Vercel and production credentials. **Before launch** The providers' free plans cover building and launching; upgrade Vercel to Pro before you take payments. Customize the product, review content and permissions, and test customer flows using the [production launch checklist](/docs/operations/launch). ## Build with your agent [#build-with-your-agent] [Download the docs (.md)](/ship-and-scale-docs.md) and give your agent access to your repository. Use this prompt to build context for future features. [Agent-Friendly Docs](/docs/agent-friendly-docs) explains how the manual and `AGENTS.md` work together. **Example agent prompt** ```text title="Prompt for your coding agent" Read ship-and-scale-docs.md and follow the repository's AGENTS.md, including relevant nested instructions. Inspect the code to understand the architecture, existing features and conventions. Use this context for the features I ask you to build. Read the relevant guides and code, reuse existing patterns, and flag conflicts or missing decisions before editing. Preserve workspace isolation, permissions and secret handling. Implement each requested feature, run relevant checks, and report anything unverified. Start with a brief summary of how the app fits together, then wait for my first feature request. ``` ## What's in the starter [#whats-in-the-starter] Each card links to a detailed guide. [Auth](/docs/core/authentication) Email/password, magic links, recovery and configurable verification. Google sign-in is available once you connect your OAuth app. [Workspaces](/docs/core/workspaces) Workspace invitations, switching and Owner, Admin and Member roles. Server checks and database policies keep workspace data isolated. [Subscriptions](/docs/billing/subscriptions) Stripe Checkout, recurring plans and a billing portal. Each workspace has its own subscription, with webhooks syncing billing state. [Customer dashboard](/docs/core/onboarding-settings) A protected app shell with onboarding, profile settings and workspace controls. Reuse its layout and components for your product. [Admin panel](/docs/operations/maintenance#admin-panel) Read-only customer visibility and operator-access management. Access is separate from workspace roles; workspace admins don't automatically get access. [Storage](/docs/storage/overview) Private avatars in Supabase Storage and database-backed workspace logos, with upload validation and access policies. [Emails](/docs/email/templates-delivery) Five Resend templates: welcome, verification, password reset, magic-link sign-in and workspace invitations. Edit the source and publish through Kickstart. [In-app notifications](/docs/core/notifications-feedback) A private inbox with read/unread controls and preferences. Extend the welcome notification example with your own product events. [Customer feedback](/docs/core/notifications-feedback) A shared feature-request board with voting, plus private bug reports. Reports and voter identities stay private. [Marketing site](/docs/website/pages-blog) Landing, pricing, FAQ and contact pages, plus sample legal content. Replace the example brand and copy before launch. [Blog](/docs/website/pages-blog) Public posts backed by published content in Supabase. Add your own articles and authors; a general-purpose CMS editor isn't included. [Product documentation](/docs/website/documentation) Fumadocs pages, search and navigation for your customers. This is separate from the Ship & Scale manual you're reading now. [SEO](/docs/website/seo-metadata) Metadata, canonical URLs, social previews and sitemap controls. Configure your production domain and review launch settings before enabling indexing. [REST API](/docs/integrations/api) Workspace API keys and permission-checked endpoints to read and rename a workspace. Extend these patterns for your own resources. [MCP](/docs/integrations/mcp) OAuth and scoped tools to read and rename a workspace through MCP clients. Add tools for your product's actions. [AI chat · optional](/docs/integrations/ai) OpenRouter streaming chat, saved conversations and workspace credit checks. Supply a funded provider account, or remove AI while keeping the core SaaS features. ## Your member dashboard [#your-member-dashboard] Your Ship & Scale member area contains the Starter kit, Documentation, Founder playbook and Discord community. It's separate from the customer dashboard in your app. Open **Starter kit** to connect GitHub and get access to the starter. [Setup](/docs/start/environment) walks through each step. Ship & Scale member dashboard with separate cards for Starter kit, Documentation, Founder playbook and Discord community. ## Start here [#start-here] Continue through **Tech stack → Setup → Accounts → Configuration → Kickstart** to get your local app running. [Troubleshooting](/docs/operations/troubleshooting) is available along the way. [Next: Tech stack](/docs/build/codebase) Review the stack and architecture before setting up your project.