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

Give people access to build

Anyone with access can use an application’s views in Workforce. Building and changing applications needs a builder seat and permissions on top.

What a builder needs

  1. A builder seat. Your organisation’s plan comes with a number of builder seats. Ask your Flowstate contact for more.
  2. The Open Studio permission. It opens the area where applications are built. Only the Administrator role has it to begin with.
  3. Permissions for the work they do. These are grouped under Studio - Flows on the roles page:
PermissionLets them
View flowsSee the flows list and read a flow.
Edit flowsChange a flow on the canvas and save the draft.
Publish flowsFreeze a version of a flow so it can be deployed.
Deploy flowsDeploy, pause or roll back a version. A deployed flow acts as the person who deployed it.

Give a builder access

  1. Go to Organisation → People & roles → Roles.
  2. Open the role your builders have, or create one for them.
  3. Turn on Open Studio and the Studio - Flows permissions they need.
  4. Save the role, and give it to your builders under Users.

See Invite people and manage their access and Roles and permissions.

Keep building and going live separate

Give Edit flows to the people who build, and Publish flows and Deploy flows to the people who sign off what goes live. A change then always has a second pair of eyes before it reaches anyone.

Give someone the right to decide

A workflow names the roles it asks for a decision. Each person also needs the right to decide on that step. Ask your Flowstate admin to give it. See Make a decision a workflow asks for.