Bitget built its name on copy trading and a deep shelf of native automation. Spot grid, futures grid, DCA, Martingale, an AI bot, and a whole marketplace of traders you can mirror with one tap. For plenty of Bitget users that shelf is enough, right up until it isn't. The day you want a rule more specific than the presets allow, or the same strategy running on Bitget and a second exchange from one screen, the built-in menu runs out. So you go looking for an outside bitget trading bot and hit the wall every serious trader eventually hits: the first slick option wants you to paste your Bitget API key onto its servers. "I don't want to give my API keys to a third party" is the sane default for anyone who has read the breach post-mortems this category has lived through. "I want more than the presets give me without building it from scratch" is the other half of the same ask. And you are probably already paying for charts, plus a signal service, plus now a bot, which is three bills to do one job.
That wall is worth understanding before you connect a single key, because it is structural, not bad luck. A Bitget native bot runs inside the same company that custodies your funds. A SaaS bot runs on a server you do not control and keeps your key there. Both put the automation somewhere other than your own hands. The one model that does neither is a bot that runs on hardware you own and reaches into Bitget over the API, where the key never leaves the machine.
That is where a real bitget trading bot earns its keep. TradeArmor is a self-hosted crypto trading platform: built-in BTC/USDC signals with a multi-year live track record, 15 real-time technical indicators, a plain-English AI strategy builder, plus DCA, grid, futures, copy trading, backtesting, paper trading, and tax reporting, all running on your own hardware where your API keys never leave your machine. Bitget is one of eight exchanges wired into the setup wizard out of the box, so it connects on day one with no request form and no waiting. On a Bitget account, that self-hosted clause is the entire point, because your exchange key is exactly the one you least want living on someone else's server.
What Bitget's native tools do, and where they stop
Give Bitget its due. Its native automation is genuinely deep for an exchange: spot and futures grid bots, DCA and Martingale presets, an AI bot, and the copy-trading marketplace it is best known for, none of which cost a subscription on top of trading fees. For a grid in a range-bound market, or a hands-off mirror of one trader, that shelf does real work. If a preset grid is all you need, you can probably stop reading here.
The presets are a fixed menu, and fixed is where they end. A native bot will not take a boolean rule you wrote and run it on every candidate trade. It will not filter its entries through a signal you brought from somewhere else. It will not run the identical strategy on Bitget and Coinbase at once so one dashboard covers both. And copy trading, the feature Bitget is famous for, hands the decisions to a stranger and keeps your funds and the whole arrangement inside Bitget. Mirroring someone else is not the same as owning a strategy.
That last point is quieter than the others and it matters more. When the thing running your automation is also the thing holding your coins, self-custody is not part of the conversation, because nothing about it is self-hosted. It is the same trade-off you make with any SaaS bot versus a self-hosted one, just wearing the exchange's own logo instead of a third party's.
Want to see the dashboard, the signals, and the strategy engine a self-hosted setup gives you? See all features.
What Bitget traders actually want from an external bot
Cut through the marketing and the wishlist is short. People who go looking past Bitget's native presets want four things.
They want their own entry logic. Not a preset grid, but a rule like buy when RSI is oversold and Supertrend flips bullish, written once and run automatically on every candidate. TradeArmor's formula engine takes exactly that, either in plain language through the AI strategy builder or as a boolean formula directly, no Python required.
They want DCA with brakes. Averaging into a spot position is the daily bread of a Bitget account, and most simple DCA tools keep buying straight into a crash with nothing to stop them. TradeArmor's DCA engine runs unlimited levels with cooldown gates and an EQ-price buy gate that holds the next buy until price clears the lowest unsold leg. That is the gap between dollar-cost averaging on purpose and buying every dip on the way down.
They want copy trading that does not hand over custody. Bitget's marketplace is custodial by design: the platform sits in the middle and the funds stay on the exchange. TradeArmor's copy trading is peer-to-peer through your own proxy, where provider keys and follower keys both stay local, no custodial middleman, no performance fee skimmed off the result.
They want futures with real stops. Bitget offers perpetual futures with leverage as high as 125x. TradeArmor's futures mode ships stop-loss and trailing take-profit so leverage comes with brakes attached rather than bolted on afterward. Leveraged trading amplifies losses as fast as gains, so treat that capability with the caution it deserves.
How a self-hosted Bitget trading bot runs
The setup is intentionally unremarkable. You create a Read-and-Trade API key on Bitget, set the passphrase Bitget requires, paste the key, secret, and passphrase into the setup wizard at localhost:8080/setup, pick a strategy mode, and the bot connects over the Bitget API and runs your rules around the clock. The key sits in local config on your machine. There is no TradeArmor account holding it, because there is no TradeArmor server in the path at all.
Because Bitget is one of the eight default exchanges, there is no coverage caveat and no request form: you pick Bitget from the dropdown and go. On top of the connection you get the full position engine: gated DCA, partial sells that trim exposure without losing the cost-basis anchor, take-profit and trailing take-profit, and indicator-based or signal-based exits. The built-in BTC/USDC signals, which have run live for over three years, behave the same on Bitget as anywhere else, and you can filter them through your own indicators, run them straight, or ignore them and run a fully custom strategy.
You also get to run Bitget alongside your other venues on one instance. Trading groups let a single bot run gated DCA on Bitget spot, a custom formula on Bybit, and something else on Coinbase, each with its own rules, all on one dashboard. That is the piece an exchange-locked native bot structurally cannot do.
The US question, answered straight
One thing to be honest about up front: as of 2026, Bitget does not serve US residents. The United States sits on Bitget's restricted-jurisdictions list in its own Terms of Use, and Bitget holds no FinCEN money-services registration or state money-transmitter licenses. Its CEO said in late 2025 that a US strategy was in the works, but no license or timeline has been announced. Routing around the block with a VPN violates Bitget's terms, and its KYC can flag a location mismatch, with account suspension and frozen funds as the stated consequences. None of this is legal advice, just the state of play, and it is not a criminal matter the way a couple of exchange cases have been. Bitget simply is not licensed here yet.
This is exactly where self-hosting quietly pays off. Your strategy, your positions, your signal history, and your API keys all live on your own machine, not on any single exchange. If Bitget is not available to you, or stops being available where you are, switching venues is a dropdown change in the wizard, not a from-scratch rebuild. A self-hosted bot that speaks to eight exchanges keeps your automation portable in a way an exchange-locked native bot never is. You own the strategy layer. The exchange is just a connection.
Locking down your Bitget API key
This is the part that actually protects your money, so it gets the detail.
A Bitget API key can carry Read, Trade, and Withdraw permissions. A trading bot needs a precise two of them. Enable Read so it can see your balance and order state. Enable Trade so it can place and cancel orders. Leave Withdraw switched off. Withdrawal is the only permission that moves money off the account, and automation has no use for it. The worst a leaked Read-and-Trade key can do is place trades you did not want, never move coins off the account. The mechanics of why this holds on every exchange are in the API key security guide, and the short version of whether a bot can drain your funds is: not without a permission you control.
Bitget adds two specifics worth knowing. First, the passphrase. You create the key under Account, then API Management, as a system-generated key, and Bitget makes you set a passphrase on top of the key and secret. Store it with the key, because a lost passphrase means deleting the key and creating a new one. Second, the IP whitelist. Bind the key to the address your bot runs from, and a leaked key is useless from anywhere else. The per-exchange version of all of this, across Bitget and every other venue, is in the exchange API permissions guide.
Setting it up, start to finish
The whole path, in order:
- Create the API key on Bitget. Under Account, open API Management and create a system-generated key. Enable Read and Trade. Leave Withdraw off. Set the passphrase and store it with the key, because Bitget shows it once.
- Bind an IP allowlist. Pin the key to the address your bot runs from so a leaked key cannot be used from anywhere else.
- Install TradeArmor. Download the ZIP, run
pip install -r requirements.txt, thenpython main.py. Around 512 MB of RAM and 100 MB of disk is enough, which is why a Raspberry Pi or an always-on Mac mini makes a fine host. - Run the setup wizard. Open
localhost:8080/setup, pick Bitget, and paste the key, secret, and passphrase. Choose a strategy mode: built-in signals, hybrid with your own indicator filters, or fully custom. - Paper trade first. Run the strategy against live Bitget data with a simulated balance before a single real order fires. When it behaves, flip one setting to go live.
Most Bitget users start on spot with gated DCA and the built-in signals, then grow into custom formulas once they trust the engine. The product is built to grow with you rather than force a switch to a different bot when you outgrow the starter setup, which is the trap the native presets eventually spring.
TradeArmor turns a Bitget account into a fully automated trading operation you actually own: built-in signals with a multi-year track record, 15 indicators, a plain-English AI strategy builder, gated DCA, grid, futures with real stops, peer-to-peer copy trading, backtesting, paper trading, and one-click tax exports, all running on your hardware where your keys never leave the machine. If that is the version of a bitget trading bot you want, see the pricing and get started.