The whole search space, and the tools to trust what you find
Community is not a trial. It runs the same Rust engine at the same speed, with no expiry and nothing withheld from the simulation itself. What Pro lifts is the ceiling on how much of the parameter space you can search at once, and it adds the diagnostics that tell you whether the result that came back is real or just the luckiest cell in the grid.
What the license unlocks
Three caps come off, and four tools appear. The caps are the ones that decide how much of a strategy you can look at; the tools are the ones that decide whether you should believe what you saw.
Sweeps without a cap
sweepsCommunity stops at 256 backtests a sweep, which is one 16 by 16 grid and not much of a map. Pro removes the number: the sweep fans out across every core you have, and sweep_columns pulls one metric across a million combinations into a numpy array without building a million Python objects on the way.
Monte Carlo without a cap
monte carloA thousand simulations is enough to see the shape of a distribution and not enough to read its tail, which is the part you actually care about. Pro lifts the limit, so probability of ruin and the far percentiles come from as many resamples as the question deserves rather than as many as the tier allows.
One-second resolution
resolutionCommunity simulates on 1-minute bars and hands back a daily equity curve. Pro runs the simulation on bars down to one second, and returns the timeseries at the resolution the engine actually ran, which is what intraday drawdown and exposure analysis need to exist at all.
Look-ahead detection
diagnosticsdetect_lookahead reads the strategy for operators that see the future, lead() and full_series_rank(), and names the signal that uses one. It then re-runs the strategy on truncated and extended windows and flags every trade that moves. A column precomputed from future bars reads the same in every window: the documentation says how to check it where it is built. A leak inflates a backtest quietly, and it does not show up in the metrics you would think to read. The exposure and risk checks beside it, check_exposure_stability and risk_check, stay free on every tier.
See the reports →Built-in walk-forward
validationOptimize in-sample, validate out-of-sample, then compare the stitched out-of-sample equity against the full backtest. Overfitting stops being a number you have to interpret and becomes a gap between two curves that you can see.
How the workflow fits together →Cross-exchange backtesting
executionRun one strategy across several venues inside the same simulation, instead of assuming that the single book you backtested against is the one you would have traded on. Fees and funding stay attached to the venue they belong to.
Databento and Massive
dataEquities, futures and options, next to the five crypto connectors Community already ships with. You bring your own vendor account and the connector handles ingestion into the Arrow store, with the same merge-without-duplicates behaviour as the CSV path.
Where each tier stops
The honest version of a pricing table is the one that makes it easy to decide not to buy. Here is every line, including the ones where the tiers are identical, and the Researcher column for what Pro does not do.
There is no watermark, no nag screen, no expiry and no artificial slowdown on the free tier. The Community sweep still fans out across every core on your machine, and a Community backtest returns the same trades as a Pro one.
So if your research fits inside 256 backtests a sweep and a daily equity curve, Community is the whole product and you should not pay for Pro until it stops fitting. The moment it does stop is usually the same moment you start caring about the tail of a distribution rather than its middle.
- +The Rust engine at full speed, with no time limit
- +All 104 indicators, the 38 candlestick patterns and multi-asset backtests
- +1-minute engine resolution (Pro goes down to 1-second bars)
- +CSV, pandas, Polars and Arrow IPC import
- +Binance, Bybit, Hyperliquid, dYdX, Bitstamp, Deribit, Yahoo Finance, Dukascopy and London Strategic Edge connectors
- +Tearsheets and export
- +Reproducible manifests, replayable bit for bit
| Capability | Community | Pro | Researcher → |
|---|---|---|---|
| Rust engine, 104 indicators, multi-asset | |||
| Engine resolution | 1m | 1s | Tick |
| Crypto connectors | |||
| MCP server | |||
| Tearsheets and export | |||
| Parameter sweep | 256 runs per sweep | Unlimited | Unlimited |
| Monte Carlo | 1,000 sims | Unlimited | Unlimited |
| Timeseries output | Daily | Up to 1s | Up to 1s |
| Exposure and risk checks | |||
| Look-ahead detection | |||
| Built-in walk-forward optimization | |||
| Cross-exchange backtesting | |||
| Databento, Massive and 0xArchive connectors | |||
| Tape ingestion, order flow by aggressor side | |||
| Real BBO at every bar | |||
| Tick-resolved fills inside bar backtests | |||
| L2/L3 book, queue position, latency | |||
| GPU acceleration |
Two ways to pay for the same license
Identical features either way. The only difference is whether you would rather pay by the month or save two of them by the year.
The license follows the subscription. Cancel and it runs to the end of the period you already paid for, then the library drops back to Community on its next check. Your installs stay where they are, and nothing you have already computed is touched.
The same license, ten months paid for twelve. One invoice a year, which is what an expense line prefers, and the same reversion to Community if you let it lapse.
Everything on this page, plus tick data with order flow by aggressor side, the real BBO at every bar, fills resolved on the tape, the L2/L3 book and GPU acceleration. $33/mo billed annually, $39 month to month, or $590 lifetime.
Activation is one command, once
Checkout hands you an activation code on the confirmation page. You run it once, and the license is fetched and stored locally from there on.
That matters more than it sounds: because the license lives on the machine and not in the code, it never ends up in a notebook you share, a repository you push, or a screenshot of a cell that happened to include your key.
Nothing about the install changes. pip install manifoldbt is the same package on both tiers, and the same code runs on both. The license only decides how far it is allowed to go.
# Once, after checkout. The code is on your confirmation page.
manifoldbt activate "your-activation-code"# Or from Python, if you never leave the notebook.
import manifoldbt as mbt
mbt.activate("your-activation-code") # once, and only once
# Every later import picks it up on its own. Nothing to
# pass, and nothing to keep in the file.
import manifoldbt as mbtFAQ
Stop tuning a corner of the map
A strategy that survives the whole grid, a walk-forward and a lookahead check is a different object from one that won a 16 by 16 search. Pro is what it costs to tell those two apart.