Boundaries we have engineered
Interoperability is not one technique. It is the right bridge for each pair of systems - and the discipline to keep a single source of truth on one side of that bridge.
Rhino–Revit façade pipeline (HKS LINE) - Parametric façade design stays in Grasshopper; Revit receives procedural curtain-wall families with materials, adaptive parameters, tagging, and drawing extraction depth comparable to hand-built façades. Refined across three complex production projects.
VolcanoSnail / THERM (HKS LINE) - THERM ships without a public SDK. We reverse-engineered inputs and outputs, orchestrate headless solves, and return thermal bridging insight inside the Grasshopper loop - batch scale, defensive handling of unstable models, repeatable QA.
Supawood Concept Creator - Grasshopper/ShapeDiver geometry drives a custom TypeScript web UI. Architects configure ceiling systems in the browser; CNC-ready outputs, specs, and fire ratings flow from the same parametric definition - sale-to-delivery compressed from months to days.
Karamba3D GH1/GH2 - One computational core, two Grasshopper hosts - interoperability between platform APIs via adapters rather than duplicated structural logic.
Project Shark - Live compression pipeline from Grasshopper to Android AR at 1:1 scale; the canvas remains authoritative while stakeholders review in context.
Verse3 - Event-driven visual scripting with Rhino interoperability - exploring host-agnostic computational graphs for design and AEC research.
Typical engagement
We start with a workflow audit: which tools, which parameters, which deliverables, and where data is being recreated by hand. We prototype the highest-risk boundary first - often Revit landing, solver orchestration, or cloud execution - then harden for production with your team's review cycles built in.
Outcomes teams measure
- Fewer manual re-exports - Geometry and parameters survive the trip; schedules and quantities stay tied to the model.
- Faster optioneering - Batch studies (thermal, layout, façade variants) replace one-off desktop sessions.
- One team owns the chain - No separate "integration consultant" disconnected from the plugin or web work.
- Upgrade resilience - Tests and documented failure modes when host applications change APIs or file formats.