For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/web/deployment.md (or send Accept: text/markdown).
Deployment checklist
Prepare the production dependencies and verify the flow you intend to ship.
Prepare a public app in this order
Deployment means running your app on a hosting service so other people can visit it. localhost is accessible only in your development environment. First finish real database-backed sign-in locally, choose a hosting guide below, create a separate test database, and configure the host's environment settings with the actual public HTTPS app URL. Keep local demonstration settings separate from the public app.
In a second terminal at the repository root, run the Web checks below. A successful build creates a production version on your computer; it does not upload or publish it. Do not confuse corepack pnpm --filter @supastack/web start with deployment: start runs the previously built version locally. Run it only after stopping the development server on port 3000.
Follow the chosen host's guide for migration, environment and launch steps. Test sign-up, an email code, saved account data after a restart and a paid feature in the provider's sandbox before opening sales. A mobile or desktop client must point to this running HTTPS backend. Releasing a native app is a separate step documented in its platform's distribution guide.
corepack pnpm --filter @supastack/web typecheck
corepack pnpm --filter @supastack/web buildPrepare the services
Create the Postgres database, apply the repository's migrations and enter your public app URL and authentication settings in the hosting dashboard. Choose one supported Web billing provider and one transactional email provider for the features you enable. Configure Trigger.dev when your product uses its background workflows; you do not need every integration to publish a basic app.
Configure the immutable model/price catalog and workspace AI policy before accepting production AI tasks. An empty alias policy should leave those choices unavailable.
Build and deploy the web application
Run the Web commands below from the repository root and resolve any error before continuing. typecheck checks the types, test runs the Web tests, and build creates production files locally. Follow your selected hosting guide to upload and run them with its server-side environment settings. These commands do not deploy the app.
corepack pnpm --filter @supastack/web typecheck
corepack pnpm --filter @supastack/web test
corepack pnpm --filter @supastack/web buildVerify the deployed boundaries
Verify sign-in and persistence against the deployed database; test workspace isolation; confirm Stripe sandbox webhook processing and entitlement changes; and run a background task through result persistence and transactional delivery.
Read docs/real-provider-smoke.md and docs/production-ai-runtime.md in the repository for the explicit provider acceptance process. A successful build or intercepted browser test does not establish these external outcomes.