Frontend
Pages, interface, static assets, and fast request handlers close to users.
- Good homes
- Cloudflare Pages · Vercel · Netlify
- Keep out
- Secrets · long jobs · state
Do not move the whole prototype into one mystery box. Split it into a fast frontend, a backend for secrets and slow work, and persistent data.
Map my app →Most generated apps become easier to host once the code is separated by what it actually does.
Pages, interface, static assets, and fast request handlers close to users.
Authentication, model calls, webhooks, queues, cron, agents, and slow work.
Users, app state, files, embeddings, queues, and the information that must survive deploys.
Migration is not a badge of seriousness. Keep the builder when it works; export only when a concrete limit justifies the operational load.
Use the included hosting and database for validation.
Best while:the limits are not hurting youOwn the domain and web deployment; keep managed services.
Best when:you need portability or custom CIOperate web, workers, state, monitoring, and recovery.
Best when:the product can pay for operationsGenerated code can look complete while the production behavior remains untested.
Detailed platform limits, comparisons, migration instructions, and backend patterns live here when you need the evidence behind the map.