Vertra CLI

Your infrastructure, without leaving the terminal.

Deploy, follow what is running and manage your resources with simple, readable commands that are ready for scripts.

Install the CLI View on GitHub

macOS, Linux and Windows, no dependencies

~/projects/minha-api

$ curl -fsSL https://cli.vertracloud.app/install | sh

$ vertra auth login

$ vertra doctor

Project configuration is ready

Required files were found

Upload size is within the limit

$ vertra deploy

✓ Deployment in progress

→ https://my-api.vertraweb.app

1 commandno Node.js or dependencies

3 languagesEnglish, Portuguese and Spanish

--jsonautomation-ready output

First command

Install once. Use it in the project you have open.

The CLI installs the vertra command on your machine. It then finds the current project and guides the next step.

macOS and Linux

Windows (PowerShell)

The installer downloads the latest binary, verifies its checksum and adds the vertra command to your PATH. Run it again to update.

A direct flow

From a local directory to a published application.

No separate dashboard for each step: connect your account, check the project and send it.

Connect your account

Paste an API key created in the dashboard. The key can also come from the VERTRA_API_KEY variable.

Check before sending

vertra doctor identifies missing fields, incompatible files and other local problems before deployment.

Send and follow

Deploy, stream live logs and check application status without changing context.

Real tools

What you do in the dashboard, you can also do in the terminal.

Commands for operating applications, databases and the local project without another layer between you and the platform.

Deploy and update

Send a new application or update one already linked to the current directory.

Live logs

Read history or follow output in real time with vertra logs -f.

Local checks

Run checks before deploying and fix problems while the code is still on your machine.

Files and environment

List, read and edit remote files; inspect and update environment variables.

Applications and databases

Check status, start, stop, restart and follow resource metrics.

Scripts and CI

Use --json and VERTRA_API_KEY to fit the platform into the automation flow you already use.

Also in your pipeline

Stable output for automation.

With --json, results follow the API response format. Environment-variable authentication avoids saving a key on the runner machine.

# send the project from CI

$ VERTRA_API_KEY=*** vertra deploy --json

{ "response": { "status": "queued" } }