Each recipe stands on its own. It says what to run, in what order, and what to check between steps. The recipes assume you have finished the quickstart, so the CLI is installed and signed in, and they link to the guides that go deeper.

Ship something now

MVP demo

An investor wants a link and you have five minutes.

Client delivery

The demo is tomorrow, so deploy tonight. One URL per client, with an expiry.

Hackathon demo

Build it, deploy it, and put a QR code on screen for the audience.

Routine workflows

CI/CD with GitHub Actions

Deploy on every push to main, run a smoke check, and fail the job when it breaks.

Per-PR previews

A channel per PR, the URL posted as a comment, cleanup when the PR closes.

Daily reports

HTML reports built on a cron schedule and served from the same URL.

Monorepo deploys

One repo, many apps, one CI matrix with a leg per app.

Migrations

From Vercel

Move your app and its domain.

From Netlify

The same steps on a different platform. _redirects carries over.

From Replit

$700/mo → $0/mo for hosting a static export.

Patterns

What is vibe hosting?

The deployment side of vibe coding: a live URL with no git, CI/CD, or DevOps.

Deploy from AI canvas

Deploy from inside ChatGPT, Claude, Gemini, v0, or AI Studio.

Full agent workflow

Claude or Cursor builds, deploys, and shares the app.

Share with clients

A private app and a share link with an expiry. Clients don't sign up.

Don't see your scenario?

The CLI accepts --json, and the MCP server exposes the same operations as tools, so you can compose anything these recipes do.

CLI reference lists every command.
Personal access tokens let you drive the same API over HTTP.
Email contact@vibehost.com to request a recipe.

Recipes