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 / Flowstate Sail

Connect your systems

A connection lets an application read from and write to one of your systems, such as your CRM, finance system, document store or ticketing tool. You connect a system once, and any workflow you allow can use it.

Connect a system

Most systems connect in one click. Choose the system, sign in to it, and approve the access Flowstate asks for. Flowstate never sees your password.

Some systems need a key or token instead. You paste it once into a field that can’t be read back, and Flowstate checks it with one test request. Your organisation can also use its own app registration for a system, if its IT policy needs that.

Choose what agents can do

Each connection offers operations, such as reading a record, searching or creating a document. Switch on only the ones the application needs. Reading is kept separate from writing, so an agent can look things up without being able to change them.

MCP servers connect the same way, and you choose which of their tools are allowed.

Check a connection is healthy

Each connection shows whether it’s working. If its sign-in has expired, been revoked, or doesn’t give enough access, the workflows that use it stop at the step that needs it. Sign in again, or ask the system’s admin for the access it needs, and the workflow can carry on.

AI services

AI services, such as Anthropic, OpenAI and Google, are managed in Flowstate Helm, so their spending is counted in one place. See Connect your AI providers.

Connections Flowstate already has

Systems your organisation has connected for Workforce or Flowstate Helm, such as Jira, Linear or GitHub, are listed under Integrations.