Home 9 AEC 9 BIM 2.0 Challenges Revit Without Waiting for Feature Parity

BIM 2.0 Challenges Revit Without Waiting for Feature Parity

by | Sep 18, 2026

Cloud-native platforms such as Motif, Snaptrude, Qonic, Arcol, and Hypar remain incomplete, but their modern architectures could challenge established BIM workflows and push Autodesk to respond.
Source: AEC Magazine.

 

A new generation of cloud-native BIM platforms is challenging Autodesk Revit, even though none can yet match its extensive capabilities. AEC Magazine’s Martyn Day argues that expecting these BIM 2.0 tools to reproduce everything Revit has accumulated over 26 years sets an unrealistic standard.

Platforms including Motif, Snaptrude, Qonic, Arcol, and Hypar are being built around cloud computing, modern data architectures, and AI. They lack some of Revit’s documentation, families, plug-ins, scripting, and specialized modeling capabilities. Yet many AEC workflows, including feasibility studies, competitions, concept design, and interior fit-outs, do not require Revit’s entire feature set.

Revit’s strength also comes from an ecosystem that architecture firms have spent years developing. Libraries, scripts, standards, templates, training, and established workflows make migration difficult. Some practices have also built considerable expertise around managing Revit’s performance limitations, file versions, linked models, and cloud collaboration.

The article notes that Autodesk faces a similar transition. Forma is gaining building design, collaboration, data, and AI capabilities, while Revit is becoming increasingly connected to Autodesk’s cloud platform. As more workflows migrate toward Forma, the distinction between extending Revit and eventually replacing parts of its role becomes less clear.

BIM 2.0 introduces its own risks. Cloud-native platforms can increase dependence on vendors because customers may not possess a standalone project file. Firms therefore need to evaluate data exports, IFC fidelity, offline access, APIs, pricing, and what happens if a provider is acquired or disappears.

Rather than immediately replacing Revit, Day encourages practices to test emerging platforms on suitable real projects. Such participation could expose weaknesses, help developers improve their products, and give firms practical experience with alternatives.

The larger issue is competition. If AEC companies wait for complete Revit parity before trying new platforms, promising alternatives may disappear before they have enough real-world use to mature.