A dense three-day stretch across billing, the Revit plug-in, Morpheon chat, the XR viewer, and two app-store submissions. Here’s what’s live.
Stripe webhooks are now receiving production events on the primary ScanBIM account. Subscription upgrades, downgrades, and seat changes flow into the dashboard without a manual step.
The 1.1 release adds a signed MSI installer, an OAuth device-flow sign-in, and a seven-button ScanBIM ribbon inside Revit. The Morpheon WPF panel docks alongside the model, backed by an embedded MCP WebSocket bridge so the assistant can read and act on model context locally. 20+ Revit-side tools are exposed, from family audits to parameter sync.
Morpheon chat now runs on Cloudflare Workers AI with a Vectorize-backed RAG layer. Each project gets an Observer Durable Object that tracks conversation state and model context. Five agent personas are seeded out of the box — project coordinator, QA/QC reviewer, clash resolver, submittal tracker, and estimator.
Potree (for classic LAS/LAZ point clouds) and a Gaussian Splatting viewer are both live in the web app. The XR viewer streams to headsets over WebRTC, and the submittal tracker UI now renders inline on the web.
The PWA shell ships with a site-walk mobile agent — capture notes, photos, and observations from the field and they sync into the project’s Observer.
More to come as review milestones land. Watch this space.
Navisworks has been the standard clash detection and coordination tool in construction for over a decade. It works. Teams know it. Workflows are established. But the limitations of a desktop-based coordination platform are becoming harder to ignore as project teams become more distributed and expectations for real-time collaboration increase.
Cloud-based coordination platforms are not replacing Navisworks overnight, but the shift is accelerating. Understanding the trade-offs helps VDC teams plan their technology strategy rather than being forced into reactive decisions.
Navisworks handles large, complex models with a level of performance that cloud platforms have not fully matched. Federated models with millions of elements, complex clash detection rules with custom tolerances, and 4D simulation with detailed construction sequencing all run reliably in the desktop environment.
Custom clash rules and search sets that teams have refined over years represent significant institutional knowledge. Migrating that logic to a new platform requires effort, and the result may not replicate every capability that experienced coordinators depend on.
For projects where all coordination team members work from the same network or can exchange files efficiently, Navisworks delivers everything needed without the subscription costs and learning curve of a new platform.
Access is the single biggest advantage of cloud coordination platforms. Any stakeholder with a web browser can view the coordinated model, review clashes, and contribute to resolution. No software installation. No file downloads. No version confusion about who has the latest model.
Real-time collaboration means that when one team resolves a clash, every other team sees the update immediately. The sequential workflow of export, upload, distribute, and wait for review compresses into continuous, parallel coordination. On fast-track projects, this acceleration directly impacts schedule.
Issue tracking and accountability improve when coordination happens in a platform that logs every action. Who raised the clash, who was assigned to resolve it, when was it addressed, and what was the resolution are all captured automatically. That audit trail improves accountability and provides documentation for disputes.
Field access to coordination models through mobile devices means that the people installing systems can view clash resolutions in context. A foreman standing at the point of installation can pull up the coordinated model and see exactly how the conflict was resolved. That direct access reduces RFIs and interpretation errors.
Most VDC teams in 2026 are running hybrid workflows. Navisworks handles heavy clash detection and complex coordination sessions. Cloud platforms handle distribution, review, and field access. The desktop tool does the computational heavy lifting. The cloud platform extends access to the broader project team.
This hybrid approach leverages the strengths of both environments. The risk is maintaining synchronization between them. When the Navisworks model and the cloud model diverge, confusion follows. Clear update protocols and version management procedures prevent this disconnect.
VDC teams considering increased cloud adoption should start with the use cases where cloud platforms clearly outperform desktop tools: broad stakeholder access, field coordination, and issue tracking. Keep complex clash detection in Navisworks until cloud platform performance catches up on computational intensity.
Evaluate platforms based on your actual workflow, not feature lists. Can the platform handle your typical model sizes? Does the clash detection logic support your coordination standards? Can your trade partners access the platform without specialized training? These practical questions matter more than theoretical capability comparisons.