Product Plate landing page and live product workbench

Product Plate

SvelteKit starter, ready to become your product.

Auth, billing, realtime data, AI, product UI, tests, and deployment, plus a practical prompt that helps your coding agent turn the starter into a focused product.

Live demo · Create tutorial · Discussions · MIT license

```sh bun create product-plate my-app ``` ## Why this exists Most starters save setup time, then leave you with a showcase app to dismantle. Product Plate gives you two paths: - `bun create product-plate` generates a lean app from one fixed product profile. - This repository remains the maintained full demo and integration source for contributors and founders who want to inspect every pattern. Generated apps contain the selected product routes, backend modules, dependencies, environment contract, tests, and navigation. The empty blog remains an explicit publish-or-remove launch decision in the generated guide. The generated `product-plate.json` records the profile and capabilities for launch checks and safe infrastructure upgrades. | Profile | Product shape | | ----------- | ---------------------------------------------------------------------------------------------------------------------- | | `prelaunch` | Landing page, real waitlist, SEO, legal placeholders, email, and Convex. | | `solo-saas` | Personal SaaS with auth, onboarding, billing, settings, support, and operator users. | | `team-saas` | Solo SaaS plus visible organizations, roles, members, invites, notifications, audit history, and organization billing. | | `ai-saas` | Solo SaaS plus AI chat, model configuration, rate limits, usage, entitlements, and usage-aware billing. | ## See the product The hosted demo creates a fresh disposable account and opens the authenticated app: - [Open the live demo](https://productplate.pages.dev/auth/demo)

Product Plate dashboard

Product Plate onboarding Product Plate editor

Product Plate workflow editor Product Plate map workspace

Product Plate 3D workspace Product Plate AI assistant

