Two open-source self-hosted projects with very different market scope and strategy assumptions.
Passivbot provides a specialized futures engine and configuration model. Freqtrade provides a more general strategy interface and research toolchain. Both keep operations local and require users to secure credentials, infrastructure and deployments.
| Research factor | Passivbot | Freqtrade |
|---|---|---|
| Expert Score | 72/100 | 78/100 |
| Trust Score | 73/100 | 73/100 |
| Risk Level | Moderate | Moderate |
| Evidence Confidence | High | Moderate |
| Product Architecture | Open Source · Self-Hosted | Open Source · Self-Hosted |
| Current Availability | Active | Active |
| Execution Environment | User Infrastructure | User Infrastructure |
| Source Model | Open Source | Open Source |
| Technical Requirements | User-managed host, updates and operational security | User-managed host, updates and operational security |
| Custody Model | Funds remain at exchanges; the runtime and credentials remain on user-controlled infrastructure. | Funds remain at connected exchanges while credentials and the runtime remain on user-controlled infrastructure. |
| Pricing | Free public-domain software; infrastructure, data, funding and exchange fees remain user costs | Free under GPL-3.0; users pay infrastructure, data and exchange costs |
| Free Plan | Yes | Yes |
| Supported Exchanges | Binance, Bybit, Bitget, OKX, Gate.io, KuCoin, Hyperliquid | Binance, Bybit, OKX, Kraken, KuCoin, Gate.io, Bitget, Hyperliquid |
| Bot Types | Perpetual Futures, Recursive Grid, Trailing Entries and Exits, Portfolio Optimization | Custom Python Strategies, FreqAI Models, Spot Trading, Futures Trading |
| Security Score | 74/100 | 78/100 |
| Transparency Score | 88/100 | 84/100 |
| Features Score | 78/100 | 94/100 |
| API Trading | Yes | Yes |
| Withdrawal Access | Not required; use trading permissions without withdrawals | Not required; configure trade-only exchange permissions |
| Paper Trading | Yes | Yes |
| Backtesting | Yes | Yes |
| Mobile App | – No | – No |
| Concerns Found | 2 documented | 3 documented |
Key differences in practice
Architecture, operating responsibility and evidence matter alongside the feature list.
Strategy scope
Passivbot's current architecture is purpose-built for perpetual futures, including recursive Grid and trailing behavior. Freqtrade supports user-authored directional strategies across supported spot and futures venues. Similar self-hosting does not make their trading assumptions interchangeable.
Backtesting and optimization
Both expose historical testing and parameter optimization. Passivbot's optimization is closely coupled to its futures position model; Freqtrade's pipeline supports strategy backtests, dry-run and optimization across custom Python logic. In both cases, overfitting and unrealistic execution assumptions remain central risks.
Security and technical requirements
Credentials remain on user infrastructure, improving local control but creating responsibility for file permissions, dependencies, process isolation, updates and uptime. Passivbot also combines Python and Rust components; Freqtrade expects comfort with Python, containers or comparable deployment administration.
Cost and fit
Neither charges a software license fee. Compute, data, exchange fees, funding and operator time still apply. Passivbot fits experienced perpetual-futures users; Freqtrade fits developers who want a broader programmable strategy framework.
Material limitations
Passivbot's averaging behavior can amplify liquidation and leverage risk. Freqtrade requires the user to supply and validate strategy logic. Neither repository, backtest engine nor optimizer establishes live profitability or operational safety.
Features and target users
The scores are comparable; the workflows are not identical.
Passivbot
Version 8 combines Python configuration with Rust execution components, recursive grid and trailing behavior, backtesting and multi-objective optimization for perpetual futures.
Best aligned with- Experienced quantitative futures users
- Operators comfortable with Python, Rust and servers
Freqtrade
Freqtrade combines Python strategies, historical data, backtests, hyperoptimization, dry-run, FreqAI and live execution in one self-hosted system.
Best aligned with- Python strategy developers
- Users who want local control
Security and custody
Permissions and architecture matter more than security slogans.
Passivbot
Passivbot's public code and local credential boundary improve inspectability, but users remain responsible for secure files, dependencies, host access and exchange permissions.
Funds remain at exchanges; the runtime and credentials remain on user-controlled infrastructure.
Security score 74/100Freqtrade
Freqtrade provides strong visibility and local control, while explicitly warning that its web interface should not be directly internet-exposed.
Funds remain at connected exchanges while credentials and the runtime remain on user-controlled infrastructure.
Security score 78/100Pricing, bot types and limitations
Passivbot
Pricing: Free public-domain software; infrastructure, data, funding and exchange fees remain user costs
Bot types: Perpetual Futures, Recursive Grid, Trailing Entries and Exits, Portfolio Optimization
Important limitations- High technical burden
- Specialized derivatives scope
Freqtrade
Pricing: Free under GPL-3.0; users pay infrastructure, data and exchange costs
Bot types: Custom Python Strategies, FreqAI Models, Spot Trading, Futures Trading
Important limitations- Requires Python and operations knowledge
- Local UI exposure risk
Sources used for this comparison
The comparison reuses the structured product research; provider evidence establishes product claims but does not independently validate them.
Passivbot
- Passivbot repository (Documentation)
- Passivbot releases (Documentation)
- Passivbot optimization documentation (Documentation)
- Passivbot license (Terms)
Freqtrade
- Freqtrade repository (Documentation)
- Freqtrade releases (Documentation)
- Freqtrade installation (Documentation)
- Docker quickstart and UI warning (Security Documentation)
Different workflows create different trade-offs.
Passivbot is the more coherent specialist for its documented perpetual-futures workflow; Freqtrade is the more flexible general Python framework. Market type, leverage competence and desired strategy freedom should drive the choice.
Scores evaluate product quality and evidence, not expected returns. Confirm current prices, eligibility and API scopes before connecting an exchange.