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

Start from a pack

A pack is a ready-made application: its workflows, data stores, views, agents and connections, bundled together. Start from a pack when someone has already built the job you need, such as month-end reporting, and adapt it to how you work.

What a pack brings in

  • Workflows, agents, data stores and views, as drafts.
  • Connections without any sign-in details. You connect your own systems.

Nothing from a pack is published, deployed or added to the Workforce sidebar when you install it. You decide what goes live, and when.

Make a pack your own

  1. Install the pack your Flowstate team has made available to you.
  2. Connect each system it uses. See Connect your systems.
  3. Check each workflow’s steps and agents’ instructions against how you work, and change what’s different.
  4. Run the tests, then publish and deploy each workflow. See Publish and deploy a workflow.
  5. Publish the views to the Workforce sidebar for the roles that need them. See Show the work in Workforce.