Preview: synthetic example. Nothing here uses real accounts or real trades, and the grading shown is not yet available.
Rerun a bot's report against your rules.
Matchstick checks a bot's fills against a prop firm's published rules and writes a report the firm can rerun with the same engine build. If your firm allows bots, someone on your compliance or trade-conduct team decides which ones to trust, and today that is done case by case. I'm building Matchstick so a trader can hand that person a report they can rerun themselves. The rule checks run in my private build today. Everything on these pages uses synthetic data, and a pilot runs on your own rule text.
No firm has agreed to rerun a report yet.
Works today
- Replay a recorded order-book session one event at a time, forward and back.
- The same session at the same point gives the same state, every time.
- A session exports as a file that carries where its data came from.
- In a private build: a bot's recorded fills are checked against a rule set. Each rule gets a pass or a miss, with the minute it broke and the reason. The check needs the fills, never the bot's source code.
- Each run is saved as a package with an id. Rerun it with the same engine build and it says the result reproduced, or names the input that changed.
- A report built on a firm's published rules lists the rules it did not check.
A match means the computation repeats. It does not mean the strategy is good, and it does not predict live fills.
Planned
- A build you can run without me. There is no public download yet.
- Seeing the order book at the moment a rule fired, in Replay. The mock-ups below show the idea.
- Settling edge cases with you in a pilot: ties, session boundaries and partial fills.
- What you receive and how long a rerun takes, written down with you in a pilot.
How a firm reruns a report today Works today
This works in a private build.
- The trader hands you the report package. It is built from recorded fills, never the bot's source code.
- You run the check with the same engine build the package names. For now, that build comes from me.
- It says the result reproduced, or names the input that changed.
Planned Opening the package in Replay to see the same grade, a build you can run without me, and what you receive and how long a rerun takes, written down with you in a pilot.
A real report on synthetic data
This is the engine's own output. The rules are made up and the bars are synthetic, and the run misses its daily loss limit. It names no firm.
Planned: the same result in Replay
These are mock-ups on a made-up account trading a made-up instrument. They show a rule result inside Replay, at the event where it fired. This view is not built yet.
Planned: reviewing a disputed breach
This is an idea, not a feature, and it is not built. A replayable record would let a trader and a firm open the same record and look at the same moment. Matchstick makes no claim about how any dispute turns out.
Three one-page resources
- How a grade is reproducedRule types, and where firms' rules differ.
- What stays whereWhat the app keeps in the browser and what the form stores.
- A pilot, in four stepsWhat you send, what I show, what you decide.
Each page prints on one sheet. Forward the link or the PDF to whoever needs it.
Talk to me about a pilot
Pilots are free while Matchstick is in preview.
We store what you type here (name, work email, firm, your line) for up to 180 days, plus the page you came from. We do not store any session data.