Overview & Installation
The deplo CLI brings the entire dashboard deploy loop to your terminal: sign in, connect your providers once, then run one command inside any repository to get live production URLs — frontend in your Vercel account, backend in your Render workspace.
The CLI is a thin, honest client for the same REST API the dashboard uses. Nothing builds on your machine — deplo detects the repository from your git remote, asks the platform to deploy it, and streams the live log (including env-variable prompts and the AI failure diagnosis) back to your terminal.
Install#
The package is @deplo.ai/cli and the binary it installs is deplo. Run it one-off with npx, or install globally:
npx @deplo.ai/cli login
npx @deplo.ai/clinpm i -g @deplo.ai/cli
deplo login
deplonpx @deplo.ai/cli — the bare deplo package on npm is a different, unrelated package. Once installed globally, the command itself is deplo.Requirements#
- Node.js 20 or newer — check with
node --version. - git on your
PATH— the CLI reads the current directory'soriginremote to identify the repository. - A GitHub repository with a remote — deployments always start from the repo on GitHub, not from your local files.
- A deplo.ai account with Vercel and Render connected — the CLI offers both connections inline the first time you deploy.
Two commands to production#
$ deplo login
→ opening https://www.deplo.in/cli-auth?port=52814&state=9f2c…&host=mbp.local
(no browser? run `deplo login --token` and paste one instead)
✓ signed in patrickdev · token saved to /Users/patrick/.config/deplo/config.json
$ cd my-app
$ deplo
→ repo detected github.com/patrickdev/my-app (main)
? Deploy patrickdev/my-app? … yes
Analyzing repository…
Detected: frontend=Next.js (client/) · backend=Express (server/)
Deploying backend to Render…
Backend live: https://deplo-my-app-api.onrender.com
Deploying frontend to Vercel…
Frontend live: https://deplo-my-app-web.vercel.app
Deployment completed
✓ backend live https://deplo-my-app-api.onrender.com
✓ frontend live https://deplo-my-app-web.vercel.app
● Deployed in 2:41 — code went in, production URLs came out.Bare deplo is an alias for deplo deploy — running the command with no arguments deploys the repository in the current directory and follows the live log.
What ships in v0.1#
| Area | Status | Details |
|---|---|---|
| Login, logout, whoami | Live | Browser hand-off or pasted token; provider connection checklist |
| Connect Vercel / Render | Live | Vercel OAuth in the browser; Render via masked API-key prompt |
| Deploy with live log | Live | Stack detection, env prompts, AI diagnosis on failure, exit code gates CI |
| Status, list, logs, open | Live | Deployment state per repo or across all projects; open URLs from the terminal |
env set / env ls, monitor, analytics, --json output | v0.2 | Manage env vars and read monitoring data without the dashboard |
| Standalone binaries, Homebrew | v0.3 | Install without Node |
Dive in#
Complete first-run setup on a new machine: prerequisites through first deploy.
Browser hand-off login, CLI tokens, headless machines, and CI.
Every command: purpose, syntax, flags, examples, and expected output.
The config file, environment variables, and pointing the CLI at another API.
Running deplo in GitHub Actions and other CI systems with DEPLO_TOKEN.
CLI-specific issues: login loops, token errors, repo matching, and connectivity.