Free. MIT. Forever.
BonkLM is MIT-licensed and free forever. The Enterprise tier — humans on the line for production deployments — is being scoped with design partners. How do we compare?
Open
- All 9 layers · 12 validators · 5 guards
- 43 integrations — Express, Next, ElizaOS, LangChain, Mistral, …
- Self-hostable · edge-compatible · V8 isolates
- Unlimited prompts, unlimited validators
- Community Discord · public advisories on GitHub
Enterprise
- Everything in Open, plus humans:
- A named engineer when production trips an edge case
- Co-development on validators tuned to your stack
- Roadmap input ahead of public release
- No prompts logged
- No PII stored
- Same code for everyone
- One license — MIT
The Open tier is the product.
Eight capabilities ship in the MIT release. The Enterprise tier is being scoped with design partners — when it lands, this section gains a second column.
- All 9 defensive layers · 12 validators · 5 guards
- 43 integration packages
- Self-hostable · edge-compatible
- On-prem · airgapped builds
- Unlimited prompts · unlimited validators
- Custom validators (write your own)
- Reproducible build artifacts
- Community Discord · public advisories on GitHub
Six things buyers ask first.
Is BonkLM really MIT? Always?
Yes. The library is MIT-licensed at HEAD and every tagged release. There is no feature gate. When the Enterprise tier ships, it will sell access to humans (named engineers, co-development), not access to features the open-source code does not already have.
Do you log my prompts?
No. The library runs in your process; nothing leaves your network unless you explicitly call out to a remote validator. We have no telemetry. No prompts, no completions, no PII, no IP addresses. Audit it yourself in `src/`.
Can I self-host on-prem or airgapped?
Yes. The runtime is a pure Node module with no required network calls. Airgapped deployment is supported out of the box on the Open tier — no Enterprise-only path required.
When does the Enterprise tier ship?
No firm date. We are scoping the offer with design partners on GitHub Discussions before announcing a release timeline. If you have a production deployment that would benefit from a named engineer + co-development, please tell us what you need.
How fast is the validator chain?
In-process, no network hop. The full engine (2 validators + 1 guard, short prompt) measures ~0.05 ms p50 on a single-core M-series — see packages/core/benchmarks/RESULTS.md for the methodology. Longer prompts scale linearly: medium prompt ~0.3 ms, ~5.6 KB long-form prompt ~14 ms. LLM-in-loop validators inherit upstream model latency separately. The pipeline runs in parallel where the contract allows.
What's your CVE disclosure policy today?
Public advisories on GitHub at the time of release. Embargoed pre-disclosure and a private fix channel are on the Enterprise roadmap; until that ships, every reporter and consumer is on the same public timeline.
Still deciding?
Read the spec end-to-end, or open an issue with what you’d need from the Enterprise tier. Both routes are short.