License — MIT
killBottleneck is open source under the MIT License — since v1.0.0 (7 November 2026). The beta releases before it (v0.x) were published under the Sustainable Use License and stay under it; the change is not retroactive.
In plain words
| You may | What stays with us |
|---|---|
| Download the source, read it, run it | The name "killBottleneck" |
| Use it internally — company, team, yourself | The logo and the brand files |
| Modify it, redistribute it, build your own product on it | |
| Self-host it for free, forever — for your clients too | |
| Host it as a service and charge for it |
The MIT License asks for one thing: keep the copyright notice. Everything else — including what the old license forbade, such as hosting it for third parties — is allowed.
The name and the logo
"killBottleneck" and its logo identify the original project and our hosted service, so people can tell them apart from forks. They are not part of the MIT License. A fork or a service of your own needs its own name; saying it is based on killBottleneck is welcome. The details, including the list of brand files, are in TRADEMARKS.md.
Why open source
Reach. killBottleneck is meant to be used — in companies, by AI agents, in places we will never hear about — and a permissive license is what gets a project there. It is the license of the tools we build on and of the agent frameworks that connect to killBottleneck. Keeping the hosting right for ourselves, as the beta did, kept the project out of the catalogues and the conversations where open source lives.
What funds development is hosting by the authors: the hosted plans pay for the people who build the product. If you would rather not run a server, that is the way to support the project.
What the hosted service is and is not
Our hosted service runs exactly the image you can build from the repository. The infrastructure around it — provisioning, billing, the customer portal — is ours and is not published; you do not need it to run killBottleneck yourself.
Contributions
The project is open to read and fork, but closed to code contributions: ideas and bug reports are very welcome, pull requests with code are not accepted. One person is accountable for the code, and reviewing outside changes would cost more than it saves. If you need it to work differently, fork it — the MIT License allows exactly that.
See CONTRIBUTING.md in the repository for the details, and SECURITY.md for how to report a vulnerability.

