VitruAI + Speckle
VitruAI for Speckle authenticates against a firm’s Speckle workspace and reads and writes streams that VitruAI translator and interop agents consume, including geometry, parameters, and classifications. It supports Speckle’s hosted speckle.xyz, on-prem Speckle Server installations, and Speckle Automate webhooks, and is currently shipping with 1–3 design partners running Rhino-to-Revit and Grasshopper-to-Revit hand-offs through Speckle.
- Reads and writes Speckle streams natively so geometry, parameter data, and classification stay aligned between Rhino, Grasshopper, Revit, and IFC connectors.
- Powers the Rhino↔Revit Interop Agent as the preferred hand-off path for firms with an active Speckle workspace and open-BIM requirements.
- Connects to Speckle Automate so agents can be triggered by stream events and post QA/QC, translation, or compliance results back to the same stream for downstream tools.
Install, authentication, and what runs through the integration.
-
Personal access token authentication
An admin issues a workspace-level Speckle personal access token, and VitruAI stores it encrypted per tenant with rotation policies aligned to the firm’s IT standards. Integration scopes follow Speckle’s token permission model, so agents can only read and write the specific streams the token grants. This keeps Rhino-to-Revit translation workflows controlled while still giving VitruAI enough access to process geometry, parameters, and branch history.
-
Hosted speckle.xyz and on-prem Speckle Server
VitruAI for Speckle connects to both Speckle’s hosted speckle.xyz service and self-hosted Speckle Server instances on the same code path, so firms can keep a single configuration across projects. On-prem servers need an outbound HTTPS route to the VitruAI tenant plus a one-time IT review of the single FQDN and IP range. Once approved, agents can move data between Rhino, Grasshopper, and Revit connectors without exposing additional inbound ports.
-
Speckle Automate compatible
VitruAI agents subscribe to Speckle Automate webhooks so commit-to-main, branch-merge, or tag events can trigger runs without manual clicks. A Grasshopper designer can push a new stream version, have an Automate function call a VitruAI endpoint, and receive translation or QA/QC results written back as new branches or commit comments. This pattern works for geometry translation, open-BIM checks before IFC export, or pre-flight checks before publishing to Revit.
-
Object-classification preserved across tools
VitruAI reads and writes Speckle object kit semantics so classifications produced by Rhino, Grasshopper, and Revit connectors stay intact through each hand-off. Category, family, type, and custom property mappings are preserved when the Rhino↔Revit Interop Agent runs, which reduces rework on the Revit side and keeps schedules and filters stable. This also improves downstream IFC and openBIM exports because element intent remains clear in the Speckle stream.
-
Outbound HTTPS only with regional tenancy
The integration uses outbound HTTPS only, with a single FQDN and documented IP range that IT can pin in firewall rules. Tenant regions are currently eu-central or me-central, so firms can keep Speckle traffic within a preferred jurisdiction while still connecting to speckle.xyz or on-prem servers. This model fits existing security reviews for Rhino-Grasshopper and Revit plug-ins and avoids opening new inbound ports.
-
Rhino and Grasshopper into Revit via Speckle streams
VitruAI agents consume Speckle streams produced by Rhino and Grasshopper connectors, translate them, and write Revit-ready geometry and parameters back to Speckle or directly into Revit. Firms already invested in Speckle can keep their existing stream structure while adding VitruAI’s translation and QA/QC passes. This keeps the same Rhino↔Speckle↔Revit pattern already used for many Rhino-to-Revit translation workflows, but adds automated checking before elements land in the model.
Speckle integration — common questions from BIM and Digital Practice teams
-
Does this work with on-prem Speckle Server?
Yes, VitruAI for Speckle connects to on-prem Speckle Server instances over the same API path it uses for speckle.xyz. The only requirement is an outbound HTTPS route from the Speckle Server network to the VitruAI tenant’s single FQDN and IP range. Most firms run a one-time IT review, then allow agents to process streams used for Rhino, Grasshopper, and Revit coordination.
-
Does it integrate with Speckle Automate?
Yes, VitruAI agents subscribe to Speckle Automate webhooks so events such as commit-to-main or branch-merge can trigger runs. An Automate function can call a VitruAI endpoint, wait for translation or QA/QC to finish, and then write results back into the same stream as new branches or commit metadata. This is useful for pre-flight checks before Revit publishing or IFC export in open-BIM pipelines.
-
Is Speckle the only hand-off path between Rhino and Revit?
No, VitruAI also supports a direct plug-in-to-plug-in path between Rhino and Revit for firms that do not use Speckle. For practices with an existing Speckle workspace, Speckle is usually the preferred path because it keeps a single source of truth for streams already used by Rhino-Grasshopper integrations and downstream Revit models. Both paths are supported by the Rhino↔Revit Interop Agent and can run side by side on different projects.
-
What permissions does the workspace token need?
The Speckle personal access token used by VitruAI needs stream read and stream write permissions on the projects where agents will run. An admin-level token is not required; many firms issue a service token scoped to a small set of Rhino-to-Revit or Grasshopper-to-Revit streams. This keeps access tight while still allowing translation, QA/QC, and open-BIM checks before data flows into Revit or IFC exports.
-
What does the Beta cohort look like?
The Beta cohort currently includes 1–3 design partners with active Speckle workspaces and live Rhino-to-Revit or Grasshopper-to-Revit hand-off flows. Typical teams include a BIM manager, a Rhino or Grasshopper power user, and a Revit lead coordinating models that also export to IFC for openBIM integrations. Each Beta deployment ships a per-project accuracy and performance report calibrated to the customer’s Rhino↔Speckle↔Revit pipeline.