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 Bitbucket

Connect Bitbucket Cloud to see pull requests and repositories in Flowstate, alongside what they cost and how much AI helped. Flowstate only reads from Bitbucket.

You need access to integrations. Ask your Flowstate admin.

Before you start

  • In Bitbucket: someone who can see the workspace’s repositories.
  • In Flowstate: your people added with their work email addresses. See People and teams.

Connect Bitbucket

Bitbucket connects in one click. You sign in to Bitbucket and approve, with no key or token to copy.

  1. Go to Settings → Integrations, select Browse catalog and open Bitbucket.
  2. Select Connect. Bitbucket opens.
  3. Sign in and approve Flowstate’s read access for your workspace. You come back to Flowstate.
  4. Match each Bitbucket account to a person. See Match people and teams from your tools.

What syncs

  • Repositories, pull requests, who opened and reviewed them, and when they merged. Changes arrive as they happen.
  • Nothing goes back to Bitbucket.

Pull requests show in Workforce’s Engineering insights and in Flowstate Helm’s Engineering. See Engineering insights and See what AI is used for.

If something’s not right

  • Some repositories are missing. Flowstate reads what the person who connected can see. Connect again as someone who can see them.
  • Someone’s pull requests aren’t counted. Their Bitbucket account isn’t matched to a person yet. See Match people and teams from your tools.