turbo-vibe is a Node.js CLI that, given a YAML file describing your architecture, gives your app staging and production in your own Cloudflare, Vercel, Supabase and WorkOS accounts — in minutes if your accounts are ready.

The problem

Going live means environments, databases, previews, secrets, DNS and rollbacks, and since I kept rebuilding the same pipelines on every project (and I’m lazy), I packed it all into a CLI. Full story in Building turbo-vibe.

How it works

npx @turbo-vibe/cli init    # describe your app and connect your accounts
git push origin main          # every merge deploys to staging and is smoke-tested

Every merge is built once, deployed and smoke-tested on staging, and then the same build is promoted to production once a person approves it.

What you get

• Secrets that never touch the disk or the logs
• Migrations before the new code goes live
• No deletions without --allow-deletions
• A preview environment per pull request
• No real lock-in: everything lives in your accounts

Ship it with your agent

npx @turbo-vibe/cli adopt generates skills that teach Claude Code or Cursor how to make your project deployable, while secrets and the production deploy stay with you.

Stack and status

TypeScript on Node 24, OpenTofu and GitHub Actions, with Vercel targets in beta and a weekly live run recorded in COMPATIBILITY.md. MIT-licensed and available on npm.