dira quietly tracks the minutes you're actually engaged while Claude Code, Codex, Gemini, Cursor, OpenCode and Grok do the work — then turns them into invoices anchored to real commits.
Start tracking freeSee how it countsOne person supervising three agents is still one human-minute per minute. dira dedupes it for you.
The minutes you were present — prompting, approving, reviewing. Deduped across parallel sessions. The only thing money is computed from.
How long agents actually ran — larger than your engaged time because you supervise several at once. Evidence, never a billing base.
Tokens and an estimated figure per session — a separate, optional invoice line, so you bill or absorb the AI surplus per client.
dira signs each interval on your machine and confirms the commit SHAs exist in your remote. A client can inspect the commits behind any hour.
Two products record what already happened. Two turn that record into forward value.
Every deliverable the Act asks for is a question about a Tuesday that already happened — and dira is the only thing in your stack that was in the room when it did.
One price for all four books — dira, zavet, proba and miara. You are billed per developer who actually recorded something that month, and for nothing else — from two active developers up to fifty. Above fifty we quote per contract, because org-wide rollout is a different job.
Everything in Team, plus proba's Enforce dial (org-wide rulesets, fail-closed available, break-glass recorded) and the whole stack inside your own VPC; SSO/SCIM, data residency, audit export.
Quoted per contract. You get the number on the first call, not the third.
Talk to us →A developer who recorded no sessions is not billed — not prorated, not billed. Already tracking locally? Your existing data flows straight in, nothing to re-capture.
Start free in one command. Charge clients with proof, not estimates.
Start tracking free →dira quietly tracks the minutes you're actually engaged while Claude Code, Codex, Gemini, Cursor, OpenCode and Grok do the work — then turns them into invoices anchored to real commits.
One person supervising three agents is still one human-minute per minute. dira dedupes it for you — so the base every invoice bills from is real.
The minutes you were actually present — prompting, approving, reviewing. Deduped across every parallel session. This is the only thing money is computed from.
How long agents actually ran — larger than your engaged time because you supervise several at once. Evidence and a capacity signal, never a billing base.
Tokens and an estimated dollar figure per session. A separate, optional invoice line — so you can bill or absorb the AI surplus per client, never hidden in the rate.
dira signs each interval on your machine and confirms the commit SHAs exist in your remote. A client can inspect the commits behind any hour. That's stronger than any timesheet.
Two products record what already happened. Two turn that record into forward value. Hover a segment.
The whole suite — letopis →Most tools ask you to trust a number someone typed in. Every number here traces back to something signed and checkable: a session, a commit, a written decision, a merge. That is the only reason a client, an auditor or a CFO ever accepts it.
While your agents work, dira counts the minutes you were actually there — prompting, reviewing, approving. Run four agents at once and it still counts one you. Each hour is stamped with the commits it produced, so a client can click through and see the work.
Six months on, nobody recalls why exports stream row-by-row. zavet writes the reason down when the choice is made, keeps it in the repo next to the code, and blocks the next agent from quietly undoing it. Ask /zavet:why and get the answer in seconds.
Gold gets stamped 585, 750 or 999 for how much of it is really gold. proba stamps every merged pull request the same way — did tests pass, did a second person review it, which agent wrote it, how long you supervised. It reports; it never blocks.
Agents made your old estimates useless — the same feature now takes a fraction of the time. So miara ignores gut feel and prices new work from jobs you actually delivered, with real recorded hours. It gives a range, and below three similar jobs it gives no number at all.
If what you ship with agents falls in scope, someone eventually asks who was supervising the agent, for how long, and on whose authority. Article 14 wants the oversight to be real; Article 17 wants the record of it; Annex IV wants the rationale behind the design choice you made in March.
Every one of those is a question about a Tuesday that already happened — and dira is the only thing in your stack that was in the room when it did.
The Cyber Resilience Act's reporting duty starts first. Article 14 gives you 24 hours to file an early warning on an actively exploited vulnerability, 72 for the full notification and 14 days for a root-cause report — for products already on the market, not just future ones. On that clock, knowing what changed, which agent wrote it and why is the difference between filing and guessing.
The September clock →And the honest part. dira is not an AI Act product and will not pretend to be one. It does no runtime logging — Article 12 governs the AI system your users touch, while dira records the AI that built it. It cannot tell you whether you are high-risk, and no dashboard on earth can certify you as compliant. What it removes is the archaeology: the interviews, the guessed dates, the design rationale written in August about a decision made in March.
The full article-by-article mapping →One price for all four books — dira, zavet, proba and miara. You are billed per developer who actually recorded something that month, and for nothing else — from two active developers up to fifty. Above fifty we quote per contract, because org-wide rollout is a different job.
Everything in Team, plus proba's Enforce dial (org-wide rulesets, fail-closed available, break-glass recorded) and the whole stack inside your own VPC; SSO/SCIM, data residency, audit export.
Quoted per contract. You get the number on the first call, not the third.
Start free in one command. Charge clients with proof, not estimates.
Start tracking free →