LICENSE

Open source: AGPL-3.0-or-later

The library is published under the GNU Affero General Public License v3 or later. The full text is in the LICENSE file of the source repository.

AGPL is a strong copyleft license. Its distinguishing feature is the network-use clause: if you modify the library and provide network access to your modified version (for example, a hosted product or an internal API that outside users can reach), you have an obligation to make your modified source available to those users. For research, internal operations, open-source projects, and other non-network deployments, AGPL is a natural fit.

Commercial license

If AGPL doesn't fit your deployment, we sell a commercial license. The commercial license grants:

• A non-AGPL grant for use of the library in proprietary products and services.
• Relief from the AGPL's source-disclosure obligation for network use.
• Optional support, integration help, and custom-feature work under a separate engagement.
• Custom terms negotiable for embedded use, white-labeling, and larger teams.

Email [email protected] with your deployment shape (product description, scale, timeline) and we'll reply with current terms.

FAQ

Does pure use of bytesandbrains trigger AGPL's source-disclosure obligation?

Using the library unmodified, even at the heart of an internal service, does not by itself create a disclosure obligation. The clause that distinguishes AGPL from GPL kicks in when you modify the library and provide network access to the modified version. Specific situations vary, so consult a lawyer for binding guidance.

Can I build a proprietary product on top of bytesandbrains?

Under AGPL, the source-disclosure obligation can attach if you modify the library and serve users over a network. If you want to keep your product closed and avoid that obligation, the commercial license is the path. Many teams in this position prefer a clear contractual grant to navigating AGPL case by case.

Can I contribute under AGPL and still buy a commercial license?

Yes. Contributions are accepted under AGPL through the standard contribution flow on GitHub. The commercial license is a separate transaction with the project owner and does not require you to relicense your contribution.

How is the commercial license priced?

Pricing is per deployment. Common shapes include perpetual licenses for embedded use and annual subscriptions that bundle support. We size the license to the deployment and the engineering effort involved. Email us and we'll sketch a structure.