Covered now
nerviq.netand its documentation pages- the public GitHub repository
- the
@nerviq/clidistribution - waitlist, enterprise-contact, and early-access intake flows
These draft terms separate what is governed by the AGPL-licensed CLI from what is governed by the public website and communications surface. They do not yet describe a hosted commercial service.
The final production version should name the legal entity and mailing address. Until then, the safest approach is to define scope clearly and leave entity details as placeholders.
nerviq.net and its documentation pages@nerviq/cli distributionA future hosted dashboard or paid product should have its own commercial terms, account rules, suspension language, and SLA commitments.
The site terms should not pretend those paid-service terms already exist.
The most important legal line here is simple: the code license governs the code, and the website terms govern the site and related communications.
The Nerviq CLI is currently distributed under AGPL-3.0.
This draft keeps the public surface honest: useful, available, and maintained, but not sold as a guaranteed service level.
The public website, docs, and free/open-source surfaces are provided without a service-level agreement.
Response times, uptime, and support are not guaranteed on the free tier.
If paid plans arrive later, SLA language should live in separate commercial terms or an order form.
Because Nerviq still ships beta and preview surfaces, the terms should explicitly say that roadmaps, examples, and previews are informational rather than binding promises.
The public free surface should carry a standard draft disclaimer, but final wording must still be reviewed by counsel.
The website, documentation, and free/open-source software are provided "as is" and "as available" to the fullest extent permitted by law.
This includes no implied warranty of merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability, or error-free operation.
To the fullest extent permitted by law, Nerviq should not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages arising from use of the public site, docs, or free/open-source software.
The final production version should also define any cap on direct damages if legal review recommends one.
The site links outward to GitHub, npm, Vercel-hosted infrastructure, and public proof artifacts. The terms need to acknowledge those dependencies without taking responsibility for third-party availability.
Nerviq may link to GitHub, npm, Vercel-hosted infrastructure, and public proof artifacts.
Nerviq is not responsible for third-party content, policies, or availability.
Nerviq retains rights in the website, branding, and non-open-source assets.
Open-source code remains governed by its repository license.
User-submitted feedback may be used to improve the product, subject to the privacy commitments on personal-data handling.
The suspension language should stay narrow and tied to abuse or security threats, while governing-law details remain placeholders until the legal entity is finalized.
Nerviq may suspend or restrict access to the website or related workflows for abuse, security threats, unlawful activity, or material violation of these terms.
This clause should remain tightly scoped to legitimate platform protection needs.
Governing law: TBD.
Venue: TBD.
General contact: business@nerviq.net.
Security matters should route through the security reporting path rather than general support.