For engineering leaders

Start measuring your team’s AI spend.

Tokens, cost, model and timestamps for every AI tool your team uses. Never the content. Your code never leaves your team’s machines, but you will know how much you spend and on what.

Let’s talk about a pilot Already have an account? Sign in →

One event, as it travels example 

tool            claude_code
model           claude-opus-5
tokens_input    1 284
tokens_output   812
tokens_cache    3 900
cost_usd        0.0417
occurred_at     2026-09-18T09:41:07Z
project_ref     a91f… (opaque)
What never travels

promptresponsefilepathdiffrepository name

Data boundary

The product is trust.

From the developer’s machine to your team’s backend, only derived, allow-listed metadata crosses. The content of the code never leaves. It is not a promise: the events table has no column where it could fit.

Crosses

  • Tool and agent version
  • Model used
  • Token counts: input, output and cache
  • Cost derived from the model’s public price
  • Event timestamp
  • Opaque project, session and machine references

Never crosses

  • Prompts or responses
  • Files, paths or diffs
  • Repository or branch names
  • Nothing that identifies a person beyond their Permea account
How it works

One agent on every machine, one dashboard for the team.

01

Install the agent

An open-source binary on every team machine. It enrolls with a join code and needs nothing else.

02

Only metadata travels

The agent derives tokens, cost, model and time from each use and sends them over HTTPS. The content stays where it was.

03

See spend where it matters

By developer, by project and by model. Budgets as a reference and monthly reports to allocate the cost.

Permea observes, it does not cut.

A budget is a reading reference: crossing it stops no service and interrupts no measurement. The figures are the value of usage at each model’s public price; what your organization really pays depends on your contract, and Permea does not know it.

Where the data lives

In the European Union, encrypted, with no extra third parties.

Server in the EU

The database lives on a server in the European Union and is served over HTTPS only.

Encrypted backups

A daily backup, encrypted before it leaves the machine, stored in the EU and kept for thirty days.

This site does not track you

No cookies, no analytics, no third-party fonts. What is stored and why is in the privacy policy.

Contact

Let’s talk about a pilot.

Tell us how many people use AI tools on your team and which ones. We reply by email.

This data is used only to reply to you and is not stored in any database: the email is the only record.