Explore Flowstate

The Flowstate platform
Helm

Know what AI costs. See what you get back.

Understand spending, share budgets and connect AI use to the work it supports.

Recent insights All insights

Buy tokens, rent GPUs, or own the rack?

Open-weight models are now good enough to make self-hosting a financial question rather than a capability one. I modelled four options, an office rack, colocation, rented GPUs and per-token APIs, to find where each one actually wins. The answer turns on utilisation, and it isn't the one the internet keeps giving.

Turn a $3m AI bill into $1.9m

Most teams overpay for AI twice without noticing: they run everything through the default flagship model, and they buy the tokens on a metered plan they can't see into. An intelligent proxy fixes both. Here is the maths, a calculator you can drag, and where Flowstate fits.

Start with the work All use cases

Understand AI spending and value

See where the budget goes and what the business gets back.

Share one AI budget across your tools

Fund people, teams and projects across connected services.

Give your team more capacity

Reduce the preparation, checking and follow-up around recurring work.

Connect AI use to delivered work

Follow AI activity into projects, code and business results.
Quick links
Flowstate / People + AI Talk through your priorities
Documentation
Get help
Docs / Integrations

Connect GitHub Copilot

Connect GitHub Copilot to see who actually uses Copilot, and what your organisation is billed for it.

You need access to connect AI providers. Ask your Flowstate admin. For pull requests and commits, see Connect GitHub instead.

Before you start

  • An organisation owner in GitHub, to create the token.
  • The Copilot usage metrics policy enabled in GitHub. Without it, GitHub doesn’t report activity per person.

Connect GitHub Copilot

  1. In GitHub, create a personal access token with the read:org scope. For a fine-grained token, give it the View Organization Copilot Metrics permission instead. Don’t use manage_billing:copilot: it doesn’t give access to organisation reports.
  2. Note your organisation’s login exactly as it appears in your GitHub web address.
  3. In Flowstate, go to Settings → Integrations, select Browse catalog and open GitHub Copilot (Business / Enterprise).
  4. Under How to connect, select Use this route.
  5. Enter the token in Personal access token and the login in Organisation.
  6. Select Verify and connect.
  7. Match GitHub logins to people under Settings → Integrations → User attribution. GitHub doesn’t send email addresses, so Flowstate can’t match them for you. See Match people and teams from your tools.

Check it’s working

The token is listed under Connected keys with the status Working. See spend and adoption in Agent insights.

What Flowstate brings in

  • What GitHub billed your organisation for Copilot, each day.
  • Each person’s daily Copilot activity, recorded against their GitHub login.
  • Flowstate syncs every hour, and brings in your history when you first connect. Reports start on 10 October 2025 and reach back one year.
  • GitHub publishes each day’s figures within two full days, so the latest day or two is always empty.

If something’s not right

Cost arrives but there’s no activity per person. The Copilot usage metrics policy isn’t enabled in GitHub.

The last day or two are empty. That’s expected. GitHub hasn’t published those days yet.

Activity isn’t shown against a person. Their GitHub login isn’t matched. Match it under User attribution.

The connection shows Key rejected. The token expired or lost its scope. Create a new one and select Replace key on the connection.