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

Publish and deploy a workflow

Changes reach the people using an application in three stages. You edit a draft, publish it as a version that can’t change, then deploy that version where it should run. Each stage needs its own permission, so the person who builds a change doesn’t have to be the person who puts it live.

Publish a version

When the draft is ready, publish it. Publishing checks the workflow and its tests:

  • If the workflow has problems, you’ll see “This flow cannot be published yet. Fix the problems listed and try again.”
  • If its tests haven’t passed since the last change, you’ll see “The tests for this flow have not passed since it last changed.” Run the tests, fix what fails and try again.

A published version never changes. To change it, edit the draft and publish again.

Deploy a version

Deploy the version to an environment:

  • A test environment to try it safely. Runs there act as the person who started them.
  • Live for the people who use the application. Runs there act as the person who deployed the version.

Only live environments can be started from outside Flowstate, such as by another system calling the workflow.

Agree to a workflow running as you

A live run acts as the person who deployed it. Another person can agree to a specific version running as them instead, for example when it needs their access. Only that person can agree: “Only you can agree to a flow running as you.” Their agreement covers that exact version, so a new version needs agreeing again.

Change a live workflow

  1. Change the draft. The live version keeps running unchanged.
  2. Run the tests and publish the new version.
  3. Deploy it to a test environment and check a few runs.
  4. Deploy it live.

Pause or roll back

  • Pause a deployed version to stop new runs starting. Runs already going carry on.
  • Roll back to put an earlier version live again, if a new version causes problems.

Who can do what

PermissionLets you
View flowsSee the flows list and read a flow.
Edit flowsChange a flow and save the draft.
Publish flowsFreeze a version so it can be deployed.
Deploy flowsDeploy, pause or roll back a version.

See Give people access to build.