Skip to content
Trazum

In development. Not open yet.

Trazum Pro

The open tool answers for a person, on their own files. Pro answers for an organisation, from the receipts every machine in it files.

What it answers

Four questions, for an organisation rather than a person. Pro stops there: it does not become a proxy, a gateway or a monitoring platform.

  1. Where the model spend went

    By project, by model and by provider, over a period, from every machine that files a receipt.

  2. Whether it is inside its budget

    Ceilings on the organisation or on one project, with what is consumed, the burn and the projection, and an alert before the invoice rather than after it.

  3. What changed when it moved

    Why the bill moved: volume, size, unit cost and the interaction that belongs to none of them, four terms that add back to the change exactly.

  4. A figure an auditor can trace

    Every figure says which rate produced it and when that rate was last reviewed. A number nobody can audit is what Pro exists to replace.

No prompt text reaches this server.

Not redacted, not hashed, not truncated on arrival. The analysis already ran on the machine that made the call, a laptop or a CI runner, and what travels is a receipt: token counts, the model, the rate applied, the date that rate was last reviewed, the attribution label, the period, and what could not be priced.

  • The receipt is made by trazum receipt, with receiptFrom from @trazum/core: MIT, in this repository, readable by anybody without asking for anything.
  • A test plants prompt text, a file path, a branch name and a credential in a log, and fails if any of them reaches the receipt.
  • One field is yours to write: the label. It travels as you wrote it, so name it after a project and not after a prompt.

A capability that would need the prompt does not get built.

Free forever, and what Pro adds

Anything one person can compute from their own files on their own machine is free, forever, in the open tool. Pro adds what nobody has alone: aggregation and memory across a team.

The open tool, MIT

  • Every analysis this repository performs: the bill, the gates, the optimiser, the pricing, the converters and the report documents
  • On your own machine, with no account and no provider key to begin
  • The receipt Pro reads, and the code that makes it

Trazum Pro

  • Budgets and alerts across a team
  • Chargeback to cost centres
  • Reports that arrive on their own
  • An audit log of who changed what
  • Single sign-on

No analysis moves out of the open set to make a feature of Pro. If Pro needs an analysis that does not exist, it is written here, in the open, first. Pro is proprietary and developed separately, and that relicenses nothing in this repository. What is open, what is not, and what cannot move

The tiers

A flat price for the organisation, by the model spend it manages in a month, not by seat. The product measures that number itself, from your own receipts, so the tier you are in is arithmetic and not a negotiation.

Trazum Pro tiers, by managed spend a month
TierPriceManaged spend a monthPrice as a share of spend
Team€149 a monthUp to €5,0002.98%
Growth€499 a monthUp to €25,0002.00%
Scale€1,499 a monthUp to €100,0001.50%
EnterpriseBy agreementAbove €100,000By agreement

The share is also the break-even: at Growth, Pro pays for itself the moment it finds a 2% saving on a bill it is already watching.

Free for an organisation of one member. Paid from the second.

These prices were decided, not measured, and nothing is charged today.

Not open yet

Pro is in development, in a separate private repository. Nobody can use it yet and there is nothing to buy: billing is not built, and it waits until organisations ask for it.

This opens your email with a message to davidmunozrey@protonmail.com and the subject filled in. The maintainer reads it, and nothing else is done with it: no list, no tracking.