Examples¶
Complete, runnable strategies that showcase what qkt can do. Each example is a real .qkt file you can copy, paste, and run.
How these are organized¶
Each example is one page with the same shape:
- What it does — the trading idea in plain English
- The strategy file — copy-paste ready
- How to run it — exact commands
- What to expect — what the backtest output should look like
- How to adapt it — common modifications and gotchas
Single-strategy examples¶
-
EMA-crossover trend-follower
The "hello world" of momentum trading. Buy when the fast EMA crosses above the slow EMA, exit on cross-below or bracket.
-
RSI mean-reversion
Fade extreme oversold readings on RSI(2). Scale-out at three price targets to bank profit progressively.
-
Donchian breakout
Classic Turtle-style breakout. Long when price closes above the 20-day high, exit at the 10-day low.
-
STACK pyramiding
Layer in three entries as the trade moves in your favor — each layer carries its own size with a shared bracket.
-
Risk-managed strategy
ATR-sized positions, daily-loss halts, drawdown cap. The risk discipline that turns a backtest into a live deployment.
Multi-strategy examples¶
-
Regime-gated portfolio
Three strategies (trend, mean-revert, breakout) gated by a regime detector. Only one runs at a time, depending on market conditions.
-
Cross-broker portfolio
BTC on Bybit and EURUSD on Exness MT5, running side by side in one daemon. Same risk engine, different venues.
End-to-end deployment¶
-
Full-stack starter
The whole bundle:
qkt.config.yaml,.env,docker-compose.yml, two strategies, deploy walkthrough. Clone, edit credentials, run.
Looking for something simpler?¶
The recipes section has step-by-step walkthroughs for individual tasks (add a stop-loss, run a parameter sweep, debug a strategy that isn't firing). Use recipes when you're learning; use examples when you need a working starting point to adapt.
Don't trade these with real money yet¶
Every example here is paper-account-only. qkt is pre-1.0 — see status & safety on the homepage. Use these to learn the engine and validate your own ideas, not as production strategies.