
Native connectors, no setup burden
Claude Code, GitHub Copilot, Codex, Git, and Jira. Token and compute cost comes straight from the provider APIs. Nothing installs on an engineer's machine.
Capture human time and AI activity together in Jira so you can measure what your AI tools are truly contributing and costing.


Tempo is trusted by 30,000+ global companies






Get a breakdown of your AI investment by provider, team, and epic – with every dollar of spend tied to the Jira work it funded.
Connect to GitHub, Claude, and OpenAI to see AI vs non-AI cycle times, blended work items, and how AI spend maps to real work. No manual tagging involved.

Compare AI-assisted work against everything else on cycle time and throughput, by team, tool, and model.

Human time and AI activity on the same Jira work item, captured automatically. No tagging, no change to how engineers work.

AI spend attributed to the Jira issue, epic, and initiative it supported. Spend tied to no work at all is shown, not buried.

Token and compute cost pulled straight from AI provider APIs. A receipt from the provider, not a figure inferred from code volume.
See where your AI spend actually lands.

Claude Code, GitHub Copilot, Codex, Git, and Jira. Token and compute cost comes straight from the provider APIs. Nothing installs on an engineer's machine.

Every dollar traces to a ticket, an epic, and an initiative, including the spend that maps to no work at all.
Deploy people and agents deliberately.

Human time and AI activity sit on the same Jira row. Nobody logs anything extra and nobody reconciles two systems.

See where a person adds the value and where an agent does, story by story, then staff the next sprint on evidence.
Optimize the spend you already have.

From work item to epic, initiative, and portfolio, in the shape finance and the board already read.

Team against team, quarter against quarter, tool against tool, model against model, and AI-assisted work against everything else. Shape usage, optimize models, capitalize spend, cut waste.
Get board-ready AI ROI data today – with a 90-day lookback
Ensure your company's data is completely secure and that you're in compliance with the latest standards.









Tempo tools integrate with the solutions your organization already uses, right out of the box.
Tempo's products help teams increase productivity and communicate across their organization.
Visualize project plans and roadmaps with a Gantt chart extension for Jira
Learn moreTempo’s intuitive automation and Jira-native design make it the most trusted time tracking tool for enterprise organization.
Learn moreA powerful team resource management tool designed to optimize capacity planning and project management in Jira
Learn moreThe roadmapping tool designed for high-performing teams delivering boardroom-ready strategic roadmaps.
Learn moreCouldn't find what you need?Go to ourDocumentation
Yes. Workforce Intelligence is available now on the Atlassian Marketplace. You can start a free 30-day trial on your own Jira instance in a few clicks, or book a demo with a solutions expert to see it live first. Early-adopter pricing is available for the first paying customers.
Workforce Intelligence pulls session cost – token counts, compute cost, and model version – directly from the provider (Anthropic, OpenAI, GitHub Copilot). When that session's code lands on a branch carrying a Jira issue key, the cost resolves to that issue, rolls up to its epic, and groups by the Jira initiative it belongs to – sitting beside the human hours already logged against the same work. Spend that can't be tied to a work item is shown as unattributed rather than force-fit.
For AI cost and usage, Workforce Intelligence connects directly to Anthropic (Claude Console admin API), OpenAI (admin API), and GitHub Copilot. On the Git side, it reads commit history from GitHub to resolve session cost to the Jira issue the code supported. Additional connectors – including GitLab, Bitbucket, and Cursor – are on the way.
No. It connects at the organization level through provider APIs – there's nothing to install on individual machines, no manual tagging, and no change to how engineers do their work.
Spend that can't be tied to a Jira work item using the current attribution method is shown as unattributed, so the numbers stay honest about what's actually traceable versus what isn't yet.
Get the data you need without changing your workflows.