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 Router

Flowstate Router

Flowstate Router is a gateway for AI requests. Your team points Claude Code, Codex, Cursor and other tools at it. Their requests then pass through Flowstate on the way to the AI service. Nobody needs a new account or a Flowstate key.

Flowstate Router is part of Flowstate Helm. It lets Flowstate record what each request was for, and it gives you optional controls over which model answers.

What people notice

  • They keep signing in with the account they already use: a Claude subscription, a ChatGPT sign-in, Google or an API key, including OpenRouter and xAI keys.
  • They change one setting in each tool, once. Connect your AI tools has the exact setting for each.
  • Their tools work as before.

What your organisation gets

  • A record of every request. Flowstate records usage, cost, savings and the routing decision. It doesn’t keep what was said unless an admin turns on session transcripts for that AI service. See Data residency and what’s captured.
  • Optional intelligent routing. Flowstate can move simple prompts to a cheaper model from the same provider. It’s off until an admin turns it on. See How routing works.
  • Optional outage failover. If an AI service is down, Flowstate can send requests to a Flowstate-hosted model. This needs your explicit consent.
  • A recorded decision for every request. You can see whether a request kept its model, moved to another or failed over.

Savings depend on your prompts and your models, so Flowstate doesn’t promise a figure.

How it works in short

  1. Someone sends a request from an AI tool that’s pointed at https://router.flowstate.host/api.
  2. Flowstate recognises them from their AI account sign-in or API key and finds their workspace.
  3. Flowstate applies your routing settings, then passes the request to the AI service.
  4. The answer streams back to the tool.
  5. Flowstate stores the request’s usage and routing decision in your workspace’s region. It keeps the conversation as well only if session transcripts are on for that service.

If Flowstate can’t match the person to a workspace, it refuses the request. It never acts as an open relay for anyone who finds the address.

Supported tools

Claude Code, Claude Desktop, Codex CLI, Codex Desktop, Cursor, OpenCode, Hermes and Junie. Any OpenAI-compatible tool also works with an OpenRouter key (sk-or-…) or an xAI key (xai-…).

Router or Flowstate Desktop

Flowstate has two ways to bring AI requests to Flowstate.

Flowstate RouterFlowstate Desktop
How it worksYou point each AI tool at the router address.An app on the computer sends AI requests to Flowstate. You don’t change each tool.
Best forDeveloper tools and agents you can configure.Company computers, rolled out with device management.
SetupOne setting per tool.Sign in, allow the network extension or turn on routing, trust the certificate.

See Flowstate Desktop.

In this section