Measure this visit?
Accept allows Google Analytics, Microsoft Clarity and PostHog, including session recording. Reject stops their recording. Cookieless counts and server request logs stay on. What we measure
Build & AI
We check your backtest or trading bot for look-ahead, missing data, free fills and overfitting, then run it again with the fixes in. You get a written report.
Updated
A backtest that shows a profit is a claim about the past. Before money goes behind it, someone should try to break it. That is this job: we take your backtest, or the bot already running on it, and look for the ways it could be wrong.
You get a written report. Each finding names the line of code or the data that causes it, shows the effect on the result, and says how to fix it. Then we run the test again with the fixes in, so you see the number that survives.
Building a new bot is a separate job, on the algorithmic trading page.
The data. Gaps, duplicate rows, bad prints, prices from the wrong time zone. Markets or assets that stopped trading and are missing from the test, which makes the past look kinder than it was.
The clock. Every number the strategy reads has to have existed at that moment. A daily close used at noon. A revised figure used on the day the first estimate came out. An indicator computed over the whole series. Each one leaks the future into the test.
The fills. Which price the order filled at, and whether anyone was offering it. Fees, spread, slippage and partial fills. A strategy that trades often can live or die on these alone.
The number of tries. If many variants were tested and the best one kept, part of its result is luck. We count the trials and correct the Sharpe ratio for them, with the deflated Sharpe ratio that Bailey and López de Prado published in 2014. Our free calculator does the same sum in your browser.
The code that trades. In a running bot we also read the order path. What happens on a restart, a rejected order, a partial fill or a lost connection. Whether a limit can be switched off by the strategy it is meant to limit.
We sign an NDA before you send anything. Then we take read-only access to the code and the data, or copies of them. We never need keys that can trade.
We run your backtest on our side and match your numbers. A result we cannot reproduce is the first finding.
Data gaps and missing losers, look-ahead, fills nobody offered, costs left out, and the number of variants tried. In a live bot, the order path too.
Each fault gets a fix, and the backtest runs again with all of them in. You see how much of the original result is left.
The code that produces the backtest, the data it runs on or a way to get it, and the result you want checked. For a live bot, read-only access to its logs and its order history as well.
No. We tell you what the backtest supports once its faults are fixed, and how sure that number is. Whether to trade it, and at what size, is your decision.
Then the audit matters more. We check what the code does, which can differ from what its seller described, and the report says where the two differ.
Every finding comes with its fix in the report. Your team can apply them, or we can, as a separate piece of work under the build service.
Yes. We sign an NDA before you send code or data, and at the end we return or delete our copies as the NDA sets out.
Start a conversation