Integrations

Voroa CLI command reference

Every Voroa CLI command: services, deploys, logs, environment variables, databases, domains, SSH, API tokens and workspaces, with their flags and exit codes.

How to read this page

<service> is a service name or its id, looked up only inside your active workspace. In a folder where you have run voroa link, it can be left out. Every command accepts --json for machine-readable output - a failure is then {"error", "code"} on standard error - and --workspace <id> to act on another workspace for that one command. --no-input (or VOROA_NO_INPUT=1) makes a step that would ask a question fail with the code NEEDS_HUMAN instead.

Install and sign-in are covered in the Voroa CLI overview.

Voroa CLI commands grouped by job: services and deploys, logs, environment variables, databases, domains and SSH, and account

Services and deploys

Command	What it does
`voroa services`	List the services in the active workspace
`voroa status <service>`	One service’s live state
`voroa status --all`	Every service’s state in one table
`voroa deploy <service>`	Start a deploy
`voroa deploy <service> --wait`	Start a deploy and wait for the result (`--timeout <minutes>`, default 10)
`voroa deploy <service> --follow`	Also stream the build log while it waits
`voroa restart <service>`	Restart without rebuilding
`voroa stop <service>` / `voroa start <service>`	Stop or start the running service
`voroa rollback <service> [--to <deploy-id>]`	Serve the previous version, or a chosen deploy, again
`voroa open [service] [--print]`	Open the service’s dashboard page, or only print its address

Logs

Command	What it does
`voroa logs <service> [--lines N]`	The running service’s output (default 100, maximum 1000)
`voroa logs <service> --follow`	Keep tailing it
`voroa logs <service> --search <text>`	Only lines containing the text, from the last 24 hours
`voroa logs <service> --build [deploy-id]`	A build’s log; the latest build without an id

Environment variables

Command	What it does
`voroa env list [service]`	Variable names (values are never shown)
`voroa env set <KEY> [service]`	Set a value from a hidden prompt or a pipe; `--overwrite` to replace one
`voroa env unset <KEY> [service]`	Remove a variable

A value is never taken from the command line, because it would land in your shell history: echo "$DATABASE_URL" | voroa env set DATABASE_URL web. Setting or removing a variable redeploys.

Databases, domains and SSH

Command	What it does
`voroa db list`	Databases in the active workspace
`voroa db connect <database>`	Open `psql`; asks you to confirm it is you. `--show-url` prints the address instead
`voroa domains list [service]`	Custom domains and their state
`voroa domains add <domain> [service]`	Add one and print the DNS record to create
`voroa domains verify <domain> [--fix]`	Check DNS and the certificate; exits `2` until the domain is live
`voroa ssh [service] [--print]`	A shell in the running service, using your account’s SSH keys

Account

Command	What it does
`voroa login [--password]`	Sign in with an emailed code, or a password
`voroa workspace list` / `voroa workspace set <id>`	List workspaces, or choose the one commands act on
`voroa tokens list`	API tokens in the workspace
`voroa tokens create --name <n> --scope <a,b>`	Create one; the value is shown once. `--save` keeps it on this machine instead of printing it
`voroa tokens revoke <id>`	Stop a token working immediately
`voroa link <service>` / `voroa unlink`	Remember a service for this folder, or forget it
`voroa agent`	Print the guide an AI agent follows to drive the CLI; `--json` for data
`voroa` / `voroa session`	Open an interactive session: one prompt for every command, with Tab completion

Everything else

voroa tools lists the rest of the platform as commands, and voroa tools <word> only those that match a word (voroa tools bucket). The list says for each one whether it changes anything. It covers projects and environments, scheduled tasks, database backups, users and metrics, storage buckets, environment groups, previews, edge cache, maintenance mode, usage, invoices and support tickets. For any of them:

Form	Meaning
`voroa <command> --help`	Its description and arguments
`--service-id`, `--database-id`, …	Arguments are flags named after them; required ones can also be bare words, in the order `--help` lists
`--args '<json>'` / `--args-file <path>`	All arguments as one JSON object; `--args-file -` reads it from a pipe
`voroa tool <command>`	Reach a command whose short name an everyday command already uses (`restart`, `stop`, `start`, `rollback`)

Terminal output of voroa tools listing commands such as list-buckets and create-scheduled-task, followed by voroa list-buckets printing a table

These commands need an API token: set VOROA_TOKEN, or run voroa tokens create ... --save.

Exit codes

Code	Meaning
`0`	Succeeded (with `deploy --wait`: the service is live)
`1`	Failed, including a deploy that failed or did not start
`2`	`deploy --wait` ran out of time while the deploy was still going; `domains verify` before the domain is live

Last updated November 11, 2026