VectorBT review (2026)

VectorBT is the speed king of Python backtesting. Instead of looping bar-by-bar like Backtrader or Zipline, it packs entire parameter grids into NumPy arrays and runs them through Numba-compiled kernels, Rust-accelerated in PRO. An overnight grid search becomes a coffee break. For hypothesis screening, parameter sweeps, and factor research at retail scale, nothing in the open Python ecosystem matches it.

The trade-offs are real and worth stating plainly. The array-first API is genuinely hard: users consistently report the steepest learning curve of any major Python backtesting library, and the free version's documentation is incomplete. The open-source package is in maintenance mode. Active development moved to VectorBT PRO, a paid membership ($25/mo, $240/yr, or $500 lifetime as of August 2026) that unlocks a private repo, hybrid event-driven features, a far richer data layer, and proper documentation. VectorBT also, by design, executes no live trades; you bring your own data and your own execution stack.

Our verdict: a 9-grade research engine wrapped in a 3.5-grade onboarding experience. If you are comfortable in NumPy/pandas and treat backtesting as a research problem rather than a push-button product, VectorBT is one of the best value propositions in retail quant tooling, and PRO at its current early-contributor pricing especially so. If you want gentle docs, built-in execution, or a GUI, look at QuantConnect or TradingView instead.

VectorBT is a Python library for backtesting and quantitative research built by solo developer Oleg Polakow. It exists in two versions. The original vectorbt (vectorbt.dev, GitHub: polakowo/vectorbt) is published under a fair-code Apache 2.0 + Commons Clause license (free to use, source-available, not resellable) and has accumulated 8.6k+ GitHub stars. It is now explicitly in maintenance mode: bugs get fixed, new features do not land. VectorBT PRO (vectorbt.pro) is the closed-source successor, distributed as a membership that grants collaborator access to a private GitHub repository, a members-only Discord, and exclusive documentation.

The core idea in both versions is the same: represent strategies, parameters, assets, and time as dimensions of NumPy arrays, then evaluate everything at once through Numba-compiled code instead of looping through bars. That is what the project means by 'vectorized' backtesting. It also explains why VectorBT occupies a different niche from event-driven engines like Backtrader, since it is a research instrument for testing many ideas quickly rather than a trading platform. PRO extends the model into what it calls a hybrid engine, adding more realistic order types, portfolio optimization, cross-validation tooling, and a substantially larger data layer.

VectorBT's engine compiles the hot path with Numba, and PRO adds a Rust backend. The practical result, echoed across user comparisons, is that it can run roughly a thousand parameter combinations in the time a loop-based library processes one backtest. That makes it the strongest open tool for parameter sweeps, robustness checks, and factor screening at retail scale.

Accuracy depends on how you use it. The simulator models fees, slippage, and position sizing, and PRO adds granular order types (limit, stop-loss, take-profit) plus event-projection and pattern tools. Walk-forward analysis is supported in both versions via rolling splitters, with PRO shipping a more complete cross-validation module. That module matters: a tool this fast at optimization makes overfitting trivially easy, and the splitters are your main defense.

The honest caveat is that pure vectorization struggles with path-dependent logic. Strategies whose next order depends on intricate intrabar state are harder to express faithfully than in an event-driven engine, and naive implementations can hide look-ahead bias from users who don't understand the array model. PRO's hybrid callbacks close much of this gap, but they require writing Numba-compatible code. This library rewards engineering skill, and demands it.

VectorBT bundles no market data. It is bring-your-own-data by design, operating on any pandas/NumPy time series you feed it, from daily bars down to individual ticks.

The open-source version keeps things minimal: a built-in Yahoo Finance wrapper plus whatever you load yourself. VectorBT PRO is where the data story gets serious. Verified from the official features page (August 2026), PRO ships unified downloaders for crypto exchanges via CCXT (Binance, Bybit, KuCoin, Bitfinex), brokers-as-data-sources (Alpaca, Interactive Brokers), and market data vendors (Polygon.io, TradingView, Databento, Alpha Vantage, Nasdaq Data Link), alongside local formats (CSV, HDF5, Parquet, Feather) and storage backends (ArcticDB, DuckDB, PostgreSQL, LMDB caching).

