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 / Integrations

Connect Jira

Connect Jira to bring your projects and ticket activity into Flowstate, where they become effort, cost, capitalisation and R&D evidence. Flowstate only reads from Jira.

You need access to integrations. Ask your Flowstate admin. For the whole set-up, including linking projects, see Connect your project tool.

Before you start

  • Your people in Flowstate, with the email address they use in Jira. See People and teams.
  • Someone who can approve apps for your Atlassian site, usually a Jira admin.

You can connect one project tool at a time.

Connect Jira

Jira connects in one click. You approve the Flowstate app for your Atlassian site, with no key or token to copy.

  1. Go to Settings → Integrations, select Browse catalog and open Jira.
  2. Select Connect with Jira. Atlassian opens.
  3. Choose your Atlassian site and approve the Flowstate app. You come back to Flowstate, which shows the site you’re Connected to.
  4. Choose the projects to bring in: All projects or Only these projects.
  5. Choose whether to Auto-create Flowstate projects.
  6. On the Data Mapping tab, under Project Source, choose JIRA Projects or Issue Types (e.g., Epic). Do this before the first sync: changing it later means clearing out the projects created the first way.
  7. On the Sync Settings tab, choose how far back to read under Initial Sync History Limit, then turn on Scheduled Sync, choose a Time of Day and select Save Schedule.
  8. Match people and teams. See Match people and teams from your tools.

To come back to these settings, select Configure on the Jira row of Settings → Integrations.

Check it’s working

Go to Settings → Integrations → Sync Health and open the Jira tab. When the first sync has finished, the status is Healthy and the counts of Projects, Tasks, Users and Activities are above zero. See Check and fix syncing.

What syncs

  • Projects or epics (depending on Project Source), their tickets, who each ticket is assigned to, and status changes.
  • Changes as they happen, through the Flowstate app, plus a full sync once a day at the time you choose.
  • Nothing goes back to Jira.

Optional settings

These are on the Data Mapping tab.

SettingWhat it does
Initiative SyncBrings Jira initiatives in as Flowstate initiatives. Choose Auto-create initiatives or Suggest for review, enter the Initiative issue type, then select Save Initiative Sync.
Custom Field MappingsUses a Jira field to put a project in a cost centre, department or value stream, or to link it to a Flowstate project by name. Select Add Mapping, enter the field ID (such as customfield_10001) in Source Field, choose a Field Type, then select Save Mappings.
Delivery Status MappingMatches Jira statuses to Flowstate’s delivery statuses. A linked project’s status then comes from Jira.
Effort Tracking ConfigurationChooses which ticket types count towards effort, under Task Types to Include. This applies to your whole organisation.

Connect Jira Data Center

If you run Jira on your own servers, connect it with an API token instead.

  1. Create a service account that can see every project you want, and a personal access token for it.
  2. Go to Settings → Integrations, select Browse catalog, open Jira and select Connect.
  3. Enter your Jira address in API URL, the account’s email in Email, and the token in API Key / Token.
  4. Select Test Connection. When it passes, select Continue, then follow steps 5 to 8 above.

To see changes as they happen with Jira Data Center, add a webhook:

  1. In Flowstate, open the Webhooks tab and copy the Webhook Endpoint URL.
  2. In Jira, go to Settings → System → WebHooks and select Create a WebHook. You need Jira admin rights.
  3. Name it, for example “Flowstate Sync”, and paste the URL.
  4. Select the events Issue created, Issue updated and Issue deleted, then select Create.

If the connection stops

If syncing stops and a red banner says “Jira authentication failed — sync is paused”, connect again:

  • Jira Cloud: select Connect with Jira and approve the Flowstate app again.
  • Jira Data Center: create a new token, open Jira’s settings, select Edit Credentials on the Connection tab, paste the token into API Key / Token and select Save Changes.