Crypto backtesting to paper/live automation
Both cover backtesting, paper trading, and live automation. Their common backtest was reproduced locally.
Locally testedAI TRADING INDEX
Compare 16 open-source, self-hosted AI trading tools for research, backtesting, paper trading, and automation. Rankings use official sources and reproducible local tests. Trading returns are not a ranking factor.
There is no single best tool for every job. Lumibot and VeighNa tie on broad workflow coverage, but both have heavy installs. Freqtrade and Jesse fit crypto strategy workflows, while Backtesting.py is easier for research and backtesting.

Pick the workflow first. The same tool can be a strong fit for one job and unnecessary for another.
Both cover backtesting, paper trading, and live automation. Their common backtest was reproduced locally.
Locally testedIt completed the shared backtest in the fewest setup stages among the three tested frameworks.
Locally testedOfficial sources confirm backtesting and optimization with a lower setup barrier; paper and live use remain unconfirmed.
Official evidenceOfficial sources confirm these capabilities. This task pick is based mainly on official evidence, not the shared local benchmark.
Official evidenceYes and No appear only when official sources say so. Everything else stays Not confirmed.
Ranks can tie. Each entry states the fit, the limit, and the evidence status.

Official sources cover backtest, paper, live, and agent workflows, and the rule-based local benchmark completed twice. Its breadth comes with the heaviest tested install.
Python developers who want one strategy lifecycle from backtesting to broker-connected paper or live runs, with an optional agent runtime.
People who need a small dependency set, a quick Windows install, or only a lightweight rule backtester.
The complete package is large, hit a Windows path limit here, and took more than ten minutes to install in a short-path environment.

Official sources cover factors, machine learning, backtests, local simulation, and live gateways; the common SMA benchmark also completed twice in its Lab components.
Quant developers who want factor research, machine learning, backtests, local simulation, and trading gateways in one Python platform.
People who only need a compact strategy experiment and do not want a broad modular platform.
The core and alpha dependency groups took about seven minutes to install, and the optional-module surface is substantial.

Freqtrade scores 89 in the baseline, with officially confirmed backtesting, dry-run, and live execution plus a repeatable local backtest.
Crypto strategy developers who want a CLI path from backtesting to dry-run and live automation.
People who need traditional assets, a completely offline backtest, or minimal command-line configuration.
The full dependency set, configuration, market metadata, and exchange concepts add setup and maintenance work.

Jesse also scores 89 in the baseline, covering backtesting, paper trading, and live execution with a repeatable four-step local test.
Python developers who want one crypto strategy structure across research, backtests, paper trading, and live deployment.
People who only have hourly data, want no-code setup, or do not want to maintain minute-level input.
Dependencies and data preparation are not lightweight; our local test also required import and data-granularity fixes.

Backtrader scores 84 in the baseline and reaches 90 in the easy-start scenario; it had the shortest path in the three-framework local test.
Python users who want a lightweight, controllable framework for local data and custom strategy logic.
Anyone expecting built-in data downloads, project scaffolding, experiment storage, or a polished report UI.
You must write the data loading, position sizing, experiment logging, and result export yourself.

OctoBot scores 84 in the baseline with confirmed backtesting, paper funds, live execution, local LLM support, and a visual interface.
Crypto users who prefer a visual interface and want paper trading, backtests, local LLM options, and a path to automation.
Researchers focused on traditional assets or those who want a narrow code library.
The crypto-only scope and wide feature set add configuration work; live trading still needs exchange credentials.

Hummingbot scores 77 in the baseline and covers backtests, paper scripts, and live execution, though current evidence is official-source only.
Crypto market-making and automation users who want an official paper path before connecting exchanges.
Researchers focused on equities, cross-sectional factors, or a small backtest-only library.
Controllers, executors, connectors, and long-running processes create a larger learning and operations burden.

Backtesting.py scores 76 in the baseline and 100 in the easy-start scenario, reflecting confirmed backtesting and low setup rather than broad task coverage.
Python users who want a small, readable library for quick rules-based strategy tests and parameter optimization.
Teams needing paper trading, live execution, a data platform, or a locally verified result from this site.
It covers backtesting and optimization only; data, experiment management, and execution remain your responsibility.

