Security

Security by architecture, not by promise

The strongest security posture for AI infrastructure is holding nothing that can be breached. Revyzor runs entirely inside your environment: your GPUs, your storage, your keys, your network boundary. We never see, host, or transmit your data.

Your GPUs
Runs on your infrastructure, on-prem or in your cloud tenancy. No SaaS component.
Your keys
Signing keys are generated and held by your organisation. We never hold key material.
Your data
Documents, prompts, and model state never leave your environment. Nothing phones home.

Deployment boundary

Revyzor is a plugin for vLLM, SGLang, and NVIDIA NIM, activated by a single configuration flag inside your serving stack. It makes no outbound network calls, requires no external services, and sends no telemetry, usage data, or diagnostics to us. If your inference cluster is air-gapped, Revyzor runs air-gapped.

Cryptographic signing

Every retained checkpoint carries a W3C Verifiable Credential signed with Ed25519: which model, which organisation, which document, and when. Change one byte of the retained state and the signature fails verification. Credentials from the wrong model, the wrong organisation, or a modified checkpoint are rejected at load time.

Signing keys belong to your organisation and stay inside your key management. External anchoring of public keys is on our roadmap and clearly labelled as such; we do not present roadmap items as shipped capability.

Storage and retention

Compressed model state is persisted to your own NVMe or storage tier and inherits the controls you already run there: at-rest encryption, access control, backup, and deletion policy. Retention periods are yours to set. Deleting a checkpoint is an ordinary file deletion inside your estate; there is no copy anywhere else.

What we never have

  • No access to your documents, prompts, outputs, or model state
  • No copies of your signing keys
  • No hosted service processing your data
  • No telemetry or phone-home from the deployed plugin
  • No cookies or trackers on this website

Certifications: an honest answer

We are an early-stage company and do not yet hold SOC 2 or ISO 27001. We are not going to pretend otherwise. Our answer is architectural: those certifications exist to give you confidence in how a vendor handles your data, and we designed Revyzor so that we never handle it. Source code access under NDA is available per engagement, so your security team can review exactly what runs in your estate.

Send us your security questionnaire.

We answer them line by line, and the answer to most lines is the same: it never leaves your environment.