Freqtrade vs Hummingbot
Education only. Updated Nov 10, 2026. Based only on official project pages and license files (sources below).
You are responsible for every trade your agent places. TraderStacks explains how the software works; this is not investment advice, and nothing here suggests what to buy, sell or when. Agents can make mistakes, and you can lose money. Freqtrade’s homepage also says the software is for educational purposes and to use it at your own risk.
No winner declared. These are two open-source codebases people already search for by name. Which one you run, if either, depends on the job you want the software to do and how you will secure the machine and the keys. For a safety checklist that applies to both, see AI trading bot safety.
| Freqtrade | Hummingbot | |
|---|---|---|
| Official description (today) | A free and open-source crypto trading bot written in Python, designed to be controlled via Telegram or a web UI, with backtesting, plotting, money-management tools and strategy optimization by machine learning | An open-source, community-owned Python framework for crypto market makers, described on the homepage as helping you run agentic trading strategies on centralized and decentralized venues |
| License (official files, opened today) | GNU GPL v3 | Apache License 2.0 (also stated on the GitHub repository and homepage) |
| Price of the software | Free (open source) | Free (open source) |
| How it touches your money | You run it; live mode uses exchange API keys you put in the config. Dry-run does not post orders | You run it; live mode uses keys (or protocol private keys) stored encrypted on the local machine. Paper trade can run without exchange APIs for the strategy types the paper-trade guide lists |
| Documented simulation mode | Dry-run: live simulation, no trades created on the exchange, read-only exchange operations, optional fake or empty keys, simulated wallet | Paper trade: simulate without risking actual assets; default paper connectors are documented in conf_client.yml; APIs not required for several named market-making types |
| Key-permission guidance in official docs | Keys required in production; keep them secret. FAQ: live errors often involve key, IP allowlisting, or missing Spot Trading (or equivalent) permission; futures usually need a separate enablement | Recommend only read + trade keys. Does not support deposit or withdrawal; do not enable withdraw or transfer |
| Markets as documented | Crypto. FAQ: spot, plus futures on some selected exchanges; see the official exchange-specific notes for what is supported. No sandbox accounts; use dry-run | Homepage: centralized and decentralized venues. Official pages we opened today did not give a single frozen venue count we could cite, so use the project’s current connector docs |
| Skill | Official homepage strongly recommends basic coding skills and Python knowledge, and reading the source | Client quickstart covers install, a keystore password, paper trade, then connecting a live exchange when you choose to |
How official docs frame each project
Freqtrade’s feature list is organized around writing a Python strategy, downloading history, backtesting, hyperoptimization (including machine-learning tools it calls FreqAI), then Dry-Run or Live-Trade, and monitoring through Telegram or freqUI. That is a research-then-deploy loop. The Docker quickstart warns that the bundled sample strategy is a demo and reference only.
Hummingbot’s official site and GitHub README frame it as a market-making and algorithmic-trading framework, with paper-trade connectors and, on the homepage, an AI harness called Condor. We did not open Condor’s full documentation this session, so we do not describe what that harness can do beyond the homepage listing. A documented limit that matters for testing: V2 strategy controllers currently require a live exchange connection and are not supported on paper-trade connectors.
Safety overlap
Both projects expect you to secure the machine and the keys. Freqtrade documents a REST API / freqUI that should stay off the public internet. Hummingbot encrypts keys with a client password. Neither official documentation we read today tells you to grant withdrawal permissions. Walk through the safety checklist before switching either project out of its simulation mode.
Hosted alternatives (keys stored by a vendor) are a different model; see 3Commas vs Cryptohopper.
- Sources (official pages and raw license files, opened Nov 10, 2026; each returned HTTP 200)
- Freqtrade: homepage, configuration / dry-run, FAQ, exchange-specific notes, GPL-3.0 license.
- Hummingbot: homepage, paper trade, connect API keys, client quickstart, Apache 2.0 license, GitHub repository.
- Checked on
- Nov 10, 2026
- Not covered
- A performance comparison, a venue-by-venue connector audit, Condor’s full docs, or running either bot with a funded account. We did not test these ourselves this session.
Frequently asked questions
Is Freqtrade or Hummingbot better?
We do not declare a winner. Both are free, open-source projects you run yourself and connect to venues with keys you configure. They differ in license, documented focus, and how paper or dry-run mode works. Which fits depends on the workflow you want to operate and secure.
Are they free?
Yes, as open-source software. Freqtrade’s official license file is the GNU General Public License version 3. Hummingbot’s official license file, and its GitHub repository, state the Apache License 2.0. You still pay exchange fees, infrastructure, and any market-data costs the venue charges.
Do I need API keys to try them?
Not for the documented simulation modes. Freqtrade Dry-run can run without production API keys and only performs read-only exchange operations. Hummingbot’s paper-trade guide says exchange APIs are not required for Pure Market Making, Cross Exchange Market Making and Avellaneda Market Making on paper trade. Hummingbot also documents that its V2 controller framework does not currently support paper-trade connectors.
Does TraderStacks tell me which strategy to run?
No. Official sample strategies are for reference. We give no tickers, signals or strategies, and nothing here is financial advice.
Next: AI trading bot safety checklist · Freqtrade · Hummingbot · Crypto bots, safely · 3Commas vs Cryptohopper
Education only, never trade advice.
