Narrower than the incumbents. Deeper where a compliance function looks.

The field at a glance

Competitor cells summarise each vendor's own published documentation, held in our research library. If a cell misstates a product, tell us and this page gets a new revision.

Two cells worth reading twice: Autodesk's 3D viewing and e-Builder's executive reporting are genuinely ahead of aptEDMS, and the desktop sync row runs against us across most of the field. The rest of this page says why we hold those positions.

Vendor by vendor

Idox FusionLive

Mature and wide, with the full EPC deliverables machinery — which aptEDMS now also carries: placeholders, planned, forecast and actual dates, submittals, formal review with a consolidator, and progress measured from the register. Three behaviours documented in FusionLive's own guide are worth knowing before a security review finds them: Custom BI Reports ignore document security (its guide's warning, verbatim), Skip Document Security is an admin search override, and BI feed links carry no security at all — anyone with the URL can consume them. aptEDMS has no equivalent escape hatch: every query, including its own API's, resolves through row-level security. Retention, legal hold and disposition are absent from FusionLive's administration chapters entirely.

Oracle Aconex

The closest philosophical relative: its neutral, immutable correspondence model is the right idea, and aptEDMS agrees with it — sent mail here cannot be edited either. The differences are that an aptEDMS transmittal is additionally verifiable (a sealed package with a hashed manifest, not just an immutable record), and the commercial model: Aconex prices as a percentage of the capital value, negotiated and unpublished; aptEDMS is a flat monthly price per project, printed on the pricing page.

Asite

Strong in public-sector and government frameworks, with a visual workflow builder and a real desktop sync client in aDrive — the sync row is Asite's to win, and we say so above. Where the positions reverse is records and integrity: file fixity, retention, legal hold and a written storage policy are aptEDMS ground that Asite's documentation does not cover.

Procore

A construction management platform first and a document system second — site diaries, RFIs, field tools, priced as a percentage of construction volume. If you are buying construction operations, Procore is a fair choice; document control depth of the kind this site describes is not its game, and it does not claim otherwise.

Autodesk Construction Cloud

The best 3D and BIM viewing in the field — native RVT, DWG, NWD and IFC through its own viewer — and ISO 19650 naming support. If daily model coordination is the job, ACC earns its seat. aptEDMS converts and views models but deliberately does not attempt model markup, and delegating heavy BIM to a tool like ACC is a position we defend rather than a gap we deny.

e-Builder

Owner-centric capital-programme management with executive reporting as its headline — genuinely ahead of aptEDMS's report builder, which covers the common cases and scheduled exports rather than ad hoc BI. Its document module is process-driven with browser redlining; integrity and records controls of the kind above are not documented.

And the rest

DocuWare and its peers are office document management — invoices, HR records, general business content. Good products, different market: no revision codes, no transmittals, no register. Bluebeam Revu is the markup benchmark rather than an EDMS — it is the bar the aptEDMS viewer was measured against (clouds, callouts, stamps, layers, calibrated measurement), and that bar is met in the browser, without a desktop install.

Where aptEDMS is ahead

The pattern in the matrix: the whole field enforces access in the application and audits by report. The capabilities below come from records management rather than project collaboration, and on the evidence of the vendors' own documentation, the category does not model them at all.

Where it is behind

• Breadth of accumulated features. A decade of EPC requests adds up. If your evaluation is a checklist written from an incumbent's manual, aptEDMS will not win it.
• Desktop sync. Asite, Procore and Autodesk ship real sync clients. The aptEDMS app installs and reads offline, and markup drawn offline syncs on reconnection — but a cross-project desktop working set does not exist and is not scheduled.
• Ad hoc business intelligence. e-Builder's executive reporting and ACC's Insight are ahead. The aptEDMS report builder covers the common cases, scheduled, to PDF and Excel — it is not a BI studio.
• Native BIM. ACC's model viewing is the best in the field and this page says so. aptEDMS views and converts; it does not coordinate models.
• Track record. The incumbents have references you can ring. No page argues that away.

Differences on purpose

Recorded so an absence is traceable to a decision rather than looking like an oversight. Disagreeing with a reason is fair; these are positions, and we defend them.

No folder tree

Documents live in a register with metadata and saved views. A folder is one filing scheme frozen at kick-off by whoever set it up first; metadata lets every discipline arrange the same documents the way that discipline works — and folder trees are where access control quietly diverges from intent.

Sent correspondence cannot be edited

Aconex got this right and aptEDMS holds the same line: a correction is a further message, never a rewrite. A system whose sent correspondence can be silently amended cannot claim its thread is evidence.

No markup on 3D models

Markup is keyed to a page and a point on a sheet. Pretending a 3D position is one of those would corrupt the markup store for the drawings, which is what markup is mostly for.

Sealed transmittals instead of versioned work packages

FusionLive's versioned package PDF with its automatic change table is clever, but a sealed transmittal produces something the recipient can verify against what was sent. Verification beats presentation.

No reprographics module

Print shops, fold and punch instructions — a 2010 requirement kept for continuity elsewhere. What still matters is the distribution method on a transmittal recipient, and that is one column.

The standards position

The field publishes certificates — SOC 2, ISO 27001, FedRAMP — and those attest to the organisation. aptEDMS additionally publishes a clause-by-clause self-assessment against ISO 19475, the standard about the documents themselves: six areas conformant, three partial, seven not yet built. ISO 19650 numbering, suitability and revision codes are implemented; CFIHOS reference data, facility tree and tag register are in place so a handover package assembles as the project runs.

A claim you can check is worth more than a claim you have to believe. Both assessments are available in full — ask.

Check it yourself

Everything above is a statement about behaviour, so it can be tested rather than argued. Four things worth trying in the demo, because they are where the differences show:

1. Issue a revision, then look for a way to overwrite the previous one.
2. Open the audit trail and look for an edit or delete control.
3. Seal a transmittal and read the manifest hash.
4. Try to move a document to a status the workflow does not allow.

Open the demo Ask for the assessments