Uptriva CLI · Open Source

Everything the dashboard does, in your terminal

One Go binary against the same API. Names work where UUIDs do, JSON output pipes into jq, and scoped tokens keep CI keys minimal.

Install in one line

Single Go binary. Grab it from releases or install with go. Then log in with an API token and you're in.

go install github.com/uptriva/cli/cmd/uptriva@latest
uptriva auth login
uptriva monitors list

Tokens come from the dashboard under Security → API tokens. Scoped keys (monitors:write, one status page) are enforced server-side.

Full monitor lifecycle

create, pause, resume, update, delete. Names or short ids, no UUID juggling.

Live status view

uptriva watch renders your status page as a TUI — latency, status, 10s refresh.

Alerts plumbing

contacts, webhooks, monitor groups, maintenance windows and incident updates.

Agent-ready

llms.txt documents the whole command surface so AI coding agents can drive it correctly.

Scriptable everywhere

-o json on every command. Exit codes behave. Pipes just work.

Self-updating

uptriva update pulls the latest release from GitHub.

uptriva auth loginstore an API token (prompted, never in shell history)

uptriva monitors listmonitors as a table — status, latency, regions, page

uptriva monitors create --type http --target <url> --status-page <id>new monitor

uptriva monitors pause|resume|delete <name>lifecycle by name or id

uptriva watch --status-page uptrivalive TUI scoped to one page

uptriva heartbeat <name>push a heartbeat ping

uptriva incidents create|update|resolveincident ops

uptriva overviewaccount uptime, monitors and agent health

uptriva updateself-update to the latest release

Point an AI agent at the repo's llms.txt and it can manage your monitoring correctly.