Everything the console does, from your terminal.
curl -fsSL https://outplane.com/install.sh | sh
outplane login
outplane deploy create --wait
One binary, no runtime
A single static binary. Nothing to install beside it, nothing fetched afterwards. The installer checks the download against the release's own checksums, never asks for a password, and puts the binary where you can already write. On Windows, and anywhere your tools already arrive through Node, npm i -g outplane does the same job.
Eighty five commands
Create and deploy applications from a repository or a prebuilt image. Follow a build, or read the output of one that failed. Set environment variables, open ports, point custom domains, attach disks, provision managed PostgreSQL and hand out its connection strings. Read logs, requests and metrics. Open a shell on a running instance.
Every command has its own help with runnable examples, and outplane --help lists them all.
Built to be driven by a program
Output is text on a terminal and JSON in a pipe, so the same command reads well to a person and parses in a script. Every outcome has a stable exit code, appended to and never reused, so a pipeline can branch on the status alone. Failures arrive as an object with a code and a suggested next step, and the message is the only part that changes between releases.
Anything that deletes something never prompts. It stops, and hands back the exact command that would proceed, so the approval belongs to whoever is accountable rather than to whichever terminal happened to be open.
It teaches your coding agent, too
The installer also sets up an agent skill, so the assistant in your editor knows how to use all of this rather than guessing at it. Run outplane skills install if you arrived another way.
Documentation is at docs.outplane.com/cli.