Open source
Traza is a trace database for agent workloads: one binary, no external database, no queue, no coordinator. It is Apache-2.0, and it is the whole product. Traza Cloud is a way to not run it yourself.
The covenant
An open-core promise is only worth what you can verify. So each of these says how.
There is no enterprise directory, no source-available license, no feature that only our builds switch on. Third-party components keep their own licenses, listed in the repository’s notices.
How to check Read LICENSE and NOTICE at the root of the repository, and look for anything that is not Apache-2.0 in its source tree.
Every cell runs an unmodified traza-server release (0.28.0 or later). The cloud talks to it only through its documented HTTP API; it never patches, forks or wraps the engine’s storage.
How to check Fetch an evidence pack for your project. Its engine_version field is the build that generated it; compare it with the releases page.
Authentication and scoped credentials, tenancy, quotas, retention, erasure with receipts, backups and restore, the run fuses, replays, the ledger and evidence packs: all in the open binary, documented in its own docs.
How to check Every feature on this site that is not listed in the next item is in the engine’s documentation, with its HTTP route.
Running and upgrading cells; orgs, members, SSO and an audit log; API keys with scopes and rate limits; alert delivery to email, Slack and webhooks; share links; and a notary that signs your ledger, which by definition has to be someone other than you.
How to check Compare the plan table on the pricing page with the engine documentation: every paid line is hosting, collaboration, delivery or a third-party signature.
Export is on for every plan, including when you are capped or unpaid, with no egress fee. It streams one span per line in the engine’s native JSON, ends with a trailer that says whether it is complete, and your own traza-server ingests the lines through its native route. Large payloads and annotations are fetched separately; the export guide shows how.
How to check GET /v1/export through api.trazadb.com with a read key, on any plan, at any time.
Why Apache-2.0
Traces carry prompts, completions, tool inputs and customer identifiers. The software that stores them should be software you can read, build, audit and run without asking anyone. Apache-2.0 lets you do all of that, commercially, with an explicit patent grant, and without a clause that changes what you may do if you compete with us.
It also keeps us honest. If the cloud were a fork with the good parts held back, you could not tell from outside. Because it is the same binary, the only way for the cloud to be worth paying for is to run it better than you would want to, and to add what genuinely needs a host.
Run it yourself
No metadata database, no column store, no lock service, no object store to configure. Three direct dependencies
in a default build, HTTP, threading and file I/O from the standard library, and an engine crate that is
#![forbid(unsafe_code)].
It is single-node: one writer per data directory, no replication or failover in this release. If you need native high availability today, the engine’s README says so before you find out.
cargo install traza --locked --bin traza-server
./traza-server --data-dir ./datatraza-server listening on 127.0.0.1:8080
traza-server: durability=wal — acknowledged writes are fsynced to the write-ahead log and recovered on restartRelease archives with the dashboard built in, Docker images and build-from-source steps are in the README.
| Self-hosted engine | Traza Cloud | |
|---|---|---|
| License and price | Apache-2.0, free | Free tier, then priced by spans |
| Foresight, Steer, X-Ray, Replay & Fork, Guard, TQL, the importers, MCP | Yes | Yes, on every plan |
| Live runs and nudges | The engine’s live-runs API and stream, on the server | Mission Control across every project, on your phone and in Slack |
| Across projects and developers | One server’s tenants, by API | Foresight board, weekly change digest, coding agents view |
| Ledger and evidence packs | Yes; bring your own notary | Yes; our notary anchors hourly and signs packs on Team |
| Who runs, upgrades and backs it up | You | Us |
| Orgs, members, SSO, audit log | Tokens, scopes and tenants | Accounts, roles, OIDC SSO and audit on Team |
| API keys | Bearer tokens per tenant | Scoped project keys with per-project rate limits |
| Alerts | Poll the fuse event feed | Email, push, interactive Slack and signed webhooks, delivered and retried |
| Your data leaves with | The data directory | GET /v1/export, any time |