Choose strategy or thesis version
Start from a versioned definition.
Reproducible backtesting
Backtests that know what they knew at the time.
A good backtest should survive three questions: what data was available, which strategy definition ran, and which assumptions produced the result. QJ is designed to keep those answers attached.
Instrument Master Identity
Warehouse Facts + compute
User State Decisions
Audit Evidence
Workflow
Choose as-of date or snapshot
Review data as it existed then.
Run or review output
Inspect assumptions, exclusions and results.
Attach to a decision
Promote output into watchlist, monitor or IC pack context.
Status
Point-in-time replay — technical preview.
The architectural foundation for point-in-time reproducibility is in place — data layer separation, warehouse snapshot design and trading calendar service. Full vendor snapshot registry and broader bitemporal rollout across all asset classes are in technical preview and active development.
Product proof
Show the evidence, not only the promise.
Next step
Review a backtest with evidence.
Walk through data snapshot, strategy version and run output.
Request Demo