## What is included - **App:** SvelteKit 2, Svelte 5, TypeScript, Tailwind CSS v4, shadcn-svelte. - **Backend:** Convex functions, realtime data, storage, organizations, notifications, API keys, and generated types. - **Accounts:** Better Auth, email/password, Google OAuth wiring, reset flows, onboarding, profiles, protected routes, and admin roles. - **Billing:** Autumn checkout, subscription state, and customer portal patterns. - **AI:** Vercel AI SDK route, streaming assistant UI, Markdown, suggestions, and tool calls. - **Product UI:** dashboard, profile/settings, workspace invites, developer API keys, admin, editor, graph, map, 3D, uploads. - **Public UI:** landing page, docs, blog, changelog, legal templates, component gallery, and theme builder. - **Delivery:** Bun, Vitest, Playwright, opt-in PWA support, request IDs, security headers, GitHub Actions, Cloudflare Pages. ## Start here ```sh bun create product-plate my-app cd my-app bun convex dev bun run dev ``` The interactive command asks for a profile, product identity, and theme. CI and scripted creation can be explicit: ```sh bun create product-plate my-app \ --profile solo-saas \ --name "My Product" \ --description "Short product description" \ --theme neutral \ --yes ``` Run `bun run doctor` while configuring providers and `bun run verify:launch` before production. The normal path needs Bun only; Devenv remains optional. See [the create-to-production tutorial](./docs/tutorial.md) for product kickstart, preview deployment, and production setup. ### Inspect or contribute to the full demo Clone this repository only when you want every maintained integration and showcase or intend to contribute: ```sh git clone https://github.com/rodrgds/productplate.git cd productplate bun install --frozen-lockfile bun convex dev bun run dev ``` [`START_HERE.md`](./START_HERE.md) remains the guided product-kickstart prompt for direct full-demo forks. Generated apps receive a shorter profile-specific version. ### Optional reproducible environment Product Plate uses Bun 1.3.13 from its pinned nixpkgs in devenv. With direnv installed, allow the environment once, then run the named commands directly: ```sh direnv allow setup convex-dev dev ``` Without direnv, enter the same pinned environment for each command: ```sh devenv shell -- setup devenv shell -- convex-dev devenv shell -- dev ``` `setup` performs a frozen install and creates `.env.local` from `.env.example` only when `.env.local` is missing. It never overwrites existing local configuration. The install is staged beside the repository and moves `node_modules` into the project, keeping dependency state on the durable `/workspace` filesystem rather than `/tmp`. Open `http://localhost:5173`. For local auth, set the same URL in Convex: ```sh bun convex env set SITE_URL http://localhost:5173 ``` ## Environment Minimum local variables: ```env CONVEX_DEPLOYMENT= PUBLIC_CONVEX_URL= PUBLIC_CONVEX_SITE_URL= SITE_URL=http://localhost:5173 BETTER_AUTH_URL=http://localhost:5173 BETTER_AUTH_SECRET= ``` Optional integrations: ```env GOOGLE_CLIENT_ID= GOOGLE_CLIENT_SECRET= RESEND_API_KEY= OPENROUTER_API_KEY= CHAT_MODEL=openrouter/free AUTUMN_SECRET_KEY= ENABLE_PWA=false ``` PWA generation is off by default. Set `ENABLE_PWA=true` only after choosing a cache policy for your product; the starter's opt-in worker caches install assets and public marketing images, not authenticated pages or API responses. Use [`.env.example`](./.env.example) for local configuration and [`.env.server.example`](./.env.server.example) for production-only secrets. The devenv Bun wrapper asks Node to parse `.env` and `.env.local` as data, then invokes the pinned Bun binary with `--no-env-file`. Dotenv files are never sourced or evaluated as shell code, and their contents are not embedded in the Nix store. Raw Bun setup also uses `--no-env-file` in a clean environment. ## Commands Run these names directly inside direnv or as `devenv shell -- ` outside it. No Git hook rewrites or stages files; run `verify` explicitly before handoff or commit. Use `verify-full` on a release-capable machine when the resource-heavy production build is required. For generator work, `bun run verify:profiles` checks all four generated profiles sequentially. Pass profile names after `--` to narrow the run, such as `bun run verify:profiles -- solo-saas`. | Command | Purpose | | ----------------- | ---------------------------------------------- | | `install` | Install exactly from `bun.lock` | | `setup` | Frozen install; create `.env.local` if missing | | `dev` | Start SvelteKit | | `convex-dev` | Start Convex | | `check` | Typecheck Svelte and TypeScript | | `format-check` | Check formatting with oxfmt | | `lint` | Check formatting, then lint with oxlint | | `test-unit` | Run Vitest | | `test:e2e` | Run Playwright | | `build` | Build for production | | `verify` | Run lint, checks, and unit tests | | `verify-full` | Run `verify`, audit dependencies, then build | | `verify-profiles` | Generate and verify every release profile | ## Project map ```text src/routes/ Public, auth, API, and product routes src/routes/(app)/ Authenticated app shell and product examples src/routes/docs/ Public setup and architecture docs page src/routes/theme-builder/ Theme-token builder for kickstart styling src/lib/components/ui/ shadcn-svelte primitives src/lib/components/ai/ Streaming assistant and tool components src/lib/components/landing/ Reusable marketing component gallery static/screenshots/ Product screenshots used by the site and README src/hooks.server.ts Request IDs, security headers, optional request logs src/convex/ Schema, auth, billing, orgs, developer APIs, storage, crons _template_options/ Inactive provider, database, and marketing scaffolds docs/ Integration, theme, template-option, observability/security guidance ``` ## Deployment Direct full-demo forks of this repository use the checked-in Convex and Cloudflare Pages workflow. Pull requests use `CONVEX_PREVIEW_DEPLOY_KEY` to create an isolated branch deployment. `main` uses `CONVEX_PRODUCTION_DEPLOY_KEY`, builds through `bun convex deploy --cmd`, activates the backward-compatible backend, uploads the exact Cloudflare artifact, and then runs a smoke test against the public URL. Configure Cloudflare credentials, `CLOUDFLARE_PROJECT_NAME`, the final `SITE_URL`, and provider secrets in the GitHub environment. The workflow summary records the frontend URL, Convex target, Git SHA, smoke status, and rollback instruction. Preview and production deploy keys must never be the same. CLI-generated apps instead use one environment-scoped `CONVEX_DEPLOY_KEY`, a separate Pages project for preview and production, an explicit transactional email sender, runtime provisioning, and deployed readiness checks. Follow [the generated-app deployment guide](./docs/tutorial.md#4-open-a-preview). ## License MIT. Use it for personal, commercial, closed-source, or open-source products.