Exchange Failover Bots: How to Compare Your Options

November 17, 2026Updated November 19, 202612 MIN8 views
Exchange Failover Bots: How to Compare Your Options

No mainstream crypto trading bot offers a one-click switch that moves your positions from a failed exchange to a healthy one. What exists is a set of continuity features: tolerance for API errors, orders that live on the exchange itself, several exchange connections run side by side, and risk limits that act when the bot cannot. Darkbot is the option we recommend here because it connects to multiple exchanges through API keys, runs several bots at once, and pairs automation with structured risk controls and human oversight. That combination is what continuity depends on in practice.

This comparison explains what failover really means for a bot, sets out the three main approaches (self-hosted software, hosted platforms, and Darkbot), and gives a checklist for the setup you should have in place before you rely on any of them.

Darkbot
app.darkbot.io
Build More Resilient Exchange Coverage
Connect multiple exchanges with API keys, run several bots at once, and use Darkbot’s risk management tools to support trading continuity.
Run paper trading

TL;DR

  • “Failover” for a trading bot usually means surviving an exchange or connection failure without leaving unmanaged risk. It rarely means automatically moving funds to another venue.
  • Capital sits on one exchange at a time. Real continuity comes from splitting capital across exchanges, running separate bots per exchange, and keeping protective orders and risk limits in place.
  • Self-hosted software such as Freqtrade has no license fee, but you own the server, uptime and monitoring. A hosted platform moves that work off your plate.
  • Darkbot connects to major exchanges via API keys, supports multiple simultaneous bots, backtesting, paper trading and risk management tools. Standard is $12.50 per month and Premium is $25.00 per month.
  • Whatever you choose, use trade-only API keys with withdrawals disabled and set alerts before you scale position size.

What exchange failover means for a trading bot

In IT, failover means a standby system takes over when the primary fails. Applied to a crypto bot, the idea breaks into four separate problems, and each has a different solution.

The exchange API is slow or returning errors. The bot cannot read prices or place orders. A well-built bot retries, backs off, and avoids sending duplicate orders when the connection returns.

The exchange is down or halts trading. Your funds and open positions are held by the exchange. No bot can move them while it is offline. The only protection is what was set before the outage: stop orders resting on the exchange, modest position size, and exposure spread across venues.

The bot itself stops. The server crashes, the network drops, or the process hangs. Orders already on the exchange continue to exist, but nothing manages them. A hosted service or a monitored server addresses this.

Your API key stops working. Keys can expire, be revoked, or be blocked when your IP address changes and the key is restricted to a list of allowed addresses. This is the most common self-inflicted outage and the easiest to prevent.

Seen this way, the useful question is not “which bot fails over to another exchange?” It is “which setup leaves me with the least unmanaged risk when one of these four things happens?”

Four bot failure modes and their mitigations

Why a bot cannot simply move to another exchange

A centralized exchange holds your balance in its own ledger. A position on Exchange A has no connection to Exchange B. Moving to B requires a withdrawal, a blockchain transfer, confirmations and a deposit, and withdrawals are often unavailable exactly when an exchange is in trouble. For that reason, responsible automation avoids giving a bot withdrawal rights at all (see the security section below).

Why a bot cannot simply move to another exchange

What a bot can do is operate on both venues in advance. If you hold capital on two exchanges and run one bot per exchange, an outage at one leaves the other running. This is a pre-positioned design, not a live transfer. It also means each exchange needs its own API key, its own risk limit and its own monitoring.

The three approaches compared

Criterion Self-hosted software (Freqtrade) Hosted multi-exchange platforms Darkbot
Software cost No license fee; you pay for a server and exchange fees Subscription Free tier, Standard $12.50 per month, Premium $25.00 per month, Enterprise on request
Who keeps it running You The provider The platform
Multiple exchanges at once Yes, supported per configuration Depends on plan Yes, multiple simultaneous bots across supported exchanges
API key handling Keys stored on your own machine Keys stored by the provider Keys connected through the platform interface
Backtesting and paper trading Available Varies by product Included features
Risk controls You configure and maintain them Provider tools Risk management tools and real-time analytics
Support Community Provider Personalized support

Self-hosted software: Freqtrade

