Hosted DCA, grid and signal bots over nine exchanges, with your keys on their servers.
Crypto Trading Bots & Execution SDKs
Automation that keeps running after you close the laptop — and the connector libraries the rest of this catalogue is quietly built on.
Last updated
What this category is
Software that places orders without you watching, and the libraries that software is built on. Two kinds of buyer share the page: somebody who wants a strategy running unattended, and somebody who is writing that strategy's plumbing and needs one client that speaks to forty venues.
The boundary against backtesting libraries runs through what the tool is for, not what it can do. Almost everything here can backtest, and almost everything there can place an order. A framework people install to find out whether an edge survives belongs there; one they install to keep a market-making quote alive belongs here.
The split that decides everything else
Every card on this page falls on one side of a single line, and it is a custody line rather than a technical one: does somebody else hold a key that can trade your account?
Hosted, keys on the vendor's servers. 3Commas, Cryptohopper, Bitsgap, OctoBot Cloud and CoinAPI EMS. You paste an exchange key into a web app, the vendor's infrastructure runs the strategy whether or not your machine is on, and the key sits in their database for as long as the subscription lasts. That is not a flaw — it is the entire product, and it is the only way a bot keeps quoting while your laptop is shut.
Self-hosted, keys on your machine. CCXT, ccapi, Hummingbot, OctoBot, Passivbot, GoCryptoTrader, Gunbot, dYdX v4 Clients and the Hyperliquid Python SDK. Nobody else can reach the account, and nobody else is keeping it up either. The self-hosted list is the same cut taken across the whole catalogue.
Self-hosted is not the same claim as open source, and two cards here prove it. Gunbot is a signed binary you install and license against an ERC-20 wallet — you own the deployment and cannot read or fork what is executing your strategy. dYdX v4 Clients publish their source and ship it under a custom licence, not the AGPL their README badge and package metadata claim, whose grant terminates automatically if you fall out of step with the venue's terms of use. Running it yourself answers the custody question and leaves the audit question open.
What the money is when the product is free
Most of this page costs nothing, and almost none of it is unfunded. Five mechanisms do nearly all of the paying, and who pays for your free trading bot works through each one and how to find it in a vendor's own documentation in about ten minutes. Two of them are worth naming here because they are visible on the cards.
A builder fee is the one that comes out of your fill. CCXT adds one basis point on top of the exchange's own fees on seven DEX venues, on by default, switched off with a single option. The Hyperliquid Python SDK does the same on its one venue, also default-on and also switchable. It is documented in both cases and it is still a charge most readers will not have priced, because it does not appear on any pricing page — there is no pricing page.
Everything else comes out of fees you were already paying. Exchange API-broker rebates fund CCXT; the Hummingbot Foundation is paid by venues for maintained connectors and sponsorships, and four of the referral links in its README advertise a fee discount to you as well; OctoBot names nineteen exchange partners; 3Commas routes every sign-up button on its exchanges page through affiliate codes. None of that is hidden and none of it is disqualifying. It is simply the reason a particular venue is the default in the setup guide, and it is worth knowing before you conclude that the default was chosen on latency.
Two cards appear to take nothing at all. Barter and GoCryptoTrader carry no referral links, no sponsor banners and no broker programme in their READMEs — GoCryptoTrader asks for a Bitcoin donation instead. On a page where the normal funding model is the venue, that is unusual enough to be worth stating.
The headline prices do not compare
The hosted platforms cluster within a few dollars of each other at the entry tier and are metering three different things: bot types on one, a single bot whose effort scales on another, bot counts per type on a third. Two people with identical strategies land on different vendors, and the plan you need is decided by how many positions you intend to have open at once and in how many shapes — not by which strategies you want. 3Commas vs Cryptohopper vs Bitsgap converts all three into the same unit; OctoBot vs Passivbot does the equivalent job on the self-hosted side, where the price is zero and the thing being metered is your attention.
One card is not in that market at all. CoinAPI EMS is an institutional execution API billed by the account-hour rather than by the month, with TWAP and VWAP over twenty-six destinations — the shape of product the trading terminals page is full of, filed here because it is bought to be driven by code.
The connector layer is the load-bearing part
Most of this category does not talk to exchanges itself. It depends on a connector library that normalises forty REST dialects into one call, and that dependency is invisible on the feature page. It matters for two reasons.
The exchange count you are reading is usually the connector's, not the product's. A framework advertising a hundred venues is counting what its dependency supports, and support in that list means "an adapter exists", not "somebody traded through it last month".
The connector's maintenance status, not the framework's, decides whether your venue keeps working. A venue changes an endpoint, the connector lags, and the framework you chose for its active development is suddenly unable to reach the exchange holding your balance. It is also where the rate limit is enforced or not — a connector that does not throttle on your behalf will get the key banned by the venue rather than by the framework.
What else actually decides the choice
What the paper-trading mode actually simulates. Dry-run against live prices and backtest against history are different claims, and neither models what your own order does to the book.
Whether it models perpetual funding at all. Funding is paid every few hours and is one of the two largest cash flows on a leveraged position. An engine that never charges it will show an automated perp strategy earning money it would not have earned, and the same defaults problem set out on backtesting libraries applies to the backtester bolted into a bot — usually more so, because it was not the reason the product was built.
Whether your own code can reach it. A hosted platform with no API, no webhooks and no TradingView execution is a closed box however good the bots are, and that is a real position several vendors take. If your stack has to talk to the platform, it eliminates candidates before anything else is considered.
What is not here
Products that sell signals, calls or managed allocation. This catalogue lists software people run against their own keys and their own decisions; a subscription that tells you what to buy is advice, and the duty that comes with it is not one an unaffiliated catalogue can carry.
Copy-trading features inside a bot are a capability flag, not an exclusion — the line runs through whether the vendor's business is publishing the calls, not through whether the software can follow somebody else's.
What this category looks like
Counted across the 16 cards on this page, not quoted from anyone.
- Free tier
- 14 of 16
- Cheapest paid month
- median $29, across $9.99 to $999 — from the 7 cards that publish a monthly price
- Has a "call us" tier
- 2 of 16
- Publishes no tiers at all
- 9 of 16
- Open source
- 8 of 16
- Runs on your own machine
- 10 of 16
- Ships an MCP server
- 4 of 16
All 16 tools in Bots
Compiled from each vendor’s own documentation, pricing page and terms — no card here is marked hands-on yet.
Showing 16 of 16
Multi-exchange trading workspace — smart orders, scanners, bots and a journal.
Rust trading engine and market-data streams — live execution is a trait you implement.
Hosted grid, DCA and futures bots on seventeen venues, with no API and no webhooks.
Header-only C++ market data and execution for 30 venues, on a Bloomberg-shaped API.
One MIT client for 104 crypto exchanges, 76 of them over websocket.
One order model over 26 exchange destinations, TWAP and VWAP, priced per account-hour.
Hosted spot bots built in forms, one bot per subscription, with a marketplace attached.
Four language clients for one perp DEX, under a licence that is not the one on the badge.
A Go trading engine for 22 exchanges that has never cut a release or a tag.
A closed-source bot you install once, licensed against an ERC-20 wallet you control.
Apache-2.0 Python framework for running market-making bots on CEXs and DEXs.
The official Python client for signing and sending orders on one perp DEX.
GPL-3.0 Python bot with a web interface for grid, DCA, basket and TradingView strategies.
The OctoBot engine hosted by the vendor, from free to $29.99, with no backtester at all.
A contrarian perp market maker you configure in JSON and leave running for months.
Head to head
Background
How this part of the industry works, rather than which product to pick.
How to
One task each, answered with cards from this listing.
The words on these pages
Defined once, as this catalogue uses them.
FAQ
What is the difference between a trading bot and a backtesting library?
What you buy it for. A backtesting framework answers whether a strategy had an edge; a bot keeps placing orders while you are asleep. Several products do both, and they are listed here when the automation is the reason people install them.
Do free crypto trading bots exist?
Most of the self-hosted ones are free and open source — you supply the server, the exchange keys and the strategy. The money in this category is in hosted tiers, exchange referral rebates and paid strategy marketplaces, so read who is paid by whom before reading the feature list.
Does this catalogue list bots that trade for you automatically?
It lists software you run against your own keys and your own strategy. Products whose business is selling calls, signals or managed allocation are out of scope — that is advice, not tooling, and it comes with a different duty to the reader.
Is a self-hosted bot safer than a hosted one?
It is more auditable, which is not the same thing. On a self-hosted bot nobody else holds a key that can trade your account, and on most of them you can read exactly what the code does with it. In exchange you own the server, the patches and the key file on disk. The failure mode moves from trusting a vendor to trusting your own operations — and self-hosted does not automatically mean readable, because two of the products here run on your machine without publishing their source.
What should I check before pasting an exchange key into a bot?
Five things, in this order. That withdrawal permission is off and IP allowlisting is on, because a trade-enabled key is the account short of moving coins out. Where the key is stored — your disk, your browser, or the vendor's database. Whether the vendor has ever disclosed a key-exposure incident, since a published one is more track record than silence. Whether the bot adds a fee to your fill or a broker code to your order. And whether you can revoke every key at once from one screen when something looks wrong.