Apache 2.0
Permissive, with an explicit patent grant. The backbone of the default kiLM stack.
Licensing policy
Permissive by Default, Copyleft Only by Explicit Choice
kiLM is built so that what you receive — and what you are obligated to — is predictable. The default stack uses only permissive open-source Licenses. Strong-copyleft and source-available Licenses are excluded unless you deliberately opt in, and the boundary depends on your deployment pattern.
Included by Default — Permissive Licenses
The standard kiLM stack relies exclusively on these families. They impose no copyleft obligations on your own code or data.
MIT
Minimal and permissive — use, modify, and redistribute with attribution.
BSD (2- & 3-Clause)
Permissive; redistribute with the copyright notice. No copyleft reach.
MPL 2.0
File-level weak copyleft — changes to the licensed files are shared back, but it does not reach into your surrounding code.
Excluded by Default — Opt-in Only
These Licenses are not part of the standard distribution. A component under any of them is included only if you explicitly enable it for your deployment, with the obligations made clear up front.
GPL (v2 / v3)
Strong copyleft. Optional components only; never in the default path.
AGPL v3
Network copyleft — its obligations can reach hosted services. Opt-in only, behind an explicit profile.
SSPL
Source-available, not OSI-approved. Excluded from the default stack.
BUSL
Source-available with a time delay to open-source. Excluded from the default stack.
What Applies to Your Deployment Pattern
The licensing boundary tightens with isolation.
Air-Gap / Intake-Only
The default permissive-only stack: no copyleft and no source-available components — the cleanest obligation profile.
Managed Service (Private Cloud)
We Operate the instance, so any opt-in component runs under our operational control. You inherit the permissive default unless you request otherwise.
Hybrid
Permissive inside your perimeter; any cloud-side component you approve is licensed explicitly, so there are no surprises across the boundary.
Licenses for kiLM
Separate from the open-source families above, your kiLM license is shaped by two choices: which capabilities you turn on, and how many people use it. You License only the features and functionality you need, at the seat count and deployment stage that fit — the permissive open core is always included.
Capability bundles
Enable only what you use — outgoing Intelligence, paid-LLM providers, GPU compute, external integrations, multi-domain, and high-volume quotas. Each is a separate right-to-use add-on layered on the free permissive core.
Per-functionality entitlements
Fine-grained control: CAD / PLM BYOL adapters, individual system connectors, Fine-Tuning, image search and more are license-locked and stay OFF until your entitlement turns them on. You pay for exactly the functionality you enable — nothing more.
Permissive core included
The base platform runs on permissive open source (Apache / MIT / BSD / MPL). You pay for add-on capabilities, seats, and support — never for the open core. A per-build SBOM ships with every quote.
Seats & deployment stage
Usage scales with your engagement stage — from a small proof-of-concept to a full production rollout. Seats are named users, bound to email and enforced through your SSO / Keycloak.
PoC
Proof-of-concept: a short, time-boxed evaluation with a handful of named seats and only the capabilities under review — a minimal footprint to prove value.
Trial
Evaluating prospects: local-LLM only, no outbound emit, no GPU and low monthly caps — cost-contained by design, with a limited team seat allotment to run a real pilot.
Beta
Early-access: subsidised add-ons and mid-volume caps, with production-grade SLA on the managed substrate and expanded seats for a wider rollout.
Production
Full enterprise: every capability bundle available, Standard / Pro / Enterprise capacity tiers, and a contracted seat count that scales with your organization.
Optional role-group seats cover teams, and BYOL adapters honour a per-vendor concurrency cap. The exact capabilities, seat counts, and caps for your stage are set on your quote.
How We Keep It Clean
Every third-party dependency is reviewed against this policy before it ships. Permissive families are preferred; anything copyleft or source-available is flagged and requires explicit sign-off. This page summarises policy, not legal advice.
A complete SBOM (Software Bill of Materials) with the component-level License inventory for your build is provided along with your quote.