A different execution model
In trac, each calculation is defined upfront in an explicit metadata contract that drives execution and is preserved as the record of what was run.
Calculations are auditable, repeatable, and self-documenting.
How trac works
A contract based approach
Analytic execution is not a transient event — each calculation is the resolution of a governed durable contract.
Append-only data storage
Using standard cloud object storage, an append-only data model ensures that a complete immutable history of all analytic inputs is retained.
Virtualised model deployment
Model code remains in an external repository (e.g. GitHub) and is fetched dynamically at runtime, so every prior version of every model is a recoverable and executable asset.
Metadata-driven orchestration
Analytics is built around four governed object types each with their own metadata structure: data, models, flows and calculations.
Calculation contracts
Each calculation generates a calculation contract — a durable metadata record that both initiates execution and persists as the authoritative record of what was run.
Runtime resolution
Calculation contracts contain all information required for execution and are resolved at runtime, without reliance on mutable configuration or environment state.
Want the deeper technical view?
Read the calculation-as-contract white paper →What trac enables
Transforming the regulated analytics operating model
By shifting the unit of control from environments to calculations, trac strengthens controls, improves analytical capability and reduces operational overhead.
The trac runtime can be installed independent of the platform. trac models can be run in your existing tools — from IDEs and notebooks to production environments — and will behave consistently across environments.
By defining each calculation as an explicit contract, lineage, explainability and repeatability are intrinsic to execution — not enforced through separate tools or processes.
Because every calculation is preserved as a reusable, queryable object, outputs can be combined, compared, and extended without rebuilding pipelines or reconstructing past runs.
Where trac sits
A governed execution layer for your analytics stack
trac sits alongside your existing tooling — introducing a governed execution layer that connects models, data, and compute into a controlled environment where every calculation is defined, executed, and preserved as a governed object.
Explore deployments