Licensing
The FSL-1.1-ALv2 / Apache-2.0 split, what you may build and sell, and the two-year Apache conversion.
Neuralis is source-available under a deliberate two-tier split. This page is the licensor's binding interpretation of that split — it explains intent and answers the common cases, and it does not amend the license texts themselves.
The split
| Tree | License |
|---|---|
The Neuralis host and the product packages (agent-core, brain-core, admin, machine-core) | FSL-1.1-ALv2 (Functional Source License 1.1, Apache-2.0 future license) |
@neuralis/package-system — the contract layer every package imports | Apache-2.0 |
The examples/* authoring reference trees | Apache-2.0 |
Licensor: Eszes LLC. Each tree carries its own LICENSE file and
license manifest field — licensing is declared per package, never inherited
from a repository root.
What you can do
The FSL permits any use except a Competing Use (offering the software to others as a commercial product or service that substitutes for it). That explicitly includes:
- Self-hosting Neuralis for your organization — any size, any revenue, production included. Internal use is a named Permitted Purpose.
- Non-commercial education and research.
- Professional services. An agency or consultancy may install, configure, extend, and operate Neuralis for a client — the client self-hosts under its own license rights, and the agency acts as its contractor. Building custom packages for that client is part of the same permitted service work.
- Forking and modifying for any Permitted Purpose, with the license and copyright notices kept intact on redistribution.
What you cannot do
You cannot take the FSL-licensed product and offer it to third parties as a competing commercial product or service — for example a hosted "Neuralis as a service", or a rebadged substitute with substantially the same functionality. That single carve-out is the entire restriction.
The two-year Apache conversion
Every FSL-licensed version automatically becomes available under Apache-2.0 two years after its release — irrevocably, by the license's own Grant of Future License. The protection window is rolling and version-scoped: the newest release is FSL-protected, and the codebase continuously flows into the permissive commons behind it.
Building packages: no restrictions transfer to you
Third-party package authors only need the Apache-2.0 contract layer
(@neuralis/package-system) and the Apache-2.0 example trees. Importing the
contracts, publishing your own packages — commercially or not, under any
license you choose — carries no Neuralis restrictions onto your code. The
FSL boundary exists so the product cannot be resold as a competing service; it
was never meant to reach the ecosystem built on top.
Trademarks
"Neuralis" and the associated names identify the origin of the software. The FSL grants no trademark rights beyond identifying that origin — forks and derived offerings must use their own names.
Contributing
External code contributions will require a CLA (contributor license agreement) so the split-licensing model stays legally coherent; the CLA gate goes live before the first external pull request is accepted. Until then, issues and discussions are welcome.