Kraken is the current priority deployment. Binance and Pionex are also preferred exchanges for current deployments. This page explains how a Kraken connection is intended to work, what the bot can and cannot do on the account, and what a user should verify before connecting. Compatibility is confirmed during onboarding.
Why users connect a bot to Kraken specifically
The software does not change any of Kraken's own security model. It automates order placement on top of it.
How the Kraken API connection works
A user generates an API key inside their own Kraken account settings and grants it two permissions only: query funds and account data, and create and cancel orders. Withdrawal permission is left off, and Kraken enforces that restriction on its side. The key is entered once during setup. We never ask for a password, a seed phrase, or a fund transfer.
Once connected, the bot translates a chosen rule set into standard Kraken API calls: place order, cancel order, check balance, check order status. Every call is the same type of action a user could place manually inside the Kraken interface. Automation changes the speed and consistency of execution, not what actions are possible on the account.
If anything ever asks for a Kraken withdrawal key, a password, or a transfer to an outside wallet in order to activate a bot, that is not how a legitimate non custodial connection works, and it should be treated as a warning sign. See the full security page for more on this.
Not locked into Kraken only
Kraken is the current priority deployment. Binance and Pionex are preferred exchanges for current deployments. Other exchanges may be reviewed on request at the same license price. Compatibility is confirmed during onboarding.
If a specific exchange is not shown on the site yet, that does not mean it cannot be used. A bot is regularly prepared for other platforms on request and personalized to that exchange's own API. Customization for a different platform does not change the price of the license, the tiers stay the same as described on the plans page.
What a Kraken bot cannot do
- It cannot guarantee profit on any Kraken trade. Market volatility and liquidity remain outside any software's control.
- It cannot exceed Kraken's own rate limits, minimum order sizes, or listed trading pairs.
- It cannot recover a loss caused by normal market movement. It removes manual timing error, not market risk.
- It cannot access funds beyond what the API key permits. There is no shared pool or pooled liquidity involved.
Coin selection and strategy scope on Kraken are tied to license tier, covered in the plans breakdown. The one time API connection step is covered in the setup guide.