Skip to main content

GitHub Copilot cost and adoption

Copilot is a seat subscription for most teams, which makes "what did it cost" a different question from "is it being used". Acticly answers the second with no setup at all, and the first when Copilot traffic runs through a gateway.

Try the demo

What Acticly reads

  • Commit messages, pull request metadata, Co-Authored-By trailers, branch prefixes such as `copilot/`, and labels.
  • Through a LiteLLM gateway: billed spend for any Copilot traffic routed through it, attributed per person.

What you get

  • Copilot adoption per person and per team, from data your repositories already hold.
  • Which pull requests were Copilot-assisted, and how they compare on review time and rework.
  • Seat-versus-usage clarity: whether the people holding seats are the people using them.
  • With a gateway — per-person billed spend alongside your other AI cost.

How to connect

Connect your code repository and adoption data appears — there is nothing for developers to install. Billed spend needs Copilot traffic routed through a LiteLLM gateway.

Acticly → Integrations → Version Control

Adoption   Connect a code repository
           (zero setup — Copilot-assisted commits detected automatically)

Spend      Copilot traffic → LiteLLM gateway → Acticly pulls billed spend

What this does not cover

  • Per-session Copilot telemetry. Copilot does not export it.
  • Your GitHub Copilot seat invoice — Acticly does not read GitHub billing.
  • Prompt or completion content.

Related integrations

CursorLiteLLMGitHubAll integrations