Backtest crypto strategies as portfolios, not isolated trades.
A signal that looks good on one chart often fails when scaled across a portfolio. Keel backtests crypto strategies as multi-asset portfolios on Hyperliquid markets with real fees, slippage, funding rates, drawdown, exposure, and position sizing visible — so you can judge a strategy by what it actually does, not by a single trade.
Three ways most backtests lie.
Single-asset, no-cost, won’t-deploy. Each gap turns a backtest into wishful thinking.
A signal that prints money on BTC alone often craters when scaled across a portfolio. Single-asset notebooks miss correlation, exposure, and concentration risk.
Test as a portfolio across the Hyperliquid universe. See how the strategy behaves when sized, rebalanced, and constrained — not just whether one trade worked.
A backtest without realistic fees, slippage, and funding is a fantasy. Strategies with thin edge often die at first contact with execution costs.
Real Hyperliquid fees, slippage estimates, and funding rates are baked into the simulation. Funding-aware sizing and carry strategies are testable end-to-end.
A backtest in a Jupyter notebook is hard to translate into live trading. The translation layer between research and production is where bugs hide.
The same structured pipeline that backtests is the pipeline that runs live. No translation layer, no drift between research and production.
Under the hood
Structured strategy engine
Strategies are composable pipelines of typed components. The system validates every connection at edit time — errors caught before you backtest, not after you deploy.
AI built on the same system
AI doesn’t generate code — it composes from the same components you use. It understands valid connections, constraints, and trade-offs. Every strategy it builds is structurally valid.
Detailed backtest reports
Sharpe, Sortino, max drawdown, win rate, trade-by-trade logs. Compare runs side by side. Real fee and slippage modeling.
Version control for strategies
Every edit creates a new version. Compare any two versions side by side. Tag releases, restore previous versions, fork strategies. Your full history, always recoverable.
Auditable execution logs
Every live run is logged — what the strategy calculated, what orders executed, what filled. Full transparency.
Non-custodial by design
Your keys never touch our servers. Keel uses Hyperliquid’s native delegation. Sign once, revoke anytime.
Common questions
How accurate is the backtest?
Backtests run on real Hyperliquid market data with real fees, slippage estimates, and funding rates. Multi-asset portfolio behavior is simulated with realistic position sizing and rebalance logic. The same pipeline that backtests is the pipeline that runs live.
Does it model funding rates?
Yes. Funding rates are first-class in the backtest — long perps that pay funding cost you, short perps that receive funding pay you. Funding-rate carry strategies and funding-aware sizing are testable end-to-end.
How long does a backtest take?
Most multi-asset backtests on Hyperliquid markets complete in seconds. Larger universes and longer date ranges run on the backtest worker without blocking the UI.
Can I export results?
Backtest runs save as artifacts you can browse, compare, and re-run. Per-strategy version history lets you compare any two runs side by side. The CLI surfaces backtest output programmatically.
Will live performance match the backtest?
Backtest-to-live parity is a design goal — the same strategy code runs in both. Live performance can still diverge from backtests due to slippage, market impact, and regime changes. Auditable execution logs let you compare what the strategy expected vs what the market did.
What about strategy backtesting vs portfolio backtesting?
Both. Backtesting in Keel always evaluates the strategy as a portfolio — sizing, exposure, drawdown, and concentration limits are all part of the simulation. You are not running a single-asset chart-by-chart backtest; you are running the whole strategy.