Skip to main content
← Tutorial Hub

DEPLOY

Step 3 of 3

Deploy — a rocket on a launchpad with deploy target indicators

Target acquired. I deploy to all six. Tell me which one and I'll handle the rest — provisioning, DNS, SSL, monitoring, backups. You just need to set the deploy target in your PRD frontmatter.

Kusanagi avatarKusanagi

SERVER PREREQUISITES

Deploying to a fresh Linux server (VPS, EC2, DigitalOcean)? Install Node 20 and Git before creating your VoidForge project:

# Install Node 20 via NodeSource
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs git
# Create your project
npx thevoidforge init my-project

For full platform-specific instructions (including libnode-dev conflicts on Ubuntu), see the Install tutorial. If you're running the wizard on a remote server, see Remote & LAN Access for SSH tunnel, --lan, and --remote options.

6 DEPLOY TARGETS

VPS

Full control with SSH provisioning

Vercel

Zero-config for Next.js, edge CDN

Railway

Simple container deploy with managed DB

Cloudflare

Workers + Pages on the edge

Docker

Containerized deploy anywhere

Static

HTML export, serve from any CDN

HOW IT WORKS

Set your deploy target in the PRD frontmatter:

deploy: "vercel"

When the build reaches Phase 12, Kusanagi takes over. She reads the DevOps methodology, runs the pre-flight checklist, and executes the full deployment sequence for your target.

The Haku wizard handles provisioning interactively. If you prefer manual control, configure deployment following Kusanagi's instructions in the build log.

You can also deploy anytime with the standalone deploy command:

/deploy

Kusanagi auto-detects your target, runs pre-deploy checks (build, tests, clean tree, credentials), executes the deploy, and verifies health. If the health check fails, she rolls back automatically. Use /deploy --dry-run to preview without deploying.

HEALTH CHECK

After deploy, Phase 13 runs the launch checklist: SSL verified, security headers checked, monitoring active, backups tested, all flows verified in production. Only then does the build state update to LAUNCHED.

WHAT'S NEXT

Your app is live. Run the Gauntlet for a full-spectrum review before real traffic hits. Then set up the growth engine to drive users to your deployed product.