# Kilter licences

> How Kilter is licensed: source available. You can read it, run it, and self-host it.

Source: https://paddington.io/kilter-licenses

Licensing

# Kilter licences

Plain-language summary. This page explains how Kilter is licensed; the binding terms are in the LICENSE file shipped with each release and in your written agreement. Where they differ, those documents govern.

Kilter is source available. You can read it, run it, and self-host it. Leaving is easy by design, because that's what keeps us honest.

## The short version

-   Kilter's source is available to clients, with one restriction: you can't turn Kilter itself into a competing hosted offering.
-   Everything Kilter provisions is standard Kubernetes: you can self-host it, or run on any Miniscaler in the network.

## Source available

Clients receive Kilter's source. You may read the source, build it, run it in development and in production, and modify it for your own use. The single restriction is the obvious one: you may not use Kilter to offer a commercial hosted product that competes with Paddington's managed service. Everything a team actually wants to do (self-host, audit, patch, extend, run agentic workloads) is permitted.

## Why we license it this way

The whole pitch of the [sovereign cloud](/k8gentic) is that your infrastructure is yours to keep and easy to leave. A source-available license is how we put that in writing. If we ever stopped earning your business, you would already hold everything you need to walk, which is exactly the [enforcement mechanism](/pricing) that keeps our pricing and our behaviour honest.

## Questions

Licensing or partnership questions: [hello@paddington.io](mailto:hello@paddington.io). See also our [Terms of Service](/terms).