Freqtrade is open-source software you run yourself. According to a professional review of Freqtrade published in October 2026, it carries no hosted runner, signal subscription, commercial license or token. Your costs are a server and exchange fees. The same review states that it holds your exchange API keys and calls the exchange directly. Its spot support covers Binance, BingX, Bitget, Bybit, Gate, HTX, Hyperliquid, Kraken, OKX and others, and its futures support covers Binance, Bitget, Bybit, Gate, Hyperliquid, Kraken and OKX.

The fit is a technically confident trader who wants full control. The continuity burden is also fully yours: a virtual server that restarts after a crash, a process supervisor, log monitoring, an alert if the bot goes silent, and a plan for key rotation. The software gives you tools; the failover design is your own project. For a part-time trader, that operational work is often the real cost, more than the software license.

The key storage point deserves attention. A self-hosted bot keeps credentials on a machine you must secure. This crypto account security guide for beginners covers how self-hosted bots store exchange keys and connect directly to accounts, which is worth reading before you place a key on any server.

Hosted multi-exchange platforms

Hosted platforms such as 3Commas, Cryptohopper, Bitsgap and Pionex run the bot on their infrastructure, so a crash on your laptop or home network does not stop it. Their exchange coverage, bot types and plan limits differ, and each publishes its own current pricing on its own site. Compare them on the criteria in the checklist below rather than on headline features. If you already use one of them, the same checklist applies to your current setup.

Darkbot

Darkbot is an AI-based crypto trading automation platform. It is not a signal service: it executes rule-based logic that you configure, and the AI layer is used for consistency and probabilistic pattern evaluation, not for prediction. For a continuity-minded trader, the relevant capabilities are these:

  • Exchange integration through API keys. You connect your own exchange accounts. Read our guide to API-based exchange integration for how the connection works.
  • Multiple simultaneous bots. You can run separate bots on separate exchanges, which is the practical way to avoid depending on one venue.
  • Risk management tools and real-time analytics. Limits and monitoring sit in the same interface as your strategies.
  • Backtesting and paper trading. You can run a configuration against history and in simulation before it touches real capital.
  • Direct order routing and human oversight. These are part of how we approach security and reliability.
  • Portfolio management and automated rebalancing. Allocation across accounts can be managed in one place.

The Free plan gives you a limited-feature entry point. Standard is $12.50 per month and Premium is $25.00 per month, with an Enterprise tier and a 14-day money-back guarantee. Details are on the Darkbot pricing page.

How each approach handles the four failure types

Failure What protects you Where Darkbot fits
API errors or latency Retry logic, no duplicate orders, monitoring Platform-managed execution with real-time analytics
Exchange outage Pre-split capital, small size per venue, protective orders set in advance Multiple bots across exchanges, risk tools
Bot or server stops A supervised server or a hosted service No server of your own to maintain
Key problems Trade-only keys, IP restrictions, rotation Key integration guides and security practices below

One point applies to every row. Protective orders placed on the exchange (such as a stop-loss that lives on the exchange rather than inside the bot) continue to work if the bot goes offline, provided the exchange itself is up. Check how each strategy places its exits before you let it run unattended.

A continuity checklist before you rely on any bot

This is the setup that matters more than the choice of software.

1. Lock down the API key

Create a key with trading permission only. Leave withdrawals disabled. If the exchange supports it, restrict the key to the IP addresses your bot uses. Darkbot has published material on this: what API key security means in automated trading and how IP restrictions are supported across exchanges. A key that cannot withdraw limits the damage from a leak to trading activity on that account.

2. Split capital deliberately

Decide in advance what share of your capital sits on each exchange. For a nano-capital account of a few hundred dollars, two exchanges may be more than you need, and the exchange minimums may dominate. For larger accounts, two or three venues reduce single-point dependence. Whatever the split, size positions so that a frozen exchange does not put the whole account at risk.

3. Define risk limits that do not depend on the bot

Set a maximum position size, a maximum number of concurrent trades and a maximum loss per strategy. Where the exchange lets you place exits on its own books, use them. The aim is that no single failure turns a controlled loss into an open-ended one.

4. Rehearse in simulation

Run the strategy through backtesting and then paper trading. Simulate the situation you care about: what the strategy does when it misses a candle, when orders are not filled, when the price gaps. Backtests do not reproduce live outages, so treat them as a check on logic, not on infrastructure. Our setup guide walks through this sequence.

5. Set monitoring and alerts

