Deploy Tempo

Deploy Tempo sites with VibeDeploy

Tempo is a visual IDE that writes real React and Next.js code as you design. It is where you build, not where the finished site lives. VibeDeploy takes that exported build to an EU-resident host with a custom domain, automatic SSL, and flat per-plan pricing.

Deploy your Tempo site See pricing

Why VibeDeploy for Tempo

Tempo is a visual React IDE: you design components directly and it writes the corresponding React or Next.js code in real time. It does not run your production site. When the build is ready you export it to GitHub or edit it locally, then you need 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

Tempo produces standard React and Next.js code that most people ship to a US PaaS. VibeDeploy serves the same build 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

Tempo bills per seat for the editor. VibeDeploy hosting 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 exported from Tempo deploy with no extra config.

How to deploy a Tempo site

1
Design and build in Tempo
Use Tempo's visual editor as normal; it writes real React and Next.js code behind the direct-manipulation canvas. VibeDeploy serves static and SPA output: a Vite or React SPA, static Next.js export, Astro, SvelteKit, or plain HTML. When the preview looks right, produce a production build.
```
npm run build
```
2
Get the code out of Tempo
Tempo has native GitHub sync and lets you edit the project locally in VS Code. Either push to a GitHub repository or pull the project down and locate the build output folder (commonly dist or build).
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.vibedeploy.be.
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.vibedeploy.be.
5
Optional: deploy from a Claude or Cursor session
If you open your exported Tempo project in an MCP-capable client such as Claude, Cursor, or Windsurf, that client can deploy through the VibeDeploy MCP server at https://mcp.vibedeploy.be/mcp. This runs from your editor, since Tempo's own IDE does not connect to external MCP servers.

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	Per-seat editor	Flat per plan
Custom domain	On your chosen host	Yes, on every plan
Automatic SSL	On your chosen host	Yes
Best fit	Visual React development	Static / SPA front-ends

Common questions about deploying Tempo

Does VibeDeploy run the Supabase or Stripe backend Tempo wired up?expand_more

VibeDeploy serves the static or SPA front-end. Tempo integrates Supabase for auth and data and Stripe for payments, and those are external services your front-end calls from the browser, so they keep working from a static site. What VibeDeploy does not run is an always-on Node or SSR server of your own; for that part use a server host.

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. Server-side rendering and API routes need the Next.js server running, which is not part of VibeDeploy's static-edge model. For SSR-heavy Next.js use a server host; for static-export Next.js, just deploy the output.

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 repo Tempo syncs to later so every push rebuilds and redeploys. Same hosting either way.