Describe the strategy
Entries, exits, sizing, and the drawdown you will not tolerate — in your own words, not in JSON.
For Kraken
Anyone who has wired up Kraken by hand knows the ritual: pick the right permission boxes, discover the nonce window, widen it, get an invalid-nonce error anyway, then read a forum thread from 2019. The stack handles all of it. You describe the strategy.
6 MB · Windows, macOS, Linux · No credit card
Invalid nonce. Permission denied. Rate limit exceeded. None of these are trading problems, and all of them stand between you and a running strategy.
Entries, exits, sizing, and the drawdown you will not tolerate — in your own words, not in JSON.
Kraken scopes keys granularly — querying funds is a different permission from placing orders. The stack knows which it needs, and does not ask for withdrawal rights.
Monotonic nonces and Kraken's tiered rate counter are handled in the adapter, where they belong, instead of surfacing as errors you have to interpret.
Real historical data first, then live in a size you would not mind being wrong about.
Every other tool in this category maintains a fixed roster of exchanges, and that roster is both the product and the reason for the monthly bill. QuantIDE has no roster. Kraken is a stack — and if you also trade somewhere nobody has built for yet, you describe it and the connection gets written.
Kraken lets you scope a key narrowly, and a trading strategy has no business holding the right to move funds off the exchange. The stack asks for querying and order placement and stops there — and the key itself stays on your machine, never travelling with a stack you share.
Kraken meters API calls against a tiered counter that decays over time, so a strategy that backtests beautifully at one order a second may simply not be allowed to run that way. Testing against real history surfaces that before your money does.
Kraken requires every signed request to carry a nonce larger than the last one that key used. Run two things on one key, restart at the wrong moment, or let clocks drift, and you get rejections that look like an authentication failure but are not. It belongs in the adapter, not in your day, which is where the stack puts it.
Only what the strategy actually needs — querying funds and placing orders are separate permissions on Kraken, and withdrawal rights are a third that a trading strategy has no business holding. The stack asks for the narrow set and nothing more.
No. Describe what you want and you get readable code you own, in whatever language the job calls for. You never have to write it, and you can ask what any part of it does.
On your machine, scoped to the one connection that uses them, and never included when a stack is shared or published. The setup travels; your credentials do not.
Yes. There is no supported-venue list here at all. Stocks, futures and forex brokers work the same way — name the one you use and the connection gets built, or install a stack someone already published for it.
Free forever. A 6 MB download for Windows, macOS and Linux, no credit card, no trial. The paid tiers ($19.99 and $39 a month) only add hosted AI capacity.
Download QuantIDE, describe what you want to trade on Kraken, and backtest it against real history before you generate a single API key.
Download QuantIDE FreeWindows · macOS · Linux · No credit card