// POLYMARKET BACKTEST · THE REAL ARCHIVE

Find out if your strategy works.
Without building a data pipeline.

Paste a strategy in Python or Node.js and it runs against real Polymarket and Predict.fun ticks — settlement feed, order books, trade prints — inside a sealed sandbox. You get a backtest report: an equity curve, every fill priced against the depth that was really resting, and a settlement cross-check per market. No subscription and no pipeline to build. Billed per market-day scanned, so you pay for what you actually test.

write a strategyread the SDK →

Not ready to spend anything yet? Install the SDK, download the free sample archive and replay on your own machine — the same engine, so what runs locally runs here unchanged. run it locally →

How a run works

Four steps. You paste text files — we do not take zip uploads or repo links.

01

Paste your files

Up to 6 text files in the editor below. We do not accept zip files or repository URLs, so there is nothing on our side to unpack and no install hook to run.

02

One entry point, our clock

You implement a handler. We drive it tick by tick in event-time order, replaying the settlement feed, book deltas and trade prints in the order they arrived. Future rows are not in the process yet, so look-ahead is not something you have to be trusted about.

03

Sealed sandbox

gVisor container, no network, read-only filesystem, no environment variables, pinned dependency set, hard CPU and wall-clock limits. A run that tries to reach the internet fails loudly rather than silently succeeding.

04

What you get back

Equity net of modelled slippage, every fill against the depth that was actually resting, a settlement cross-check per market, and one zip holding every CSV, the JSON report and the checksums.

No strategy to test yet? Start from what the smart money is trading on PMWallets →, our Polymarket smart-money wallet leaderboard.

Write it here

Up to 6 text files, 256 KB total — enough for a strategy, its parameters and a helper module. We deliberately do not accept archives or repositories: nothing is unpacked, nothing is fetched, only the files you can see below ever reach the runner.

entry 2 / 6 files · 2.8 / 256 KB

SCOPE

ms

How late your orders reach the book

QUOTE

venue
polymarket
assets
BTC
market-days
—
cost—

Leave the page and the archive lands in your inbox as a signed link. Only used for this run; no list, no marketing.

What comes back

A finished report for a naive mean-reversion strategy on BTC 1h Up/Down. The whole thing archives to a single zip — CSVs, JSON report, coverage and checksums — so you can drop it straight into a notebook.

Sample report

● COMPLETErun_9f4c21 · python@3.1460 market-days · 41.2 GB scanned
NET PNL+$2,861
WIN RATE / PROFIT FACTOR71.7% / 1.09
MAX DRAWDOWN-$2,202
PEAK CAPITAL / RETURN—
SHARPE / BRIER2.07 / 0.203
TRADES / MARKETS325
RETURN / $ TRADED2.5%
AVG P&L / CONTRACT1.9¢
UNFILLED SIZE0.0%
AVG HOLD / WORST RUN0m / 4
TOTAL TRADED+$113,412
TIME IN MARKET—
$4.1k-$962$007-2209-09
marketsideentry_pxexit_pxsizepnl
—0x000000DOWN0.711.00500.00+$143
—0x001eefUP0.841.00500.00+$79
—0x003ddeDOWN0.851.00500.00+$75
—0x005ccdUP0.611.00500.00+$196
—0x007bbcUP0.731.00500.00+$132
—0x009aabDOWN0.851.00500.00+$74
—0x00b99aUP0.790.00500.00-$395
—0x00f778UP0.770.00500.00-$388
—0x011667UP0.850.00500.00-$427
—0x013556UP0.621.00500.00+$191
—0x015445DOWN0.541.00500.00+$227
—0x017334DOWN0.801.00500.00+$100
↓ run_9f4c21.ziptrades.csv · equity.csv · calibration.csv · fills.csv · report.json · coverage.json · sha256sums.txtstrategy report kept for 7 days

Before you paste anything

Why no zip or Git upload?

Because unpacking untrusted archives and running install hooks is the part that actually gets people owned. Six pasted files cover almost every real strategy. If yours genuinely needs a package tree, message us and we will sort it out by hand.

Who can see my code?

The runner, and nobody else, while it executes. Files are encrypted at rest and used for no other run. We do not train on submitted strategies and do not reuse them. Report archives are kept for 7 days.

Is this the same data you sell?

The identical files, byte for byte, with the same checksums. A backtest here and a backtest on your own machine after subscribing read the same bytes — that is the point of offering it.

What if the run fails?

A crash, a timeout or a compile error costs nothing; credits are only spent on a run that produces a report. The build log and stderr come back either way so you can fix it.

Running something big, or want the runner on your own machine against files you already bought? Talk to us — we also settle in USDT.