Connect · Guide

How to host your Bolt.new app in Canada.

Bolt.new builds and previews an app in the browser. When it’s ready for real users, host it in Canada.

Export the project — download it or push to GitHub — and Canner detects the framework, builds it in a sandbox, and serves it from Montreal over HTTPS.

Bolt.new (from StackBlitz) generates full projects — Vite, Next.js, Node, Astro — right in the browser. That in-browser runtime is great for iterating, but it isn’t where you run production. Because Bolt gives you the real project files, deploying to Canadian-owned hosting takes a couple of minutes.

  1. 1

    Export your project from Bolt

    Use Download to grab the project as a folder, or push it to a GitHub repository from Bolt. Either gives you the real, self-contained source with its package.json and lockfile.

  2. 2

    Build it locally once

    Run npm install && npm run build to confirm it compiles outside the Bolt sandbox. Canner runs the identical build, so a clean local build means a clean deploy. Bind any server to process.env.PORT.

  3. 3

    Send it to Canner

    Create a project, then zip the folder and drag it into the Source panel on the project page, connect the GitHub repo for push-to-deploy, or run canner deploy from the CLI. No config file needed — the framework is detected automatically.

  4. 4

    Wire up data and secrets

    If your app needs a database, provision Canner’s managed Postgres (injected as DATABASE_URL). Add API keys as encrypted environment variables so nothing sensitive ships to the client. `canner db migrate-in` streams straight from a public Postgres (Supabase, Neon, RDS…) with no local file, and a dedicated instance can follow the source live so you can cut over with almost no downtime.

  5. 5

    Ship it

    Canner builds, starts the app under its own Linux user, and issues TLS automatically. Your site is live at your-project.canner.app; add a custom domain whenever you want.

Bolt supports custom MCP connectors. In settings, add a custom MCP server pointing at https://api.canner.ca/mcp and authenticate with an “MCP connector” token from your Canner dashboard (scoped to deploy only). Then ask Bolt to deploy to Canner — it creates the project and ships your code without leaving the editor.

Say this to your agent:

Create a Canner project and save my app to it with the Canner MCP tools, then give me the live URL.
  • Handles whatever Bolt generated — Vite, Next.js, Node, Astro, static.
  • Three ways in: drag-and-drop, GitHub push-to-deploy, or the CLI.
  • Hosted only in Montreal — 100% Canadian-owned, outside the CLOUD Act.
  • Managed Postgres, object storage and cron included, no add-ons.
  • How do I get my code out of Bolt.new?

    Bolt supports downloading the project and pushing to GitHub. Either path gives you the standard source Canner builds from — you’re never locked in.

  • Do Next.js apps from Bolt work on Canner?

    Yes. Canner runs Next.js natively, along with Vite, plain Node, and static sites. The framework is auto-detected at build time.

  • Is my data hosted in Canada?

    Yes — compute and managed Postgres both run in Montreal. Canner has no US affiliate, so your app sits outside US CLOUD Act reach.

  • What does it cost to start?

    Nothing — the Starter tier is free and needs no card. It sleeps when idle; $9/mo Live keeps 2 projects always-on and adds a custom domain.

  • Can I move my existing database with little downtime?

    Yes. `canner db migrate-in` streams straight from any public Postgres server (Supabase, Neon, RDS and others) with no local dump file. For a cutover with almost no downtime, add a dedicated instance ($9/mo per project) and let it follow the source live, then switch DATABASE_URL once it has caught up. After the move you get scheduled encrypted backups on every plan, and point-in-time recovery on the dedicated instance.

Ship it on Canadian soil.

Free Starter tier, no card required. Your app goes live at your-project.canner.app with HTTPS — hosted in Quebec, outside the US CLOUD Act.