FinRL scores 75 in the baseline with reinforcement-learning research, backtesting, and an execution path, but a higher training burden.
Researchers who want to reproduce or modify reinforcement-learning trading experiments in Python or notebooks.
People who only need a lightweight rules-based backtest or do not plan to train models.
Data preparation, reinforcement-learning knowledge, dependencies, and training all raise the setup cost.

Vibe-Trading scores 75 in the baseline across multi-agent research, factors, backtests, and simulation; official sources explicitly exclude live execution.
People who want natural-language research, multi-agent analysis, factors, backtests, and saved reports in one local workspace.
Anyone who needs live execution or wants a small, single-purpose Python library.
Its broad, multi-service stack is harder to install and troubleshoot than a focused framework.

NautilusTrader scores 72 in the baseline with multi-asset backtesting and live execution, but a high learning burden and unconfirmed paper mode.
Engineering teams that need multi-asset, event-driven simulation and a production-oriented path to live execution.
Beginners who want the shortest route to a first small backtest.
Its production scope and large concept surface make it harder to learn than a lightweight Python library.

TensorTrade scores 71 in the baseline with a confirmed RL environment and backtesting, while paper and live execution remain unconfirmed.
Developers building custom reinforcement-learning environments, rewards, and execution simulations.
People looking for LLM role collaboration, a ready-made report, or confirmed live execution.
You must assemble the environment, data, reward, and training workflow yourself.

OpenBB enters as a financial-data platform with Python and REST access; backtesting, paper trading, and live automation remain unconfirmed.
Developers who need a consistent Python or REST entry point for financial data and research applications.
Anyone expecting a complete strategy backtester or execution bot from the same package.
It solves data access, not the backtest, agent, portfolio, or execution layers around it.

Qlib has confirmed factor, machine-learning, portfolio-research, and backtesting capabilities; paper and live automation remain unconfirmed.
Quant researchers building factors, machine-learning models, portfolios, and research backtests in one workflow.
Anyone whose first requirement is paper or live trading, which official sources do not confirm.
You must prepare data and learn Qlib's full research workflow before producing useful results.

skfolio covers portfolio optimization, model selection, cross-validation, and risk controls; trading workflow capabilities remain unconfirmed.
Researchers with signals who need portfolio optimization, model selection, cross-validation, and risk controls.
Anyone who needs an agent product or officially confirmed backtesting, paper trading, or live trading.
It is a portfolio component; orchestration, strategy testing, and execution must be added separately.

TradingAgents is built for multi-role LLM research and has confirmed backtesting, but paper and live automation remain unconfirmed and setup is high.
Researchers who want to inspect how analyst, trader, and risk roles collaborate in an LLM workflow.
Anyone who needs officially confirmed paper or live trading from the same project.
Setup is heavy: you must configure models, data sources, and several agents yourself.
If you only need research or backtesting, you do not need the setup and operations burden of an execution system. Add paper or live automation only when that is the actual job.
Crypto automation, traditional quant research, multi-asset engineering, and reinforcement learning call for different tools.
Compare setup difficulty, unknown capabilities, and evidence status. An unconfirmed field stays unknown; it does not become No.
We define the software job first, compare official capabilities and setup limits, then add local results only where the same command was reproduced. Unknown stays unknown. Trading returns never affect placement.
Here it means software used for trading research, strategy generation, backtesting, paper trading, or automation. Not every tool uses an LLM or multiple agents.
This ranking covers open-source, self-hostable tools whose basic start does not require external registration or payment. Data, models, cloud services, or trading connections can still add costs later.
Official sources confirm backtesting for Lumibot, VeighNa, freqtrade, Jesse, Backtrader, OctoBot, Hummingbot, Backtesting.py, FinRL, Vibe-Trading, NautilusTrader, TensorTrade, Qlib, TradingAgents. Unknown fields are not treated as No.
Official sources confirm paper trading for Lumibot, VeighNa, freqtrade, Jesse, OctoBot, Hummingbot, Vibe-Trading. They confirm live automation for Lumibot, VeighNa, freqtrade, Jesse, Backtrader, OctoBot, Hummingbot, FinRL, NautilusTrader. Unknown fields remain unconfirmed.
No. Trading performance and money-making claims are not ranking factors. This page ranks software fit.
The best fit changes with the job. The balanced self-hosted view is tied, while research-first and automation-first priorities produce different leaders.
We update when official capabilities, access, or local-test evidence changes materially. The page shows the latest verification date.