Connect the tools you already use
Acticly reads from your AI coding tools and your delivery stack. Most of it needs nothing installed on a developer machine, and none of it needs a new survey.
AI coding tools
Per-session spend, straight from the tool. Claude Code and Codex export OpenTelemetry, so one config file per developer is all it takes.
Claude Code
Details- What Acticly reads
- Session telemetry — model, tokens, and timing per session. No prompts, no code.
- What you get
- Cost per developer and per session, spike alerts, and adoption trends over time.
Codex CLI
Details- What Acticly reads
- Session logs and metrics over OpenTelemetry, with prompt logging off.
- What you get
- Cost visibility alongside your other agents, in one total rather than several invoices.
AI gateways
The tool-agnostic path. Connect a gateway once as an admin and every tool routed through it is covered, with nothing for developers to install.
LiteLLM
Details- What Acticly reads
- Billed spend pulled from your gateway on a schedule, with the principal each record belongs to.
- What you get
- Per-person cost for every tool behind the gateway, one total across providers, and optional spend controls that start in dry-run.
MCP
Details- What Acticly reads
- Nothing new — it is a read path over the data Acticly already holds, using your own identity via OAuth.
- What you get
- Ask about delivery, spend, alerts and wellbeing from Claude, Cursor, Codex or VS Code, without opening Acticly.
Tools without their own telemetry
Cursor and Copilot do not export per-session telemetry, so we do not claim to read it. You can still see adoption with no setup, and billed spend if their traffic runs through a gateway.
Cursor
Details- What Acticly reads
- Commit messages, pull request metadata, trailers, branch prefixes and labels — or billed spend via a gateway.
- What you get
- Which work was Cursor-assisted and who is adopting it, with no setup. Per-person spend when routed through LiteLLM.
GitHub Copilot
Details- What Acticly reads
- The same repository signals — or billed spend via a gateway.
- What you get
- Adoption per person and per team, seat-versus-usage clarity, and spend when routed through LiteLLM.
Code and delivery
Where the work happens. Connect one of these to get DORA metrics and delivery flow.
GitHub
Details- What Acticly reads
- Pull requests, commits, reviews, and repository metadata.
- What you get
- DORA metrics, review bottlenecks, and per-team delivery flow.
GitLab
- What Acticly reads
- Merge requests, commits, and reviews.
- What you get
- The same delivery and DORA picture as GitHub.
Bitbucket
- What Acticly reads
- Pull requests, commits, and code review activity.
- What you get
- Delivery flow and review metrics, including via the Atlassian app.
Jira
Details- What Acticly reads
- Issues, sprints, epics, story points, and status transitions.
- What you get
- Sprint delivery, epic progress, workload balance, and issues joined to the code that closed them.
Where insights land
Optional. Push what Acticly finds into the channel the team already reads.
Slack
- What Acticly reads
- Nothing from your conversations — this is a delivery channel, not a data source.
- What you get
- Alerts and insights in-channel, so nobody has to remember to open a dashboard.
Need something that is not listed?
We support custom data sources and on-premise tools, and our team can help wire Acticly into your environment.
Request an integrationNot sure what you would see? Compare the two products.