Hosting for vibe-coded apps. Deploy what an AI agent builds to a live URL from Claude Code, Cursor, ChatGPT, Gemini, and nine more coding agents. The Free plan costs nothing.

VibeHost is a hosting platform for code that people write partly by hand and partly with an AI agent. The same CLI works whether a human is typing vibehost deploy, any of the nine first-class coding agents (Claude Code, Codex, Cursor, Antigravity, Antigravity CLI, Windsurf, OpenCode, Copilot CLI, Hermes Agent) is shelling out to it, or a chat client like ChatGPT is calling our MCP server.

What VibeHost is

A managed hosting platform that runs your built artifacts behind an HTTPS URL.

Static sites. Any directory with an index.html, served directly from the edge.
Channels, not branches. Preview deploys are named channels (production, dark-mode, pr-42). The server knows nothing about git.

The mental model

flowchart LR
  subgraph You["You / your agent"]
      CLI[CLI]
      Agent[Claude / Cursor]
      SDK[REST / SDK]
  end
  subgraph CP["Control plane"]
      API[api.vibehost.com]
  end
  subgraph Edge["Edge runtime"]
      Router[Tenant router]
      Static[Static assets]
  end
  CLI -- Bearer --> API
  Agent -- OAuth 2.1 / PKCE --> API
  SDK -- PAT --> API
  API -.deploy.-> Router
  Router --> Static
  Static --> User((Visitor))

Three things follow from this picture.

For a static app, your machine builds and our server only receives. No build steps run in the API hot path, where builds have taken hosting platforms down before. The private-beta nextjs and node runtimes build in a separate sandboxed builder.
Every interface goes through the same REST API. The CLI, agents over MCP, and the dashboard all call api.vibehost.com/api/v1 with the same auth checks. The same per-app permissions apply.
Tenant code never shares a process with us. Apps run in isolated edge sandboxes. Static files are served straight from our asset storage, with no app-specific code in the path.

What's different

hammer

No builds in the API

For a static app, npm run build runs on your machine and the server only accepts the artifact. No build steps run in our API hot path.

box

Tarball deploys

The CLI packs your directory into a .tar.gz and POSTs it. Content-addressed blobs mean a repeat upload only sends what changed.

terminal

Machine-readable everywhere

Every CLI command takes --json and emits {ok, data | error} with stable error codes. LLMs branch on code, not message.

key

Agent-first auth

OAuth 2.1 + PKCE for MCP clients, PATs for CI, sessions for browsers. Same per-app grants across all three.

How to drive VibeHost

VibeHost is built around coding agents, the IDE and terminal agents that can call our MCP tools and also run our CLI in scripts. Most people start from one of these.

Nine first-class integrations: Claude Code, Codex CLI, Cursor, Antigravity, Antigravity CLI, Windsurf, OpenCode, Copilot CLI, Hermes Agent. Each one gets every VibeHost tool through our MCP server and can also run vibehost directly in scripts. See MCP server for how that works.

Download and inspect the CLI installer, run it, then use vibehost login and vibehost deploy. This is the headless path. It works from any shell and in scripts, and it is what your coding agent runs under the hood. See the CLI guide.

ChatGPT, Claude Desktop and Gemini Spark have no CLI, so they reach VibeHost only through MCP. You set them up by adding one URL.

The VibeHost Chrome extension adds a Deploy button inside Gemini Canvas, AI Studio, ChatGPT Canvas, Claude Artifacts, and v0.dev, so you can deploy what you just generated without leaving the page. Its popup can also snapshot any webpage.

Call https://api.vibehost.com/api/v1 with a PAT. It is the same backend everything else uses.

When to use VibeHost (and when not)

You want a URL and don't want to think about build infrastructure.
You're shipping AI-generated code and need agents to be able to deploy on your behalf.
You want to share previews per branch/PR/experiment without git hooks.
You need a separate URL per client, customer, or feature.
You're hosting more than a handful of small apps (Vercel and similar platforms price per project; we price per workspace).

You need a long-running stateful backend (databases, queues, persistent WebSockets). Pair VibeHost with a managed database / queue, or use a different platform.
You need server-side cron or arbitrary worker processes. We don't host those.
You need an egress-heavy media platform (video streaming). Our deploy model is artifact-based, not file-server.

Pricing in one paragraph

Free gives you *.vibehost.space URLs with the OG card watermark on. Business is priced per workspace, not per app. It turns the watermark off and adds custom domains, password gates and custom share images. Share links come with both plans. Enterprise is not a third plan but a contract with sales, for SSO, an SLA, dedicated infrastructure or raised caps.

Limit	Free	Business
Price	$0 / month	$20 / month or $199/yr (about $16.58/mo) per workspace
Static apps	100	unlimited
Storage	5 GB	500 GB
Bandwidth	10 GB / month	1 TB / month
Custom domains	0	20
Members	3	unlimited
Workspaces owned	1 free workspace	Any number of Business workspaces
Password protection	No	Yes
Custom share images	No	Yes

Over the storage cap, deploys return 402 until you free up space or upgrade. Usage-based overage billing is not live yet, so going over is never a charge today. Bandwidth is metered and shown on the usage card, but nothing is blocked when you go over it.

Business is priced per workspace, not per account: one subscription licences one workspace, so a second Business workspace is a second $20/month subscription rather than an add-on to the first. Business can also be billed yearly at $199/yr. That is about $16.58/mo, 17% less than twelve monthly payments. The Free plan allows 1 free workspace you own; creating another free one returns 402 PLAN_LIMIT_EXCEEDED. Creating a Business workspace is never refused. Each one starts its own subscription. Downgrading is not retroactive. Workspaces you already own are kept, and only the next one you create is refused.

Full feature matrix on the pricing page.

Next step

If you've never deployed to VibeHost, start with the quickstart. It takes you from installing the CLI to a live URL.

If you're integrating an agent, read MCP for OAuth or personal access tokens for static bearer tokens.

If you're coming from another platform, recipes has migration walkthroughs and common end-to-end scenarios.

Introduction to VibeHost