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

Follow a run and fix one that stopped

Each time a workflow starts, it’s a run. A run records every step: what went in, what came out, which rule fired, who decided and what it cost. Use it to check a result or find why something stopped.

Where a run is

StatusMeans
QueuedWaiting to start.
RunningWorking through its steps.
ParkedPaused until something happens. The reason says what.
CancellingStopping because someone cancelled it.
FinishedDone. The outcome says how it ended.

Why a run is parked

ReasonMeans
Needs a personWaiting for a decision. See Make a decision a workflow asks for.
Waiting until laterWaiting for a set time, such as a retry or a scheduled step.
Needs a person: result unknownA step’s result couldn’t be confirmed, so someone needs to check it before it goes on.
Needs attentionSomething went wrong that a person needs to fix.
NotifyingTelling someone about the run.

How a run ended

OutcomeMeans
PassedEverything finished as expected.
DeclinedA person or a rule said no.
CappedA spending limit stopped it.
FailedA step failed and the run couldn’t recover.
CancelledSomeone cancelled it.
ExpiredIt waited longer than allowed.

Read the steps

Each step shows its own status: Pending, Running, Waiting, Succeeded, Failed, Capped, Declined or Skipped. Open a step to see its input and output, the rule that fired, the decision and its cost.

Fix a run that stopped

  1. Open the run and find the step that Failed or Needs attention.
  2. Read the reason.
  3. Fix the cause. Common causes are an expired connection, a missing required field, or a spending limit.
  4. Let the run carry on, or start a new one.

If the fix needs a change to the workflow, change the draft, then publish and deploy it. See Publish and deploy a workflow.

If something’s not right

  • A step failed with an expired connection. Sign in to that system again. See Connect your systems.
  • A step is Capped. It reached a spending limit. Raise the limit, or change the step to use less.
  • A run has waited a long time on Needs a person. Remind the person in its Inbox to-do, or check they have the right to decide.