Nexus Execution Protocol (NEP) License Terms

1. Open-source components

Reference implementations, SDKs, and specifications that Hardalion publishes as open source are governed by the license file in the applicable repository (for example Apache License 2.0 or MIT). You may use, modify, and distribute those components according to that license, including commercial use, subject to its attribution and patent grant terms.

2. Proprietary and hosted services

The following are not open source unless explicitly marked otherwise:

• Hardalion-hosted NEP control plane and managed enforcement infrastructure
• Enterprise policy packs, audit dashboards, and support entitlements
• Hardalion trademarks, logos, and brand assets
• FinFlow OS and other product surfaces not published under an OSI-approved license

Use of proprietary components requires an active agreement with Hardalion and is subject to our Terms of Service and any order form or enterprise license.

3. Contributions

If you contribute code to an open NEP repository, you agree that your contribution is licensed under the same license as the project, unless otherwise stated in the contribution guidelines. Hardalion may incorporate feedback into products without obligation to you unless a separate agreement exists.

4. Patents and trademarks

Open-source licenses may include express patent grants as stated in each license file. "Nexus Execution Protocol," "NEP," "Hardalion," and related marks are trademarks of Hardalion. You may not use our marks to imply endorsement without written permission.

5. No warranty

Open-source software is provided "as is" without warranty to the extent permitted by the applicable license. Hardalion disclaims liability for use of open-source components beyond what those licenses require.

6. Enterprise licensing

For commercial deployments, SLAs, indemnification, or proprietary NEP modules, contact legal@hardalion.com or our sales team.