BIMcloud SaaS Outage

A Case for Operational Continuity

A recent BIMcloud SaaS outage highlighted a familiar issue in BIM environments:

Not failure itself – but the lack of continuity when it happens.

The Event

BIMcloud SaaS experienced a temporary outage, reportedly caused by an expired wildcard certificate.

A relatively small issue in technical terms – but with immediate impact:

  1. no access to shared projects
  2. no live collaboration
  3. work effectively paused

This is not unusual for cloud-based systems.
But it exposes a structural dependency.

The Real Problem

The issue is not that systems fail.

The issue is that most BIM environments are not designed for failure.

In many setups, BIMcloud SaaS becomes a single operational layer:

  1. centralised
  2. always-on
  3. assumed to be available

When that layer disappears, there is often:

  1. no fallback
  2. no defined workflow
  3. no clear recovery path

Continuity vs Uptime

Uptime is a platform metric.

Continuity is an operational capability.

These are not the same.

A system can have high uptime – and still leave teams exposed when it goes down.

The critical gap sits between failure and recovery:

  1. Can work continue?
  2. Is there an alternative mode of operation?
  3. How clean is the return to normal?

This is where most BIM environments remain fragile.

The Missing Layer

Over the past decade, BIM development has focused heavily on:

  1. tools inside the workflow
  2. performance of collaboration systems
  3. feature depth

What’s emerging now is a different requirement:

An operational layer around the system itself.

This includes:

  1. reliable backup
  2. accessible recovery
  3. defined fallback workflows
  4. controlled reintegration

Not as a replacement for platforms like BIMcloud – but as the layer that makes them resilient.

Where VKTRS Fits

At VKTRS, we are currently focusing on the backup and recovery layer.

This is the foundation.

Without reliable, usable backups:

  1. fallback is not possible
  2. recovery is uncertain
  3. continuity cannot be achieved

The broader continuity workflow – including working during outages and reintegration – builds on this layer and is part of ongoing development.

Takeaway

System failures are inevitable.

Operational disruption is not.

The difference lies in whether continuity has been designed – or assumed.

VKTRS explores the operational layer of BIM.
Not to replace existing systems – but to make them work when they don’t.