Console Overview

The Velerion Console is the browser-based control plane for the platform. Everything you can do through the CLI or the API has a corresponding surface here, so the Console is usually the fastest way to inspect state and the CLI the fastest way to change it repeatably.

What lives where

Area	Purpose
Workspaces	Top-level tenancy boundary. Billing, members and quotas attach here.
Environments	Deployment targets inside a workspace, typically dev, staging and prod.
Agents	Deployed agent definitions, their revisions and their rollout status.
Connections	Credentials and MCP servers made available to agents.
Observability	Traces, token spend, tool-call latency and error budgets. See Observability.
Settings	Roles, service accounts, audit log and SSO configuration.

First session checklist

1. Sign in and accept the workspace invitation you were sent.

2. Confirm which environment you are pointed at — the environment switcher sits in the top bar and is the single most common source of “why did nothing change” confusion.

3. Create a service account so that CI does not run under a human identity.

4. Install the CLI and link it to the same workspace:

   npm install -g @velerion/cli
   velerion login
   velerion workspace use acme-platform

Next steps

• Workspaces & Environments — how tenancy and promotion between environments works.
• Access Control — roles, service accounts and audit logging.
• MCP Catalog Overview — attach tools to your agents.
• Observability Overview — what is recorded about every run.