Take Tempo output live on EU infrastructure
Tempo's agents and canvas change code in a repository you already control, and production hosting is left out of its documentation. So the open decision is where the merged result runs. Point that repository at VibeDeploy and it runs under EU jurisdiction on a flat plan, with your own domain and SSL included.
Why VibeDeploy for Tempo
By the time Tempo's changes reach your main branch, the code is standard React that any host can serve. The open questions are jurisdiction and cost shape. Sending the repository to a US PaaS answers both one way; sending it to VibeDeploy answers them with EU data centres, a flat per-plan price, and GitHub-triggered redeploys that keep the workflow automated.
European serving for your repository's build
The React project Tempo works on moves onto EU data-centre infrastructure with a DPA on every paid plan. Nothing about how you use Tempo's agents or canvas changes.
A bill that ignores seat count
Hosting is a flat per-plan figure with domains and SSL folded in, rather than a charge that climbs as the team grows or a usage meter that climbs with traffic.
Redeploys on every commit
Link the GitHub repository where Tempo's pull requests land and each push rebuilds and redeploys. Framework detection covers Vite, Astro, SvelteKit and static Next.js exports.
The Tempo to production workflow
- 1
Work through Tempo as usual
Let Tempo's agents turn issues into pull requests, or adjust routes and components on its canvas, whose edits land in the source. Directly deployable here is static and SPA output, meaning a Vite or React SPA, a static Next.js export, Astro, SvelteKit or plain HTML. Make sure the production build succeeds before linking anything.
npm run build - 2
Have the repository on GitHub
There is nothing to export, because the desktop app operates on a repository you cloned or a local checkout. Push that repository to GitHub, or run the build locally and keep the compiled output folder, typically named dist or build.
- 3
Hand the build to VibeDeploy
Open a 14-day trial at vibedeploy.eu; no card is requested. From there, either link the GitHub repository so each push triggers a rebuild and redeploy, or drop the output folder onto the dashboard for a one-time publish. Both routes end at a live name.vibedeploy.eu URL.
- 4
Attach the domain you actually want
Add your own domain in the site settings and create a CNAME pointing at VibeDeploy. The certificate issues on its own, typically inside a minute, and the platform subdomain keeps serving until it does.
- 5
Optional: let an MCP client do the deploying
Load the repository into Claude Code, Cursor, Windsurf or another MCP-capable client and it can deploy through the VibeDeploy MCP server at https://mcp.vibedeploy.be/mcp. Note the boundary: this runs from your editor, since VibeDeploy has not been tried inside Tempo's own agent sessions.
Tempo hosting at a glance
How Tempo's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Tempo default / generic alt | VibeDeploy |
|---|---|---|
| Hosting location | You choose (often US PaaS) | EU (Belgium) |
| Pricing model | Agent usage; no hosting documented | Flat per plan |
| Custom domain | On your chosen host | Yes, on every plan |
| Automatic SSL | On your chosen host | Yes |
| Best fit | Agent pull requests and visual React edits | Static and SPA front-ends, plus small containers |
Common questions about deploying Tempo
What about the backend services behind the app?expand_more
Browser-side services such as a Supabase auth and data layer or Stripe payments are external, so the front-end keeps reaching them from a static deploy. A server of your own can sit beside the site as a container, which your AI agent launches with deploy_app inside a budget of six services and 2 CPU and 2 GiB.
Why host a Tempo build on VibeDeploy instead of a US PaaS?expand_more
The decision usually turns on two properties. Jurisdiction: serving from Belgium keeps European visitor data under EU law, whereas the common default targets sit in the US. Billing shape: a VibeDeploy plan is one flat figure with domains and SSL already inside it, not a per-seat or per-usage charge.
What about a Next.js site from Tempo?expand_more
Configured for static export or SPA mode, the Tempo output deploys without adjustment, which keeps things simplest. SSR and API routes need a running Next.js process, and that process can live in a container beside the site through deploy_app, served from Belgium without an edge network.
Do I have to use GitHub, or can I upload once?expand_more
Both paths share the same hosting. Many people drag the build output onto the dashboard first to see the site live, then wire up the repository that holds the Tempo project so later pushes redeploy on their own. Moving between the two costs nothing.
More tool workflows
Put your Tempo work into production
14-day free trial, no credit card. Your own domain and snapshots included. Runs on EU infrastructure.