Explore Flowstate

The Flowstate platform
Flowstate 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 classic personal access token with the read:org scope.
  2. If your organisation uses SAML single sign-on, select Configure SSO next to the token and authorise it for the organisation. If your organisation has Flowstate Helm, that also lets Flowstate match Copilot users by their work email. See People.
  3. Note your organisation’s login exactly as it appears in your GitHub web address.
  4. In Flowstate, go to Organisation → Organisation → Integrations and select GitHub Copilot under AI coding tools.
  5. Select Connect, or Add another account if one is already connected.
  6. Enter the token in Personal access token and the login in Organisation.
  7. Select Verify and connect.
  8. Match GitHub logins to people under Settings → Integrations → User attribution. Copilot reports each person’s activity by their GitHub login. See Match people and teams from your tools.

If your organisation doesn’t use Organisation yet, replace steps 4 and 5: go to Settings → Integrations, select Browse catalog and open GitHub Copilot (Business / Enterprise), then under How to connect select Use this route.

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.

People

If your organisation has Flowstate Helm, Flowstate also brings in everyone who holds a Copilot seat in your organisation, by their GitHub login. A seat doesn’t come with an email, so Flowstate reads work emails from your SAML single sign-on, with a classic token authorised for it (step 2). Anyone it can’t place without an email is listed on Users & teams under their GitHub login, flagged No email, until you link them to someone in Flowstate or create them with an email. Nobody is emailed until you invite them.

If the connect window (or the provider’s page in Settings) says “Imported by GitHub login: this token can’t read your SAML identities, so people need a look before they can be invited”, your organisation doesn’t use SAML single sign-on, or the token isn’t a classic one authorised for it. If you use SAML, create a classic token, authorise it (step 2) and select Replace key on the connection. Otherwise, link each person to someone in Flowstate, or create them with an email, on Users & teams.

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, or the connect window (or the provider’s page in Settings) says “This key can’t list your people”. The token expired or lost its scope, or GitHub refused it when Flowstate asked for your people. Create a new token (steps 1 and 2), then select Replace key on the connection, or Replace the key beside the message. Enter the token and your organisation’s login, and select Verify and connect.