You need to know within minutes when a bot stops trading or an exchange connection fails. Use the platform’s real-time analytics, and enable exchange-side notifications for API and login events. For busy professionals and side-hustle traders who cannot watch a screen, this is the control that substitutes for attention.

6. Write down the manual procedure

Keep a short note listing where each key is, how to disable a bot, how to cancel open orders on each exchange and who to contact. A manual runbook is part of any continuity plan, because some outages have no automated answer. Our trading bot checklist covers the wider selection criteria.

Which setup suits which trader

Nano-capital and micro-traders ($100 to $1,000 accounts, $5 to $50 per trade). Fixed costs matter. A server for self-hosting may cost more than a bot subscription is worth at this size. The Free plan lets you start with limited features, and Standard at $12.50 per month adds capacity when you need it. Keep one exchange, tight limits and paper trading first.

Side-hustle traders and busy professionals. The scarce resource is attention. A hosted platform with real-time analytics and alerts removes the need to supervise a server. Standard or Premium usually covers this need.

High-volume Binance traders and multi-account operators (market making, arbitrage, hedging). Several bots across several accounts and venues is the core use case for multiple simultaneous bots. Premium at $25.00 per month or Enterprise is where to look.

Community owners, educators and boutique funds. You carry responsibility for other people’s expectations as well as your own capital. Documented limits, paper-trading evidence and a clear procedure for outages matter more than strategy novelty. Enterprise is the tier for custom needs.

Traders in high-inflation countries. Capital preservation and withdrawal access often outweigh everything else. Keep withdrawals disabled on bot keys and keep exposure to any single venue modest.

Existing 3Commas, TradingView or Bybit Bot users. Moving does not mean abandoning your logic. Map your rules, run them in paper trading, then move capital in steps.

Our view on failover

Traders often ask for failover as if it were a feature switch. In our experience of the problem, it is a design: where capital sits, how orders are placed, who can touch the keys, and how quickly a person learns something has gone wrong.

We build Darkbot around systematic execution, structured risk control and repeatable logic. The AI layer supports consistency and rule-driven adaptation. It does not forecast prices and it does not promise results. That matters for continuity because a system that behaves the same way every cycle is easier to monitor, to limit and to pause.

Our approach also keeps a person in the loop. Direct order routing and human oversight are part of how we think about reliability, and multiple simultaneous bots let you spread activity across exchanges instead of concentrating it. We recommend starting in paper trading, writing down limits first, and scaling only after the setup behaves as designed.

Grisha

Start with a plan that fits your size

If you want continuity without running servers, Darkbot lets you connect your exchange accounts by API key, run several bots side by side, and use risk tools, backtesting and paper trading from one interface. Start on the Free plan, move to Standard at $12.50 per month or Premium at $25.00 per month when you need more, and use the 14-day money-back guarantee to confirm the plan fits. See the Darkbot plans.

Darkbot

If you want the foundations first, read our guide on how to automate crypto trading.

FAQ

Does any crypto bot automatically move my funds to another exchange during an outage?

Not as a standard feature, and you would not want it. Moving funds needs a withdrawal, which requires a key with withdrawal permission and a working exchange. The safer design is capital split across exchanges in advance, with one bot per venue.

What happens to my open orders if the bot goes offline?

Orders already on the exchange stay there and can still fill. Nothing adjusts or cancels them until the bot or you do. Use exits that rest on the exchange where available, and keep alerts on so you learn quickly that the bot has stopped.

Is self-hosting cheaper than a subscription?

The software can be free, as with Freqtrade, but you pay for a server and for the time to maintain, secure and monitor it. A subscription moves that work to the provider. For small accounts the subscription is often the lower total cost.

What API permissions should a bot key have?

Trading and reading balances only, with withdrawals disabled. Where the exchange allows it, restrict the key to specific IP addresses. Rotate keys on a schedule and remove any key you no longer use.

Sources

Grisha Chasovskih
Written by

Founder & CEO, Darkbot

More articles

Start trading on Darkbot with ease

Come and explore our crypto trading platform by connecting your free account!

Start Free Trial

Free plan available • No credit card required

Contents

Free access for 7 days

Full-access to Darkbot Premium plan

Start now

Free plan available • No credit card required

Cryptocurrency trading involves substantial risk of loss. Past performance does not guarantee future results. Articles are for informational purposes only and do not constitute financial advice.