The public Kiploks engine repositories on GitHub are released under the Apache License 2.0. That is a permissive open-source license: you can read the code, run it locally, build on it in many commercial and non-commercial settings, and the license file in the repo is the source of truth for exact terms.

What Apache 2.0 usually means in practice

Patent and copyright grants are spelled out in the license text
You are expected to keep notices where required
Warranty disclaimer applies

Nothing in this article replaces the license text. If you ship a product that embeds the engine, confirm compliance for your situation.

What is not "the engine"

The Kiploks web application (accounts, projects, hosted runs, storage, collaboration) is a separate product. Hosting and product terms are not governed by Apache alone.

Why Apache for the engine

The goal is deterministic, reviewable math and adapters that integrators can pin to versions.

Common misunderstandings

Open source does not mean "no support" or "no security process." It means you can inspect and run the code under the license. The hosted product can still offer SLAs, private data handling, and collaboration features that are not in the public repo.

Attribution and notices

Follow the license requirements for notices in distributions you ship. If you embed the engine in a larger system, your legal review should cover dependency trees, not only the top-level repo.

Relationship to methodology pages

When documentation references methodology, treat it as the behavioral contract for metrics: what is computed, in what order, and on which inputs. If your local run disagrees with hosted output, compare inputs first (Methodology).

Where to read more

Open engine documentation
License and trust
The LICENSE file in the engine repository