Prompt. Deploy. Ship.

Turn one prompt into
a live app URL.

Tell your AI what to ship, let it call deployment tools, and get a secure live URL fast. Prefer direct control? Run the same flow from your terminal.

$ curl -fsSL https://vibekoded.app/install.sh | bash

Install vk CLI Read llms.txt

Built for production-minded teams: HTTPS by default • Isolated runtimes • Managed TLS + routing

Watch the handoff from CLI to MCP

First deploy directly from the terminal, then let your AI continue with MCP tools on the same platform.

vk-cli-deploy

$vk login --email [email protected]

✓authenticated

$vk app ship portfolio

→ building image registry.vibekoded.app/user-a3f9/portfolio:latest

✓registry auth + image pushed

→ provisioning deployment + service + ingress

$vk app status portfolio

✓deployment ready

→ https://portfolio-a3f9.apps.vibekoded.app

cli deploy live at https://portfolio-a3f9.apps.vibekoded.app

mcp-agent-deploy

# User: "Now let the AI roll out checkout improvements"

# AI: fetching https://vibekoded.app/llms.txt

$vk mcp create vscode

✓MCP server added: vibekoded

tool: create_deployment(name=portfolio, image=registry.vibekoded.app/...)

tool: get_dns(name=portfolio)

✓AI-driven deploy completed

→ https://portfolio-a3f9.apps.vibekoded.app

mcp deploy live at https://portfolio-a3f9.apps.vibekoded.app

Simple by design

Four steps from idea to production URL

Every customer flow follows the same path: install once, ship quickly, and keep control as your app grows.

Install and authenticate

Install vk, create your account, and sign in. You are ready to deploy from CLI or AI-assisted MCP from day one.

Ship your first app

Run vk app ship myapp and vibekoded handles build, registry auth, push, and deploy without extra infrastructure setup.

Connect your AI client

Run vk mcp create vscode (or another supported client) so your AI can call deploy and DNS tools using canonical instructions from /llms.txt.

Scale with Pro controls

Upgrade with vk account pro for higher limits, permanent deployments, and app-level vk app auto-redeploy enable myapp automation.

“We moved from scattered scripts to one deploy flow. Our first customer-facing app was live in under an hour and updates are now predictable.”

Ari S. Founder, SaaS startup

“Our team ships from terminal and AI chat with the same platform. Onboarding new engineers got dramatically faster.”

Mika T. Engineering lead

“The MCP flow is clear and deterministic. We can prompt our AI to deploy, then verify status and URL in the same workflow.”

Rene K. Product engineer

What you get

Everything you need to ship and operate

Built for teams that want speed without sacrificing control, reliability, or secure defaults.

CLI

One-command deploy

Go from source to live URL in one flow with vk app ship.

MCP

AI-native tooling

Your assistant can call deploy, list, and DNS tools through MCP with deterministic setup paths.

URL

Predictable live endpoints

Every app gets a public URL under apps.vibekoded.app with routing handled for you.

TLS

Secure defaults

HTTPS, runtime isolation, and managed transport security are built in from the first deploy.

AUTO

Auto-redeploy controls

Supported Pro apps can opt into digest-aware rollouts after registry pushes with vk app auto-redeploy.

FLOW

CLI and AI together

Start by hand in terminal, then let your assistant continue from the same deployment state.

SCALE

Built for growth

Move from free experiments to Pro production workloads without changing your workflow.

SETUP

Fast onboarding

Install once, authenticate, and deploy in minutes without maintaining bespoke pipelines.

Plans

Start free. Upgrade when your workload grows.

The full deployment workflow is available on day one. Pro unlocks higher limits and long-running automation.

Free

Default

Best for testing ideas, validating deploy flows, and shipping your first customer demo.

Deploy one app at a time
Time-limited app lifetime to keep preview environments clean
Use the full CLI and MCP onboarding flow
Great for testing builds, URLs, and AI-assisted deployment loops

Pro

Upgrade with vk account pro

For production apps that need more headroom, persistent deployments, and automated updates.

Higher app limits for active projects
Permanent deployments instead of short-lived previews
App-level auto-redeploy controls through vk app auto-redeploy
Built for CI-style image pushes and predictable repeat deploys

Upgrade from the terminal with vk account pro. After your first deploy, supported Pro apps can enable automatic rollouts with vk app auto-redeploy enable myapp.

Model Context Protocol

Let your LLM deploy for you

vibekoded exposes a fully-compliant MCP server so your AI assistant — Cursor, Claude, or any MCP-compatible client — can discover, deploy, and manage your apps without leaving the chat.

After logging in, run vk mcp create vscode or another supported client target. For unsupported tools, use vk mcp show-config. Once connected, your model gains native deploy tools: deploy, list_deployments, get_dns, and more.

If you prefer a hybrid workflow, ship the first deploy from the CLI, then let your editor or agent take over. Pro users can keep that loop running with vk app auto-redeploy enable myapp on supported apps.

vk mcp create vscode

json

# Preferred
$ vk mcp create vscode

# Manual fallback
$ code --add-mcp '{
  "name": "vibekoded",
  "url": "https://mcp.vibekoded.app/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN"
  }
}'

# VS Code confirms:
Added MCP servers: vibekoded

Use vk mcp create vscode for the clean path. The manual command is still available when needed.

# Preferred
$ vk mcp create codex

# Manual fallback
$ codex mcp add vibekoded -- \
    npx -y mcp-remote \
  https://mcp.vibekoded.app/mcp \
    --header "Authorization: Bearer YOUR_TOKEN"

# Or natively in ~/.codex/config.toml:
[mcp_servers.vibekoded]
url = "https://mcp.vibekoded.app/mcp"
http_headers = { "Authorization" = "Bearer YOUR_TOKEN" }

Use vk mcp create codex when Codex CLI is installed. The TOML approach remains the manual fallback.

# Preferred
$ vk mcp create claudecode

# Manual fallback
$ claude mcp add vibekoded \
  https://mcp.vibekoded.app/mcp \
    --header "Authorization: Bearer YOUR_TOKEN"

# Verify
$ claude mcp list

Use vk mcp create claudecode when Claude Code is installed. The manual command remains available when needed.

{
  "mcpServers": {
    "vibekoded": {
      "url": "https://mcp.vibekoded.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Use vk mcp create cursor when Cursor is installed. The JSON block is the manual fallback.

Turn one prompt intoa live app URL.