Context
Customers often ask whether Weaver is a Revit replacement. The short answer is no, and the long answer is more interesting. Different layers of the stack do different jobs; a sensible architecture keeps them separate.
Authoring, viewing and CDE-ing are three different jobs.
Explanation
Three categories of tool, three different roles:
Authoring tools
Revit, Tekla, AutoCAD, Plant 3D. These are where geometry is created and edited. Weaver doesn't replace them; it ingests IFC exports at the object level and links them into the knowledge graph. Designers keep working in the tools they already know.
Federated viewers
Navisworks, Solibri, BIMcollab. These visualise and clash-check models from multiple authoring tools. Weaver doesn't replace them either; it integrates with them via the buildingSMART BCF API for issue management.
The CDE
This is where Weaver lives. The CDE is the agreed source of information across all authoring tools and viewers. It owns the lifecycle, the audit trail, the federation, the structured data, the cross-silo queries. Revit doesn't try to be a CDE; Weaver doesn't try to be Revit.
A Weaver implementation does not change which authoring tools your designers use. It changes how the resulting information is managed, related, versioned and queried. Existing tools stay in place; Weaver becomes the semantic backbone connecting them.