Standard patterns fall short in highly regulated environments.

In most analytics systems execution is transient: a calculation runs, produces an output, and disappears. This is ideal exploratory analytics but not regulated workflows where calculations must be documented, validated, replicated, and reused.

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.

With this exection model, every calculation is auditable, repeatable, and self-documenting.

Built in Tier-1 banking environments | Open-sourced via FINOS | Adopted by global systemically important banks

See Finnovate demo

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
trac architecture

Powered by a new execution model called ‘Calculation-as-Contract’ — on trac every calculation is auditable, repeatable and self-documenting.

Read 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.

Learn more

By defining each calculation as an explicit contract, lineage, explainability and repeatability are intrinsic to execution — not enforced through separate tools or processes.

Learn more

Because every calculation is preserved as a reusable, queryable object, outputs can be combined, compared, and extended without rebuilding pipelines or reconstructing past runs.

Learn more

Transforming the operating model for: Model developers • Model users • Model risk managers • Auditors • Platform teams

Explore personas