Skip to content

Licensing

What you'll learn: The license structure across Kyvvu's packages.


Package licenses

Package License License file
kyvvu-sdk (published as kyvvu) Apache License 2.0 kyvvu-sdk/LICENSE
kyvvu-langchain Apache License 2.0 kyvvu-langchain/LICENSE
kyvvu-claude Apache License 2.0 kyvvu-claude/LICENSE
kyvvu-cli Apache License 2.0 kyvvu-cli/LICENSE
kyvvu-baseline Apache License 2.0 kyvvu-baseline/LICENSE
kyvvu-templates Apache License 2.0 kyvvu-templates/LICENSE
kyvvu-crewai Apache License 2.0 kyvvu-crewai/LICENSE
kyvvu-engine Business Source License 1.1 (BSL 1.1) kyvvu-engine/LICENSE
kyvvu-api Proprietary kyvvu-api/LICENSE
Kyvvu Dashboard Proprietary --

Python client (Apache 2.0)

The kyvvu Python client is permissively licensed. You can use, modify, and distribute it freely.

Engine (BSL 1.1)

The engine is source-available under the Business Source License 1.1:

  • Free use is permitted for development, testing, research, evaluation, and personal non-commercial purposes.
  • Production use requires a Kyvvu commercial subscription or a separate license agreement with Kyvvu B.V.
  • The engine may not be used to offer a commercial product or service to third parties whose value derives, in whole or in substantial part, from its policy enforcement, behavioural interception or runtime governance functionality.
  • Each release converts to Apache License 2.0 four years after its publication date.

The Python client depends on the engine at runtime. The Python client's permissive license does not extend to the engine. Bundling, vendoring, or depending on the Python client does not grant rights to the engine beyond what BSL 1.1 permits.

Platform API and Dashboard (Proprietary)

The API and dashboard are proprietary software. Copyright 2025-2026 Kyvvu B.V. All rights reserved.

Behavior definitions

The atomic behavior definitions (action kinds, verbs, and the Behavior schema) are part of kyvvu-engine and are governed by BSL 1.1.

Bundled policy content (Apache 2.0) -- and what that does not mean

The kyvvu-baseline package holds the 15-policy frozen baseline set. That policy content is Apache 2.0, like the kyvvu-manifests-public manifests it is copied from, which is why it is a separate Apache-2.0 package rather than part of the BSL engine: policy content carries the licence of the manifests it came from.

Apache-2.0 manifests do not make the trial Apache-licensed end to end. Loading them still requires kyvvu-engine to evaluate them, and the engine is BSL 1.1. So:

  • The policy YAML and loader in kyvvu-baseline are Apache 2.0. Copy, modify and redistribute them freely.
  • Evaluating them -- which is the only thing that makes them useful -- runs BSL-1.1 code. Free-to-try therefore remains bounded by the BSL's non-production terms: development, testing, research, evaluation and personal non-commercial use. Production use of the baseline needs the same commercial subscription as any other production use of the engine.

One further consequence: pip install kyvvu-engine alone does not get the frozen set. It is the kyvvu-baseline package; kyvvu and kyvvu-cli depend on it.

Pricing

Kyvvu meters usage by active engine instance-hours. One instance-hour is one KyvvuRunner (or kyvvu serve process) active for one hour.

Commercial licensing

For production use of the engine, commercial subscriptions, or licensing inquiries:

licensing@kyvvu.com


Next steps