Two things to note. First, the connectors are interfaces, not subscriptions: paid sources like Polygon or Databento still require your own API keys and plans, so budget for data separately if you need clean intraday or tick history. Second, the broker integrations are for data only, and connecting to Interactive Brokers through VectorBT does not give you order execution. For a research library this ecosystem is about as good as it gets, which is why we score data quality 6.5 rather than lower despite nothing being bundled.

Verified on the official membership page in August 2026:

Tier	Price	Notes
Open source	$0	Maintenance mode; fair-code license
PRO Monthly	$25/mo	Cancel anytime
PRO 12-Month	$240/yr	Effective $20/mo; listed as reduced from $300
PRO Lifetime	$500 one-time	Crypto accepted on request
Organization	Custom	Contact the developer

Mechanics worth knowing: monthly subscribers can convert to lifetime by crediting half of everything they have already paid toward the $500 (minimum $150 remaining payment). Payments run through GitHub Sponsors, Ko-fi, Patreon, Stripe, Paddle, or Gumroad depending on tier. The site explicitly frames current prices as a limited-time early-contributor offer that will rise as membership milestones are reached. Treat these numbers as a floor and check the live page before budgeting.

Context matters for value. $240/yr is roughly the cost of two months of a mid-tier commercial charting SaaS, and the $500 lifetime undercuts a single year of most professional research platforms. The catch is the membership model itself: subscription tiers grant access to a private repo, and access ends when payments stop. Lifetime removes that risk but concentrates it in a single-maintainer project instead.

Patterns across r/algotrading threads, quant blogs, and comparison write-ups are remarkably consistent.

The praise centers on speed and depth. Users who invest the time describe VectorBT as being in a different performance class from Backtrader, Zipline, or backtesting.py. The standard line: it does in seconds what other libraries do in hours. The developer's responsiveness and the PRO Discord community also draw repeated positive mentions, which is unusual for a one-person project.

The criticism clusters around three themes. First, the learning curve: even experienced Python developers report needing weeks to think in VectorBT's array-oriented model, and beginners are routinely told to start with Backtrader or backtesting.py instead. Second, the open-core drift. Reviewers note that the free version's documentation is incomplete and no longer actively developed, with the good tutorials, release notes, and new features behind the PRO paywall. Some longtime open-source users call that a bait-and-switch; others call it a fair price for sustained development. Third, the scope boundary: newcomers are sometimes surprised that a 'trading' library places no trades, and you must build your own execution layer.

We found no significant pattern of accuracy complaints. Disputes tend to be about user error in the array model rather than engine bugs.

Choose VectorBT if you are comfortable in Python, NumPy, and pandas; your bottleneck is research throughput rather than execution; and you want to sweep large parameter spaces, run walk-forward robustness checks, or screen factors across many assets. Crypto quants are especially well served: the CCXT-based data layer in PRO and tick-level support map directly onto that workflow. The $500 lifetime tier is compelling for anyone who expects to do serious research for more than two years.

Skip it if you are new to programming (start with backtesting.py or Backtrader, slug: backtrader), want an all-in-one platform with hosted data and live execution (QuantConnect, slug: quantconnect), or prefer visual, no-code strategy testing (TradingView, slug: tradingview). Options traders should also look elsewhere, because VectorBT has no native options modeling.

A realistic adoption path we see work: prototype a single-asset idea in the free open-source version to learn the array model; if the speed advantage matters to your process, move to PRO 12-Month for the documentation and data layer; convert to Lifetime once the library is embedded in your workflow. Budget separately for data (Polygon, Databento, or exchange APIs) and, if you deploy live, for building or buying an execution layer. VectorBT will never do that part for you.