Platform
One surface, and no comfortable lies on it.
MOCR sits above your engines and your venues and resolves them into a single account of what happened — priced correctly, attributed to a build, and explicit about what it does not yet know.
01 / Measurement
P&L that survives scrutiny.
Trading P&L is priced at settlement, not at last trade, and fees are computed from the venue’s actual fee law rather than read from the field it reports — which on some venues is reliably zero.
Rebates are held separate from trading net, because a system that loses money on flow while earning it on rebates is a different business from one that does not, and a single blended figure hides which you are running.
- Settlement pricing
- Positions valued on resolution, with late and revised settlements backfilled through the record rather than left as the number you happened to see first.
- Exact fee law
- Fees derived per fill from the venue’s published schedule, so the cost side is independent of whatever the venue chose to report.
- Decomposition
- Net attributable by system, side, instrument and session — enough resolution to see which leg of a strategy is carrying the other.
- Continuous history
- Halted and decommissioned systems stay in the all-time record. Turning something off should not quietly improve your track record.
02 / Liveness & provenance
Fresh is not the same as trading.
Almost every trading dashboard has one badge, and it means “data is arriving”. Operators read it as “we are trading”. Those come apart precisely when it matters, and the gap is usually discovered at the end of a day that produced nothing.
MOCR reports them separately. Sending is derived from the engine’s own decision log — evidence that an order actually went out — and alerts when it lapses while the feed stays healthy.
- Sending state
- Read from decision logs rather than inferred from uptime. A process can be running, healthy and sending nothing at all.
- Build registry
- A deploy record maps every fill to the version that produced it, so a comparison between configurations rests on which binary was armed rather than on recollection.
- Arming checks
- Verification that what is deployed is actually configured to trade. A shadow build compiles, deploys and reports healthy while sending nothing — and looks identical to a quiet market.
- Honest charts
- Series are drawn only over the range where data exists. A line padded flat to the end of the day is indistinguishable from an engine that died at noon.
03 / Experiments & parity
Tests that can answer the question.
The same change, run at two sizes, can look like a triumph and a disaster while being neither. Only the statistics distinguish an edge from a fluctuation, and only if the sample was large enough to try.
MOCR states the required sample before the run, holds each change to acceptance signals fixed in advance, and scores the simulator against the live engine on identical inputs so that a disagreement between them becomes a finding rather than an argument.
- Power analysis
- The observation count a comparison needs, computed before it starts. Some questions cost more live risk to answer than the answer is worth, and it is cheaper to learn that first.
- Acceptance fingerprints
- Each change declares what evidence would show it worked, before deploy. Post-hoc criteria are how a losing configuration keeps its job.
- Kill gates
- Conditions that stop a system automatically, defined with the change rather than debated during the drawdown they were meant to prevent.
- Sim/live parity
- Replay of live sessions through the model on identical inputs, to separate a sizing error from an execution defect — two failures that look the same in the P&L and have nothing else in common.
04 / Deployment & licensing
Your infrastructure, your data.
MOCR is licensed software deployed into your environment. We are not a venue, a broker or a routing intermediary, we do not take custody of assets or hold client money, and your order flow does not pass through us.
It reads from your engines and venue accounts and writes to your own store. Nothing about the arrangement requires you to trust us with the operation itself.
- Deployment
- On-premises or in your own cloud tenancy, reachable over your existing private network. Credentials and market data stay inside your perimeter.
- Engagement
- Annual licence with a scoped implementation alongside it, support and release access included for the term.
- Integration
- Adapters for your engines and venues are built and delivered by the engineers who wrote the platform, against a written statement of work.
- Due diligence
- Architecture documentation, security review materials and reference conversations available to counterparties under NDA.
Next step
A technical conversation, not a sales call.
Bring the problem. We will tell you what it would take to solve it, and whether we are the right people to do so.