NELVOSS
Access control and separated operational environments.
Trust
Built for Control. Designed to Be Verified.
For technical decision-makers: how Nelvoss approaches security, control and validation — with clear limits on what is claimed publicly.
Policy-based limits and human approvals for AI-assisted actions.
Traceability for relevant decisions and activities.
Documented tests with explicit verification status.
Verification levels
We distinguish architecture principles from what has been implemented and verified. A local test alone does not make a capability production-ready.
Intended design direction — not delivery proof.
Present in a codebase or product surface.
Documented test in a named environment.
Validated in a staging environment with recorded bounds.
Only when production evidence exists — none claimed publicly without register approval.
- Information security approach Defence in depth through access control, separation of environments and controlled execution paths. Not presented as a formal certification.
- Organisational access controls Roles and permissions structured per organisation and environment.
- Tenant separation Business environments are designed to remain isolated; validation status is tracked separately from marketing claims.
- AI oversight AI-assisted steps operate inside approval and policy boundaries.
- Data handling Contact data is processed as described in the privacy notice. Form submissions are validated server-side and routed to the business inbox.
- Deployment validation Isolated technical tests must not be described as production certification.
- Operational limitations Capabilities are labelled Verified, Under validation or Planned.
Evidence registry
Public technical claims are tracked internally. Only approved rows may appear on this site.
| Claim | Class | Environment | Limits |
|---|---|---|---|
| Modular foundation with licence-oriented packaging | Qualified | Product architecture / lab | Not a guarantee of every module in production for every tenant |
| Controlled AI-assisted workflows with human approval | Qualified | Product direction + selected flows | Scope varies; not full autonomy |
| Formal ISO 27001 / SOC 2 certification | Rejected (not claimed) | — | No certificate published |
| Measured % cost reduction for customers | Rejected (not claimed) | — | No invented savings |