Overview

Clone is a third-party client for Speckle, the open data platform for AEC. It signs in against a Speckle server, lists the projects and workspaces you already have there, and opens their models in a 3D viewer with filtering, comparison and property analysis on top.

It is not a fork of Speckle's own web app and it does not use Speckle's private hosted viewer code. It talks to the same public GraphQL and REST APIs that any registered Speckle application can use, and renders with the published @speckle/viewer package. Everything below describes what is actually implemented, including the parts that are not.

What it is for

Speckle already gives you a capable web app. Clone exists to try things that are awkward to try inside a large product: reading the new Parquet-backed model bundles directly in Node, treating model properties as a queryable dataset rather than an inspector panel, and putting two versions of a model side by side with synchronised cameras.

The tagline on the front page — another Speckle app — is meant literally. This is a place to prototype, not a replacement.

What it does not do

Stated plainly, because a feature list that omits its own gaps is not much use:

• Instance placements and definitions, and several analytic geometry primitives, are not decoded.
• Bundles above the size limits need a streamed or worker-based pipeline that does not exist.
• There is no cross-user server cache; geometry and properties are sent together, so deployment response-size limits apply.
• The property-export API returns whole tables, not server-filtered results, so filtering is a client-side operation over a fully downloaded dataset.
• There is no Parquet analytics service, no embedded Speckle Intelligence chat, and no external automation subscriptions.
• Version comparison is visual and camera-synchronised; it does not yet diff properties or quantities against stable authoring identifiers.