Cloud vs open engine

What kiploks.com adds on top of the same open packages you can install from npm.

The product and the library share one goal: no hidden math. Metrics and formulas you see in the cloud are meant to match the open engine for the same inputs, versions, and seeds—subject to which blocks your run exposes (full report vs public WFA, etc.).

Capabilitykiploks.comOpen engine (npm)
Core analytics (robustness, walk-forward, benchmarks)Same engine packages as the hosted productFull source; run on your machine or inside your stack
Full report UIIncluded in the productYou build a UI or consume JSON from the packages
Accounts, API keys, and usage limitsIncludedNot included (you add your own auth if needed)
Hosted storage and run historyIncludedYour files or your database
Integrations (e.g. Freqtrade, OctoBot)Guided upload and parity checksCLI and scripts; same math with your pipeline
Final verdict and full report assemblyBuilt server-side for complete reportsPublic APIs cover analysis; you host assembly if you want the full stack
SupportProduct support by planCommunity (GitHub) under Apache 2.0

If a row is unclear for your integration, open an issue on the engine repository or contact us through the site— we care about keeping this table accurate as APIs evolve.

Cloud vs open engine – Kiploks Robustness Engine