Home / Platform

Detect. Review. Redact. Prove.

Most redaction software stops at the third step. The fourth is the one that decides whether a release survives an appeal, and it is where Redactor is built differently.

ONE FILE, FOUR STAGES 1DETECTclasses found,stored as timed data2REVIEWoperator merges,adjusts, draws3REDACTburned into anew rendition4PROVEexemption, coverage,custody WHAT COMES OUT REDACTED RENDITION (b)(7)(C) ORIGINAL, RETAINED an appeal is decided against this 315file extensions12frameworks6deployments36event types

At a Glance

315

Distinct file extensions across five content types

12

Compliance frameworks, each with its own class set

6

Deployment postures, shared SaaS through air-gapped

36

Audited event types, ingestion to disposition

Where It Runs

Shared SaaS

Multi-tenant, isolated by tenant identity

Dedicated cloud

Isolated tenancy, operated by VIDIZMO

Private cloud

Your own cloud subscription

On-premises

Your data centre, your hardware

Hybrid

Cloud application reaching on-premises directories and storage

Air-gapped

Disconnected from the public internet entirely

The same engine runs in all six. AI inference is self-hostable, so detection need not call out of your network, and in an air-gapped deployment the whole stack is local: language models through vLLM or Ollama, plus local models for transcription, vision, OCR and PII detection.

Deployment · Security

See It on Your Own Files

Send us something difficult and we will run all four stages on it.