Backtesting software / Vectorbt
Vectorbt: backtesting workflow, data and limits
Array-oriented portfolio research using signal/order functions, fees, fixed fees and slippage. Readable records support reproducible inspection.
Selected workflow
No software licence fee
Fair-code with CommonsClause; PRO/data separate
Rules: Code
Data: You provide arrays/data; no instrument data licence included
- Stocks: Verified workflow
- Forex: Not established
- Futures: Not established
- Options: Not established
Cost settings: Documented; verify defaults and instrument settings
Result access/export: Documented; format and implementation below
Programmatic readable records; conversion/export is code-driven, not a hosted CSV workflow.
Limits that can change a result
Fair-code terms restrict resale of products mostly consisting of the software. Generic price arrays do not imply full Forex margin, futures multiplier or options lifecycle accounting.
Do not infer a fill model or contract lifecycle from a chart symbol alone. Historical coverage, data adjustment, sessions, time zones, commissions, position sizing and execution settings should be written down with each run. The same entry rule can produce different results under different conventions.
A test task you can reproduce
This is a suggested acceptance task, not a provider test that we performed. Save source code or rule settings, the data identifier, parameters and export. If the tool cannot accept a synthetic dataset, use an explicitly identified historical slice and record what cannot be independently controlled.
Official evidence
- Vectorbt portfolio API — Python array/signal/order simulation with fees, fixed_fees and slippage; readable records. Explicit timing and instrument/margin semantics required.
- Vectorbt licence terms — Fair-code Apache 2 with CommonsClause. Free use does not permit selling products/services mostly consisting of the software. Do not label this unrestricted open source or confuse with paid PRO.
- Vectorbt usage examples — Stock-price examples and readable records in a Python array workflow; not evidence of a complete derivatives engine.
What this profile does not establish
Published features do not establish current uptime, execution quality, predictive value, suitability or profitability. Trial limits and paid data can differ from the selected software licence. We have not opened accounts, purchased licences or run the named tool’s native imports/exports. The source register makes that boundary explicit.
Compare this workflow · Trace our own controlled SMA model · Read definitions