Ecosystem
Wickra is a family of 24 open-source trading libraries: this indicator core and twenty-three data-driven products built on it. Every one of them is a Rust core with a CLI and the same ten-language binding surface — native Python, Node.js and WASM, plus a C ABI for C, C++, C#, Go, Java and R — released to crates.io, PyPI, npm, NuGet, Maven Central, the Go module proxy and R-universe from one pipeline, and checked byte-for-byte across all ten languages by a golden corpus in every repository.
This site documents the core. Each product has its own site (the Docs column), its own README and the same layout: ## Use in any language in every root README shows the product's handle from Python, and bindings/<lang>/README.md the install line and quick start for each language.
Core — the indicator engine everything else is built on
| Repository | What it does | Release | Docs |
|---|---|---|---|
| wickra | main library (Rust core + Python / Node.js / WASM bindings + a C ABI for C / C++ / C# / Go / Java / R) |  | docs.wickra.org |
Data — market data in, market data replayed, market data synthesised
| Repository | What it does | Release | Docs |
|---|---|---|---|
| wickra-exchange | unified market-data + execution across ten crypto exchanges |  | exchange.wickra.org |
| wickra-synth | deterministic synthetic market microstructure: OHLCV, order book, trades and funding from a single seed |  | synth.wickra.org |
| wickra-timemachine | scrub the whole market like a video — every symbol, full order book, rewound to any moment via deterministic re-fold |  | timemachine.wickra.org |
| wickra-genome | a vector database of the whole market: every asset a 514-dim live vector, for similarity search, clustering and anomaly detection |  | genome.wickra.org |
| wickra-feature-store | OHLCV and microstructure streams into ML-ready feature matrices over 514 O(1) streaming indicators |  | feature-store.wickra.org |
Research — backtest, screen, search, train
| Repository | What it does | Release | Docs |
|---|---|---|---|
| wickra-backtest | event-driven backtester over the Wickra core |  | backtest.wickra.org |
| wickra-screener | parallel multi-symbol screening over 514 streaming indicators |  | screener.wickra.org |
| wickra-darwin | evolutionary strategy search at millions of backtests per second, mutating and crossing JSON specs across the 514-indicator space |  | darwin.wickra.org |
| wickra-gym | a Gymnasium-compatible, microstructure-aware backtest environment with O(1) steps for deterministic RL rollouts |  | gym.wickra.org |
| wickra-impact | the backtester that knows you would have moved the market: agent-based fills on the real historical L2 order book |  | impact.wickra.org |
Trust — prove, verify, benchmark and gate what a backtest claims
| Repository | What it does | Release | Docs |
|---|---|---|---|
| wickra-verify | confirm or refute a claimed backtest report against its strategy and data, in ten languages |  | verify.wickra.org |
| wickra-proof | Proof-of-Backtest: deterministic (spec, data) → report + blake3 hash, recomputable byte-for-byte in ten languages |  | proof.wickra.org |
| wickra-zk | prove a backtest zero-knowledge — on-chain-verifiable performance without revealing the data or the strategy |  | zk.wickra.org |
| wickra-strategy-ci | Jest for trading strategies: golden-pin the report, catch regressions in CI, property-test against fuzzed data |  | strategy-ci.wickra.org |
| wickra-benchmark | reproducible, golden-verified benchmark suite — recompute any (strategy, dataset, report) in ten languages and confirm it byte-for-byte |  | benchmark.wickra.org |
Surface — what a trader looks at and talks to
| Repository | What it does | Release | Docs |
|---|---|---|---|
| wickra-terminal | the trading terminal: a TUI and a browser renderer over the stack |  | terminal.wickra.org |
| wickra-xray | market-microstructure explorer: footprint, order-book heatmap, liquidation map, funding/OI divergence |  | xray.wickra.org |
| wickra-radar | perp-universe alert radar: OI delta, funding flip, book imbalance, liquidation clusters, OI/price divergence |  | radar.wickra.org |
| wickra-copilot | local market copilot grounded in real order-book, liquidation and funding microstructure |  | copilot.wickra.org |
| wickra-shazam | match an asset's current microstructure fingerprint against its entire history |  | shazam.wickra.org |
Edge — the core compiled for the browser, the binary, the chip
| Repository | What it does | Release | Docs |
|---|---|---|---|
| wickra-compile | compile a strategy spec into a standalone deployable: a WASM module, a self-contained binary, or a no_std artifact |  | compile.wickra.org |
| wickra-embed | allocation-free, no_std streaming indicators for bare-metal and HFT, byte-for-byte identical to the core |  | embed.wickra.org |
| wickra-pico | the O(1) indicator core running bare-metal on a $5 Raspberry Pi Pico — the LED blinks on the EMA cross |  | pico.wickra.org |
Sites and demos
- live.wickra.org — all 514 indicators over a real Binance feed, in the browser (wickra-live)
- backtest-live.wickra.org — the backtester compiled to WebAssembly, an equity curve building bar by bar (wickra-backtest-live)
- playground.wickra.org — one StrategySpec side by side in Python, Rust, JS and Go (wickra-playground)
- wickra.org — the marketing site, with the in-browser demo and the benchmarks (webpage)
wickra-<name>-site— one VitePress site per product at<name>.wickra.org;wickra-<name>-go— the published Go module of each product, mirrored frombindings/go/on every release
What every repository shares
- One core, 514 indicators, every one an O(1) state machine — the same numbers in every product.
- Data, not code: a strategy, a scan, a fingerprint, a proof is a JSON spec the Rust core executes, so the same spec runs unchanged from any of the ten languages and produces the same bytes.
- Identical across all 10 languages, proven: a golden corpus per repository, replayed through every binding in CI.
- Zero third-party dependencies in every language,
unsafe-forbidden Rust cores, hash-locked CI, SHA-pinned actions, signed commits and build provenance on every release. - One release pipeline — a tag publishes to every registry at once; the org keeps a version snapshot of what each registry holds.