Read the source.
Know the terms.
The engine is open source under AGPL-3.0. Building and serving your applications with it is free; embedding it in a closed product calls for a commercial license. The repository license is the authoritative text.
Read the repository licenseOn this page
Free, under AGPL-3.0
- Run bext in production, at any scale
- Self-host it on your own hardware
- Build, sell and distribute apps made with bext
- Read, modify and redistribute the source
- Offer bext as a service, publishing your changes under AGPL-3.0
Commercial license
- Embed the engine in a closed-source product
- Offer a modified engine as a hosted service without publishing your changes
- Redistribute it as a component of a proprietary platform
- Commercial guarantees: support, SLA and indemnity
AGPL-3.0 or a commercial license, your choice
AGPL-3.0 keeps the engine and its improvements open: if you modify it and make it available to others, including over a network, you publish your changes. If that condition doesn't fit your product, the commercial license lifts it.
What the license says, without the jargon
You own what you build
Your apps, your code and your data are yours. AGPL-3.0 covers the engine, not the applications it serves.
Supporting packages stay MIT
Most packages around the engine are MIT-licensed. Use them in any project, open or closed.
Offline validation
Commercial license keys are verified locally with an Ed25519 public key built into the binary. The engine makes no network request to check them.
Modify it, share it
If you modify the engine and make it available to other people, you publish those changes under AGPL-3.0. No changes, nothing to publish.
This is a plain-language summary, not the binding legal text. The repository license is authoritative, and any commercial license is a separate agreement.
Need to embed the engine?
Platforms, OEMs, AI: let's talk commercial license, scope and terms.