Licensing
Same code, two paths
The positronic engine and its plugins are dual-licensed AGPL-3.0-or-later OR Commercial. Take the open path and keep your changes open, or take a commercial license and keep your work private. The code is identical either way.
The two paths
Choose how you use it
Path one
AGPL-3.0-or-later
Use positronic freely, including in commercial products, provided that network-delivered derivative works are distributed under the same terms and source is made available to their users. This is the path for open projects, evaluation, research and anything you are happy to share back.
Path two
Commercial license
Use the same code privately with no copyleft obligations — appropriate for proprietary products, embedded offerings, and organisations whose compliance policy rules out AGPL. A contributor license agreement accompanies commercial licensing. Contact us to scope it.
Not sure which applies? Describe your product and deployment model to info@positronic-ai.us and we will tell you plainly.
What each component is licensed under
positronic engine & plugins
AGPL-3.0-or-later OR Commercial
Covers positronic-engram, the agent interface, the opencode and Claude Code plugins, positronic-serve and the research repository. Dual-licensed as described above, with a CLA for commercial contributors.
@shing.wong/sure-* stack
MIT
sure-factor, sure-ui, sure-state, sure-gentic, sure-web-testing and sure-examples are MIT-licensed. The foundations stay open deliberately, so anyone can build interfaces with them regardless of which path they chose for the engine.
sure-mail
MIT
The mail client and its WASM core are MIT-licensed, like the rest of the sure family: use them, modify them, ship them, with no copyleft obligation. A separate enterprise edition is planned for later under AGPL terms — it is a different line, not a relicensing, so nothing released under MIT here is withdrawn or narrowed.
iStrix
Proprietary
© 2026 Shing Wong, all rights reserved. Licensed for defensive and reactive security use under a commercial agreement. Versions previously distributed under Apache-2.0 remain under those terms for their recipients; this and later versions are closed-source.
Documentation & site
Content © positronic
The prose and diagrams on this site are ours. Benchmark figures quote committed artifacts from the research repository, and each claim is traceable to a tagged engine release.
Plain English
What dual licensing means for you
If you are building something open, the AGPL path costs you nothing: you get the engine, you run it, you modify it, and your users receive the same freedoms you received. Network delivery triggers the reciprocity clause, which is exactly the point.
If you are building a product where the source must stay yours, the commercial path removes that obligation while keeping the codebase, the fixes and the upgrades. You are not buying a fork — you are licensing the same project you would otherwise have to open.
Both paths get the same engine. Neither is a crippled edition.
Also worth knowing
The engine stores everything — episodes, objects, tau, salience, edges, embeddings — as plain SQLite tables. SELECT * FROM episode works. That makes licence compliance auditable in the same way the memory itself is: you can inspect exactly what is there.
Third-party tools invoked as subprocesses keep their own licences.
Ready to pick a path?
Licensing questions: info@positronic-ai.us