Integrations
It plugs into the pipeline, not into a silo.
Two levels. Alfresco is first-class — compare versions right inside it and file the verified result back in one click. Everything else connects over a simple web API: if a system can call a web service and store a file, it can use Redlineo.
First-class — Alfresco
Compare and file, without leaving your document store.
If you run Alfresco, Redlineo works right inside it. Open a document, pick two versions, and compare — nothing to download or re-upload. It uses your existing Alfresco login, so there are no extra passwords to manage.
Two versions, one click from Alfresco
Open a document's compare page straight from Alfresco. Its version history is already there — the tool pre-selects the oldest version as the original and the newest as the revised, with the same output choices as the main page. Adjust either side and compare.
Compare a desktop draft against the approved edition
Want to check a draft before it goes in? Compare the approved version already in Alfresco against a draft on your own computer — no need to check the draft in first.
One click from "compared" to "filed"
When the redline looks right, one button files it back into Alfresco, right next to the document it came from. Before it is saved, the tool confirms the file is genuine and unaltered — a tampered or foreign file is refused, never filed. The filing details it found (company, state, form number, and so on) travel with it, so the result is easy to search for, and it is linked to the document it redlines. One more click opens it in Alfresco.
Everything else — a simple web API
If it can call a web service and store a file, it can integrate.
Everything the app does is available to other systems, so a workflow can compare, verify and archive with no one in the loop. Any content or workflow platform can drive it.
- Content systems
SharePoint, Documentum, OpenText, Nuxeo, M-Files and others — send two versions, store the redline that comes back.
- Workflow & automation
Camunda and other workflow engines, or RPA bots — run a comparison as one step and route on the verified result. Pleosoft's own low-code platform, Pleodox, drives Redlineo the same way.
- Your own code
Any language that can call a web service. Interactive API docs are served on the running server. The document comparison API, at a glance →
The same web API also handles the rest of the document lifecycle: Classify checks a single incoming document against your filing conventions and seals it — a one-step intake gate before a document lands in the repository — while other calls re-check a produced file on demand or flatten tracked changes into fixed colors. Always with clear, plain-language messages when something isn't right, and interactive API documentation on the running server for your developers.
In short
One output, two ways to consume it.
A web page for people, a REST API for systems — and every file it produces carries its own proof and its own machine-readable record.