Features

Built for teams running agents in production, not generic analytics.
The dashboard is organized around how technical teams adopt agents: install locally, observe centrally, and decide when hosted visibility becomes necessary.

Project, machine, and workspace views

Follow adoption from the machine that runs the agent to the project that carries the spend.

Hosted dashboard access

A shared control plane when multiple buyers, leads, or operators need the same truth.

Secure authentication

Sign-up, login, password reset, and two-factor authentication included.

Control plane

One place for every operational question.

Understand not just how much was spent, but where the rollout is healthy, concentrated, or stalled.

Cost overview

Daily and per-project cost signals for teams watching AI usage budgets.

Machine inventory

See which developer workstations and runners actively emit usage data.

Workspace keys

Operate ingestion keys per workspace instead of treating rollout as one flat namespace.

Subscriptions

A single configured hosted plan today, with room for contact-led volume conversations.

Developer operations

Protected views for users, contact messages, and rollout support workflows.

Launch workflow

What a real adoption path looks like.
01

Install the local agent

Teams start on their machines without waiting for a heavy procurement cycle.

02

Aggregate usage centrally

The dashboard turns scattered usage into a shared rollout view by project, machine, and workspace.

03

Decide how broadly to standardize

Move to hosted dashboard access or a contact-led setup once several teams need one operational source of truth.

Confirm action