Security & compliance

The document never leaves the building.

Redlineo is self-hosted, pure Java, and stateless. No cloud service, no Microsoft Office, no document ever stored or sent to a third party. It is the redline tool the person who has to say yes can actually say yes to.

Talk to us about a deployment How it integrates

Self-hosted & stateless

Computed and forgotten.

✔Runs on your infrastructure. Pure Java. No Microsoft Office install, no cloud service, no outbound call with your document in it. It runs where you run it.
✔Nothing is stored. Documents are processed in memory and temp files and deleted after the download. Each request is computed and forgotten — there is no document database to breach, subpoena, or leak.
✔No per-seat rollout. A web page for people, a REST API for systems. Nothing to install on every desktop, nothing to license per seat.
✔No trackers, no cookies. Privacy is on-message for this product; the tool doesn't phone home, and neither does this site.

Data hygiene

Metadata scrubbed on every output.

Every produced file is scrubbed: no leaked author names, no company fields, no editing time, no revision fingerprints. The redline carries the change record you intend to hand over — and nothing you didn't.

Why it matters for a filing A marked-up exhibit that quietly carries an internal reviewer's name or an editing-time trail is a disclosure you didn't mean to make. Scrubbing is policy on every output, not an option you have to remember.

Deterministic by design

The same inputs always produce the same redline.

This tool is deterministic, not "AI-powered". There is no model guessing what changed — there is an engine that aligns the two documents and marks the difference, the same way every time. For a regulator, that is the point: a redline you can reproduce is a redline you can trust.

✔Reproducible. Same original, same revised, same options → the same output. Nothing stochastic in the path.
✔Self-proving. Every output re-checks itself at runtime (accept-all → revised, reject-all → original) and stamps the verdict.
✔Auditable without us. The SHA-256 certificate is recomputable with sha256sum; the integrity manifest is re-checkable on the Verify page. No trust in the vendor required.
✔Evidence that outlives the session. Years later, in a market-conduct exam or a dispute, one drop on Verify answers "is this the real, unmodified artifact?" — no database, no log trawling.

Access & credentials

The app stores no credentials.

✔Alfresco uses your own session. Comparisons from Share run against your existing login session (same reverse proxy). Nothing is stored; if the session expires you get a "reload from Share" message.
✔API forwards the caller's credentials. The Alfresco endpoints forward the caller's own Authorization / Cookie headers — the app holds none of its own.
✔Verified before it is filed. A save-back into the DMS is integrity-checked first; an altered or foreign file is refused, never stored.
✔Signed origin, optionally. Configure a signing secret and every output carries an HMAC only your server can produce — proof of provenance, not just integrity.

The compliance summary Self-hosted · stateless · nothing stored · deterministic · metadata-scrubbed · no stored credentials · every output verifiable without the vendor. The proof stack is not a feature bolted on for security — it is the product.

self-hosted document comparison
verifiable document comparison
tamper-evident redline
stateless document processing

Deploy it where your documents already live.

See how it plugs into Alfresco and any CMS/DMS via REST, or read the documentation. To discuss a deployment, get in touch.