Wickra CompileWrite once as data. Deploy anywhere.
Compile a strategy spec into a standalone deployable — a WASM module, a self-contained binary, or a no_std artifact for microcontrollers. The spec is data, not code — and the manifest is byte-identical across ten languages.
You write your strategy as a CompileSpec — the same StrategySpec wickra-backtest runs — and the compiler generates a standalone Rust project that embeds it verbatim and calls the Wickra engine. No interpreter, no runtime spec parsing.
🎯
Three targets
Emit a WASM module, a self-contained native binary, or a no_std artifact for a microcontroller from an allow-listed MCU set — one spec, whichever target you name.
🔒
A reproducible manifest
The generated manifest — the list of files with their hashes plus the canonical spec hash (project_hash) — is byte-identical across all ten language bindings and reproducible across runs.
📈
The Wickra engine, embedded
The generated project calls the same core that powers a backtest, so a compiled strategy sees exactly the same numbers over the 514 indicators of the Wickra core.
🌐
Ten languages, one manifest
The compiler is a JSON-over-C-ABI data API (Compiler::command_json) in Rust, Python, Node.js, WASM, C, C++, C#, Go, Java and R. A developer in any language emits the same project.
🧪
Deterministic, proven
The same spec produces the byte-identical manifest here and in every other binding — the exact cross-language golden invariant, pinned by a golden corpus in CI.
A compile is a CompileSpec: a strategy (the same StrategySpec a backtest runs), a target and a crate_name. The compiler embeds the strategy verbatim and generates a standalone project for the target you name.
Wickra Compile is part of the Wickra ecosystem. The project it generates embeds wickra-core, so a compiled strategy computes exactly the same indicator values a backtest or a live chart would.
Wickra Compile is a software library, not a trading system, and comes with no warranty — use at your own risk.