How it works
How Nythrex works: from AI session to production
Nythrex reads records from your tools, links them into units of work and calculates the cost of each — with a basis for every figure. Below is the same example as on the home page: one change from task to production. Click the links, or remove CI.
Atlas / Checkout
Example project · demo data
STEP 1 OF 7 · TASK
ATL-118 · Checkout address validation
Jira · picked up at 09:12
Time to production is counted from here.
Known cost of this change
$0.00
- AIreported by source—
- CImeasured × price—
- Cloud · Atlas project
- $42.00 · not split across changes
- People’s time
- estimate · optional
Three steps to the first picture
- 1
Connect your sources
One authorization per source: GitHub or Azure DevOps for code and CI, Jira or Trello for tasks, Azure for cloud. List of integrations. - 2
Connect your AI tools
One command per machine configures the Claude Code and Codex installations it finds. For a team — one settings block. More on AI cost tracking. - 3
Open the overview
As soon as records arrive, units of work, cost by project and the first recommendations appear. Until then the product honestly shows an empty state.
The chain of one change
Every link is a record from a specific source. Nythrex connects them by exact identifiers: the task key in the branch, the commit SHA, the pull request number, the session signature.
| Link | Source | What it adds |
|---|---|---|
| Task | Jira, Trello, Azure Boards | the start of the time to production |
| AI session | Claude Code, Codex | tokens, model and the cost reported by the tool |
| Commit | GitHub, Azure Repos | the link from session to code, by SHA |
| Pull request | GitHub, Azure Repos | state: in progress, merged, closed without merge |
| CI | GitHub Actions, Azure Pipelines | minutes × price, failed runs shown separately |
| Deploy | the source’s deployment events | the move from “merged” to “delivered” |
Where every figure comes from
There are no “just numbers” in Nythrex. Next to every amount you see how it was obtained:
Reported by the source
A cost the provider or tool reported itself — for example, Claude Code about its own requests.Measured × price
A quantity visible in the records (CI minutes, tokens) multiplied by the published price.Estimate
When there is no actual price — for example, AI on a subscription. Labelled as an estimate, not a fact.Incomplete
Some prices are unknown. The total shows what is known and says plainly that it is not everything.
What each role sees
- The owner and admins — the overall picture by project, team and person, and the cost-of-time estimate if it is turned on.
- A member — their own work and only their own cost of time. A member does not see colleagues by name.
- Nobody — a comparison of people with each other: there is no such report in the product.
Perguntas frequentes
How does Nythrex know which AI session belongs to a commit?
Through a hook that signs the commit with the session ID. The link comes from the commit itself, not from guessing by time. If there is no signature, the session stays unlinked and is shown on its own line.
What is a unit of work?
A change you can trace from a task or branch to the merge and the deploy: usually one pull request with its commits, AI sessions and CI runs.
What happens if a source did not send a price?
The total is marked incomplete, and a labelled gap appears in the chain. An unknown price never turns into zero.
How often is the data refreshed?
Automatically, on a schedule for each source, while AI tool telemetry arrives as people work. There is no need to start a sync by hand.
Leia também
Deixe de adivinhar.
Comece a ver.
Sem cartão e sem subscrição: os planos pagos ainda não foram lançados.