Replay / time
FerroReplay
Deterministic clock, replay, and journal primitives. The foundation for reproducible state evolution.
Tier 01
PLATFORM
Anvil
The deterministic runtime.
Anvil is built on FerroReplay, FerroMatch, FerroWave, FerroRisk, and FerroFeed. It journals every input and guarantees that any trade or signal can be replayed exactly from first principle to final fill. If you cannot reproduce it, Anvil did not do it.
The brand promise
Determinism is the design.
The platform's core promise is reproducibility. Every non-deterministic path — wall-clock timing, unordered map iteration, floating-point reduction ordering — is either removed or treated as a violation. CI enforces it.
Journal
Every external input is sequenced and written to an append-only journal. The journal is the system of record; everything else is derived.
Replay
Given a journal segment, Anvil replays the exact state transitions that produced a result. No reconstruction, no interpretation, no approximation.
Strategy SDK
A narrow, typed surface for writing strategies. Mis-ordered or stateful side-effects are rejected at compile time, not in production.
Composition
Engines, composed.
Anvil does not implement matching, pricing, signal analysis, or market-data ingestion as product brands. Those capabilities live in Ferro primitives that the MorphIQ Platform can compose. Anvil's job is to wire them together into a runtime that behaves the same way every time, under load, across environments.
Matching engine
FerroMatch
Deterministic limit-order-book matching. Price-time priority, configurable tick semantics, explicit tiebreakers.
Pricing / risk
FerroRisk
Option pricing, Greeks, implied vol surfaces. Reference implementations, property-tested, mutation-scored.
Signal analysis
FerroWave
Discrete wavelet transforms and derived statistics for non-stationary return series.
Market data
FerroFeed
Normalised market-data plumbing. Provider-agnostic contracts, snapshot rules, out-of-band replay.
Who Anvil is for
Firm operators. Strategy developers.
Anvil's audience is not end-users. It is the people who run systematic trading operations — who write strategies, run the backtests, configure the infrastructure, and carry the pager. The platform is built to remove surprises from their day.
Systematic shops
Need production determinism across staging, prod, and DR. Anvil's journal + replay is the substrate.
Quant researchers
Want their backtest and their live trade to run the same math. Anvil's strategy SDK enforces the contract.
Risk and compliance
Need audit trails that reconstruct any execution on demand. The journal is the audit trail; nothing is reconstructed.
Deeper
The platform
has its own surface.
The deep platform documentation — runtime architecture, strategy SDK, runbook, licensing posture — lives on the platform's own subdomain.