Hosting a Bolt project: your real options

Bolt can put your project online itself, and for many people that's fine. Whether it's right for you depends on one question: is this project staying in Bolt forever?

Option 1: Bolt's own hosting

One click inside Bolt, works immediately, no new accounts. Its limits show up later: the setup lives inside Bolt, so the day you continue the project in Cursor or Claude Code (the most common growth path for Bolt projects), your hosting doesn't come with you, and the history of what changed lives in Bolt's chat, nowhere else.

Option 2: GitHub sync + a developer host

Bolt can sync your project to GitHub, and Netlify or Vercel can host from there. Powerful and free to start, but you're now operating three tools built for engineers, and terms like build command, publish directory and environment variables become your problem. Workable if you have a technical friend on call; frustrating if not.

Option 3: a home that outlives the tool

Plyo imports your Bolt project through the same GitHub sync, and from then on treats Bolt as just one of the tools that edits it:

1. In Bolt, turn on GitHub sync (project settings, one minute).
2. In Plyo, choose Import from GitHub and pick the project. Keep building in Bolt; every change syncs onto a timeline automatically.
3. Click Publish. Your own address, a security check before going live, instant rollback, and visitor counts without any setup.

When you eventually add Cursor or Claude Code to the mix, they connect to the same home and the same timeline. Nothing to migrate, ever.

If your project is stuck in Bolt right now

Turn on GitHub sync today even if you decide nothing else. It costs a minute and converts your project from "exists inside one app" to "real files that any tool, host or developer can work with." Every option above, and every future one, starts from there.