Open source

A redaction tool asks you to trust it with the documents you are least willing to leak. That trust should be checkable, so the code that reads a file and decides what to remove is public.

What that gets you

Not open source as a virtue, but as something you can act on.

Read how detection works

The recognizers, the scoring, and the rules that decide what counts as sensitive are all in the open. You can read them before trusting them with a document.

Run it yourself

The same engine we run is the one you can deploy, so documents never have to leave your infrastructure.

Verify a redaction

Same input, same policy, same output. Deterministic results you can reproduce and audit rather than take on faith.

Fork it

Add a recognizer for a format we have never seen, or change how a conflict resolves. Nothing about the pipeline is sealed.

No licence surprises

Apache 2.0 for the engine, MIT for the clients, AGPL for Studio. Every repository states its terms in full.

Built in the open

Issues, commits, and releases are public. The history of how a detection rule got its current shape is there to read.

Run it on your own infrastructure

Deploy the engine yourself, with air-gapped support and no document leaving your environment.

Security & compliance
GDPR
SOC II
HIPAA