H3. Managed hosting path
What this page helps you do
Use a managed hosting service as the easiest default path.
Why it matters
Managed hosting removes a lot of server setup work, which lets you focus on the app itself.
You should already have
- an app that runs locally
Skip this page if
- you already chose a VPS or self-hosted platform path
What to do
- connect your GitHub repo to the hosting provider
- set the build and start commands
- add environment settings
- deploy a first working version
Recommended default
Use managed hosting unless you clearly need lower-level server control.
Common mistakes
- forgetting environment settings during the first deploy
- assuming persistent storage exists when it does not
- not checking background-job support
Next step
Go to H6. Deploy your app.
Related pages
Advanced notes
TODO for contributors: add a plain-English comparison table for common managed hosting providers.