Help · docs
Questions we hear every week.
If something is still unclear, email hello@vecktor.in. A human replies within a day.
Compose mode · how to use
Type a strategy. We compile, optimize, deploy.
Vecktor's Compose mode turns plain English into a typed strategy config (a StrategyDSL) that combines indicators, operators, parameters, and risk rules. The compiler validates every (indicator, operator, parameter) tuple against the catalog below before any backtest runs — there's no free-form code execution and no template lock-in.
Three-step workflow
- Compose. Type a strategy on /compose. Mention indicators by name (e.g. "RSI 14 below 30"), specify coins and timeframe, and describe the risk profile ("conservative", "aggressive", "trail my profit at 2.5%").
- Compile. The compiler emits a validated DSL config. You see the JSON inline, then choose: backtest the single config, or click Optimize ⚡ to spawn 10 variants.
- Optimize. The optimizer perturbs your numeric params (RSI period, threshold, MACD lengths, std-dev, etc.), runs each variant on a 70/30 walk-forward split, and ranks by out-of-sample Sharpe. An overfit warning fires when in-sample is more than 1.5× OOS — the textbook sign of curve-fitting.
Indicator catalog · click for operators
rsi4 ops
ema4 ops
sma4 ops
macd4 ops
bollinger6 ops
supertrend4 ops
adx4 ops
donchian3 ops
stochastic4 ops
atr2 ops
Limits — leverage 1-20x · position 1-25% · stop ≤ 50% · take profit ≤ 200% · entry rules AND-combined (OR/NOT in v2)
01
How does the new Compose mode work?
−Type a strategy in plain English on /compose. The Vecktor compiler emits a typed config (a `StrategyDSL`) that combines indicators, operators, parameters, and risk rules — no code, no template lock-in. Hit Compile to see the shape; hit Optimize to spawn 10 variants, walk-forward them on a 70/30 train/test split, and return ranked results with an overfit warning. The catalog supports SMA, EMA, MACD, RSI, Stochastic, ATR, Bollinger, ADX/DMI, Supertrend, and Donchian — entry rules are AND-combined for v1.
02
What can I actually ask for in Compose?
+03
What does the Optimize button actually do?
+04
Why do I see the strategy `custom_dsl_v1` in my backtest history?
+05
Why does my live P&L look worse than the backtest?
+06
What actually triggers the kill-switch?
+07
How honest are the fees you model?
+08
Do you see my API keys?
+09
Can I lose more than my deposit?
+10
Is Vecktor regulated?
+11
How much does Vecktor cost?
+