Deploy Tempo

Deploy Tempo sites with VibeDeploy

Tempo turns issues and feedback into reviewed pull requests on your own repository, with Claude or Codex doing the work and a canvas that edits real React components. It is where the code changes, not where the finished site lives. VibeDeploy builds that repository and serves it from an EU-resident host with a custom domain, automatic SSL, and flat per-plan pricing.

Why VibeDeploy for Tempo

Tempo works on a repository you already own: its agents run Claude or Codex sessions, each in its own git worktree, and hand back pull requests, while its canvas shows real routes and React components and writes edits back to the source. Its documentation covers previews and share links, not production hosting, so once a pull request is merged the site still needs a deploy target. VibeDeploy is that target, serving your front-end from the EU on a flat plan with your own domain.

public

EU hosting for a Tempo build

The code Tempo's agents change lives in your own repository, so any host can serve the build. VibeDeploy serves it from a Belgian data centre, so your site and your visitors' data stay in the EU. A DPA is available on every paid plan.

shield_lock

Flat pricing, no per-seat fees

Whatever you spend on Tempo's agents, hosting is a separate line. VibeDeploy is one flat price per plan with custom domains and automatic SSL included, so what you pay to serve the site does not move with your team size or your traffic.

settings_suggest

Framework detection

Vite, static Next.js export, Astro, SvelteKit, plain HTML. VibeDeploy detects the build command and output directory, so most React front-ends that Tempo works on deploy with no extra config.

How to deploy a Tempo site

  1. 1

    Let Tempo change the code

    Work in Tempo as usual: its agents open pull requests on your repository, and canvas edits write back to the source. VibeDeploy serves static and SPA output directly: a Vite or React SPA, static Next.js export, Astro, SvelteKit, or plain HTML. Before you connect anything, check that the production build runs.

    npm run build
  2. 2

    Put the repository on GitHub

    Tempo's desktop app works on a Git repository, added by its clone URL or as a local folder, so the code is already yours. Push it to GitHub if it is not there yet, or build it locally and locate the output folder (commonly dist or build).

  3. 3

    Connect to VibeDeploy

    Start a 14-day free trial at vibedeploy.be (no credit card). Then connect your GitHub repo so every push builds and redeploys automatically, or drag the build output folder into the dashboard for a one-off deploy. Either way you get a live URL at name.subsite.site.

  4. 4

    Add your custom domain

    In site settings, add your domain and point a CNAME at VibeDeploy. SSL provisions automatically, usually within 60 seconds. Until then the site stays live at name.subsite.site.

  5. 5

    Optional: deploy from a Claude or Cursor session

    If you open the same repository in an MCP-capable client such as Claude Code, Cursor, or Windsurf, that client can deploy through the VibeDeploy MCP server at https://mcp.vibedeploy.be/mcp. We have not tested VibeDeploy's server inside Tempo's own agents, so this step runs from your editor.

Tempo hosting at a glance

How Tempo's default hosting and a generic alternative compare to VibeDeploy.

FeatureTempo default / generic altVibeDeploy
Hosting locationYou choose (often US PaaS)EU (Belgium)
Pricing modelAgent usage; no hosting documentedFlat per plan
Custom domainOn your chosen hostYes, on every plan
Automatic SSLOn your chosen hostYes
Best fitAgent pull requests and visual React editsStatic and SPA front-ends, plus small containers

Common questions about deploying Tempo

Does VibeDeploy run the backend services the app uses?expand_more

VibeDeploy serves the static or SPA front-end. Services the front-end calls from the browser, such as Supabase for auth and data or Stripe for payments, keep working from a static site. If you also need a Node or SSR server of your own, it can run as a container next to the site (up to 6 services with 2 CPU and 2 GiB in total), deployed by your AI through the MCP tool deploy_app.

Why host a Tempo build on VibeDeploy instead of a US PaaS?expand_more

Two common reasons. Hosting location: VibeDeploy serves from Belgium, which matters for GDPR and European visitors, while most default targets are US-based. Cost shape: VibeDeploy is a flat per-plan price with custom domains and SSL included, rather than per-seat or usage-metered hosting.

What about a Next.js site from Tempo?expand_more

Static export and SPA-mode Next.js work out of the box and are the simplest route. Server-side rendering and API routes need the Next.js server running; it can run as a container next to the site via deploy_app, in one region in Belgium with no global edge.

Do I have to use GitHub, or can I upload once?expand_more

Either. You can drag the build output into the dashboard for a quick one-off, then connect the GitHub repository Tempo works on so every push rebuilds and redeploys. Same hosting either way.

Related deploy guides

Ship your Tempo project today

14-day free trial, no credit card. Your own domain with automatic SSL. Hosted in Belgium.