◆ policy // v1.0.4 activation
activation & source availability
NeonDiff is source-available commercial software. API-backed activation is required for every repository before useful review work begins.
last updated · july 12 2026
- Public repositories and pull requests.
- Private, internal, proprietary, client, and commercial repositories.
- Repositories whose visibility or entitlement cannot be verified.
- CLI, dashboard, desktop, daemon, and GitHub App review entry points.
An active entitlement is checked before repository preparation, provider calls, generated findings, or GitHub review posting. Repository visibility does not bypass that gate.
Source availability lets you inspect how NeonDiff works. It does not remove the runtime entitlement requirement or turn NeonDiff into open-source software.
- Inspect the implementation and its release history.
- Fork the repository for evaluation or to prepare a contribution.
- Submit issues and pull requests through the public repository.
- Keep third-party components under their own included licenses.
The repository license governs source use and redistribution. The activation service governs access to supported NeonDiff review workflows.
The NeonDiff license key proves entitlement through the production license API. It is not a model-provider credential and must not be substituted for one.
After activation, bring your own provider key or local model. Hosted provider authentication goes directly to the provider you select; a local model stays on the local endpoint you configure.
Individual support starts at $1/month or $10/year with a 7-day free trial. Organization support is $100/year with a 30-day free trial. Provider usage and model credits are not included.
A missing, expired, revoked, or invalid entitlement blocks review. If the license API cannot be reached and no valid supported activation state can be confirmed, NeonDiff fails closed before useful repository or provider work.
If activation does not succeed, sign in to the license dashboard, confirm the entitlement is active, check network access to the license API, and retry. Never paste a license key or provider secret into an issue or support transcript.
The earlier website language that described a repository-visibility exception was retired for the supported v1.0.4 release. Current installs use the mandatory activation boundary described above.
Release-specific changes are recorded in the GitHub release notes. Questions can be sent to support@electricsheephq.com.