Product overview
The whole product, end to end.
Redlineo turns two versions of a document into a redline — Word tracked changes, baked colors, or a colored Excel review copy — and proves the result. Every output verifies itself, carries a SHA-256 certificate of its exact inputs, and embeds a tamper-evident manifest anyone can re-check.
sha256sum. Produced on your server · nothing stored.What it is
A redline is only as good as your ability to prove it.
Every competitor compares documents. None produce redlines that defend themselves. Redlineo is self-hosted, pure Java, and stateless — no cloud, no Office install, no document ever stored or sent to a third party. Each request is computed and forgotten.
Its home turf is US insurance rate/rule/form filings — the redline exhibits state regulators expect in SERFF submissions — and the same primitives serve any regulated-document revision. It is deterministic, not "AI-powered": the same inputs always produce the same redline, which is exactly what a regulator needs to trust it.
The proof — what no other redline tool does
Three kinds of evidence, inside every file.
- ✔Verified as it runs. The tool re-checks that accepting every change reproduces the revised document and rejecting every change restores the original — stamped ✔ on the report page, in the response header, and in the UI.
- ✔A certificate on every comparison. SHA-256 fingerprints of the exact input files, recomputable by anyone with
sha256sum. No trust in us required. - ✔One-drop re-verification. Drop any produced file on the Verify page and it proves the file is unaltered since generation — and, with a configured secret, produced by your server.
- ✔Evidence you can hand over. To a regulator, to opposing counsel, to a market-conduct examiner — the proof travels tamper-evident inside the file itself. No database, no log trawling.
The three outputs
Two versions in. One provable redline out.
You give it the older ("original") and newer ("revised") version of the same document. It produces the marked-up copy — in whichever form the reader needs.
-
.docx · tracked
Word tracked changes
Real Word revisions the recipient reviews with Word's own accept/reject tools. This is the filing artifact: accept all → the revised document, reject all → the original — and the tool verifies that on every run.
Endorsement · form BP 04 30 The policy period begins at 12:01 a.m. 12:01 A.M. Standard Time at the address shown. -
.docx · baked
Baked colors
The same changes flattened into fixed colors — insertions underlined, deletions struck through. Looks identical in every viewer, ideal for PDF conversion; can no longer be accepted or rejected. The report page carries a color key.
- insertion
- deletion
-
.xlsx · colored copy
Colored Excel review copy
The actual revised workbook with colored fills — green inserted, amber changed (previous value in a cell comment), red struck-through deleted rows spliced back. For reviewers who live in Excel. A review view; the Word redline remains what you file.
- inserted
- changed
- deleted
The report a reviewer can act on
It opens with the number every regulator asks first.
Every Word redline can prepend a comparison report: every change numbered and none truncated (so a response can cite "items 12–15"), each line a click-to-jump link to the change itself, summary statistics, moved text recognized instead of double-flagged, and — for rate workbooks — the aggregate rate impact.
- ✔Rate impact, computed. Every changed cell shows its relative delta.
- ✔Filing metadata & assertions. Extracted by your declared conventions, checked on every run — "edition date must bump", "state must be NY" — recorded tamper-evident inside the output.
- ✔Excerpts on demand. "Changed content only" trims any output to just what changed, every omission explicitly marked.
✔ VERIFIED
6 cells changed — average +13.8 %, range +0.1 % to +25 %.
37. Sheet 'BOP' · G12 1.000 → 1.138 (+13.8 %)
The capabilities, plainly
What it does — every claim checkable.
- ✔Word tracked-changes redlines. Native revisions the recipient reviews with Word's own accept/reject tools.
- ✔A reviewable Excel redline. Rate pages become real tracked changes — not just a color report.
- ✔A colored review copy of the real workbook. Green/amber/red fills, previous values in cell comments, deleted rows spliced back.
- ✔Large rate tables just work. Print areas of tens of thousands of rows compare in seconds; beyond readable size, changed pages only — every omission marked.
- ✔Runtime verification + certificate on every output. Accept-all rebuilds the revised file, reject-all restores the original; SHA-256 fingerprints of the exact inputs.
- ✔Rate impact & filing-metadata assertions. The aggregate a regulator asks first, and your own conventions checked on every run.
- ✔A click-to-jump numbered change report. Every change listed, none truncated, each line a link to the change itself.
- ✔A machine-readable change-set in every file. One artifact carries the human report and the JSON data — systems route without parsing prose.
- ✔Verified save-back into the DMS. Integrity-checked before filing, stored next to the source, stamped and linked.
- ✔Self-hosted, nothing stored. Pure Java on your own servers; each request computed and forgotten.
- ✔Insurance-filing domain awareness. Built for rate/rule/form filings — and reconfigurable to any regulated domain via configuration.
- ✔Classify: one document, checked and sealed. Metadata extracted, assertions evaluated, scrub applied, integrity manifest embedded — with a runtime proof the content is untouched.
See it
The demo that lands in three minutes.
- Drop two filing versions — Word or Excel — on the Compare page.
- Get the redline with its report page: rate impact, metadata assertions, ✔ Verified, a clickable change list.
- Drop the result on the Verify page and watch it prove itself.
- Save it into Alfresco with one click — integrity-checked before it is filed.
Not a better diff tool — the only redline whose output is evidence.