Home / Redaction in your stack
Redaction Without Replacing Anything
Most evaluations start because redaction is missing, not because the evidence or content system is wrong. Redactor adds the missing step and leaves the system of record where it is.
Use Cases
Agencies on Axon Evidence.com
Video
Add AI redaction to body-worn camera footage without replacing Evidence.com. Multi-format, exemption codes and bulk processing, with your evidence system unchanged.
Learn moreReplacing Adobe Acrobat
Documents
Acrobat redacts one file at a time, sees text but not embedded images, and records no exemption. What changes when document redaction is the actual product.
Learn moreS3 to S3 Pipelines
Compliance
Bucket in, bucket out. Automated redaction with no duplicate storage and no operator opening a file. Built for call-recording archives and AI training data.
Learn moreMicrosoft 365
Documents
Teams recordings ingest as they are made, and SharePoint documents and Exchange archives redact for records requests. Spoken PII, on-screen text and attachments.
Learn moreWhat These Share
The API is the surface
The same REST endpoints and OpenAPI specification are available in every deployment posture, so a pipeline built against SaaS behaves identically on-premises.
Nothing has to be opened by hand
Headless processing takes a source location, applies a policy and writes the output, which is what makes an archive tractable rather than a project.
One system covers every format
Buying separately for video, audio, documents and images means four tools, four audit trails and four answers to the same procurement question.
Storage is not duplicated
A pipeline that reads and writes your own buckets leaves the content where your retention policy already governs it.
How the Integration Is Built
Point at the source
A bucket, a SharePoint library, a watched folder or a direct API call. Content is read where it already lives.
Choose the policy
A redaction template fixes the detection classes, the framework and the masking style, so the pipeline does not need a decision per file.
Process headlessly
Files are queued and redacted without an operator opening anything.
Write the output back
The redacted rendition returns to the destination you nominate, with the original handled according to your configured output policy.
Read the record
Every action is in the custody trail and the redaction record, exportable for whatever audit the system of record cannot answer.
Where This Fits
The API documents the endpoints, which are the same in every deployment posture, so a pipeline built against SaaS behaves identically on-premises. Automation and scale covers templates, queues and bulk permissions, file formats lists what can be ingested and returned, and deployment covers running the processing inside your own network.
FAQ
Questions, answered
Do we have to replace our evidence or content system?
No. Most evaluations start because redaction is missing, not because the system of record is wrong. Redaction is added as a step and the existing system stays where it is.
How does redaction fit into an existing pipeline?
Through the REST API. A source location is pointed at, a policy is applied, and the output is written back to the destination you nominate, with no operator opening a file.
Is the API the same in every deployment?
Yes. The same endpoints and OpenAPI specification are available in every posture, so a pipeline built against SaaS behaves identically on-premises.
Does content have to be copied into another store?
Not necessarily. A pipeline that reads and writes your own buckets leaves the content where your retention policy already governs it.
Which systems can content be taken from?
Amazon S3 including private buckets, Azure Blob Storage, SharePoint, OneDrive, Google Drive, Dropbox, Microsoft Teams, Zoom and on-premises NAS or SAN, with others available on request.
Tell Us What You Already Run
We will show you where the redaction step goes and what it costs to add.