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.).

Core analytics (robustness, walk-forward, benchmarks)

kiploks.com

Same engine packages as the hosted product

Open engine (npm)

Full source; run on your machine or inside your stack

Full report UI

kiploks.com

Included in the product

Open engine (npm)

You build a UI or consume JSON from the packages

Accounts, API keys, and usage limits

kiploks.com

Included

Open engine (npm)

Not included (you add your own auth if needed)

Hosted storage and run history

kiploks.com

Included

Open engine (npm)

Your files or your database

Integrations (e.g. Freqtrade, OctoBot)

kiploks.com

Guided upload and parity checks

Open engine (npm)

CLI and scripts; same math with your pipeline

Final verdict and full report assembly

kiploks.com

Built server-side for complete reports

Open engine (npm)

Public APIs cover analysis; you host assembly if you want the full stack

Support

kiploks.com

Product support by plan

Open engine (npm)

Community (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.