Deployment
Deploy the TanStack Start beta on Cloudflare Workers, or inspect the existing Vercel and self-hosted recipes.
Hosted deployment status
The TanStack Start beta includes a Cloudflare Workers build. Follow the Cloudflare deployment guide for the supported command sequence and checks against your own deployed app. The existing Vercel build remains available, but its hosted behavior is not qualified by the Cloudflare checks. Next.js guides apply to Next.js only.
Deploy the standalone app
The Cloudflare path is one TanStack Start Worker with Supabase Auth and Postgres plus your selected Stripe or Polar billing. Start here after the template runs locally. Docker and VPS deployment remain available when you want to own more infrastructure.
Cloudflare Workers
Build for Workers, configure your providers and verify the hosted app.
Vercel
Deploy to Vercel and configure its provider settings.
Docker
Build and run the application as a container.
VPS
Operate the application, proxy, TLS, and updates on your own server.
Before you deploy
- Finish Getting Started and confirm the app runs locally.
- Review Configuration so browser-safe and server-only values stay separate.
- Prepare hosted Supabase, Vercel, and Stripe access for the provider steps you intend to enable.
- Keep Stripe in test mode until checkout, webhook delivery, persisted access, and the hosted URL work together.
Existing Vercel recipe
- Create or link the hosted Supabase project and apply the included migrations.
- Save the deployed Site URL and Redirect URLs in Supabase Auth configuration.
- Link the Vercel project and add the reviewed Production environment values with Vercel CLI or Dashboard.
- Configure the Stripe test catalog and webhook endpoint used by the deployed app.
- Deploy the app and verify the exact production URL before switching provider state to live mode.
Use Hosted Environment Variables for the shared Preview/Production block and each setting's requirements.
Follow the complete Vercel deployment guide for the commands, provider checkpoints, and hosted verification path.
Runtime ownership
| Surface | Default owner |
|---|---|
| TanStack Start pages, embedded Hono API, and server services | Cloudflare Worker or selected app host |
| Authentication and Postgres | Supabase project |
| Checkout, customer portal, and billing events | Stripe account |
| Provider projects, environment values, and deployment | Provider CLI or Dashboard |
| App database checks and hosted proof | Template-local ./coremvp CLI |
Advanced self-hosting
Choose Docker or VPS when you want direct control over the application runtime. Those paths require you to own container operation, networking, TLS, updates, monitoring, and recovery.
Was this page helpful?