CAD connector strategy

Embedding Dry into CAD workflows

Dry should embed into CAD as the compiler, verification and report layer below host-specific geometry, document state and UI. The host owns design intent extraction. Dry owns IR, simulation, verification, reports and target output.

PatternsHostsMVPs

Ownership Boundary

Host CAD owns

Design context

• geometry selection and feature context;
• native UI, document state and authentication;
• B-rep, mesh, sketch and curve extraction;
• workflow persistence and collaboration.

Dry owns

Compiler behavior

• Dry IR and G-code import/export;
• toolpath lowering, verification and simulation;
• machine/material/process profiles;
• trace, compare, rewrite and report semantics.

Product boundary

Do not over-own CAD

• avoid generic B-rep modeling;
• avoid mesh repair and full slicing as first scope;
• avoid native feature-tree ownership;
• keep connector UI thin.

Integration Patterns

Local plugin calling Dry

Best for Fusion 360, Rhino/Grasshopper, Blender, FreeCAD and early SolidWorks prototypes.

Workflow: select sketch/curve/body -> convert supported intent -> call Dry CLI/SDK -> show report and G-code/IR.

Cloud app calling Dry service

Best for Onshape and enterprise/browser workflows.

Workflow: authenticate -> read document context -> run Dry cloud job -> return report/artifact link.

Post-processor hook

Best for low-friction pilots.

Workflow: host exports mesh/path/G-code -> Dry reviews, traces or rewrites -> accepted artifact is archived or uploaded.

Product SDK embed

Best for commercial CAD/CAM, slicer and manufacturing SaaS vendors.

Workflow: vendor product embeds Dry native/wasm/API service and exposes review/emit/report features.

Host Prioritization

Host	First motion	Why	Risk	Priority
Fusion 360	local add-in	fastest polished CAD MVP, strong maker/R&D overlap	packaging and OS support	1
Rhino/Grasshopper	components	best procedural toolpath fit	lower direct ACV	2
Onshape	cloud app + FeatureScript helper	strong cloud/platform story	auth, permissions and service complexity	3
FreeCAD	workbench/macro	open validation channel	weak revenue path	4
Blender	add-on	strong visual/demo surface	not manufacturing-native CAD	5
SOLIDWORKS	enterprise add-in/bridge	high-value industrial accounts	heavy Windows/enterprise burden	6

Host Playbooks

Fusion 360

Autodesk's Fusion API supports scripts, add-ins and applications that customize Fusion. Dry's best first move is a local add-in.

MVP:

1. Add command: Compile with Dry.
2. User selects sketches, curves, faces or a body.
3. Add-in converts supported entities to Dry design JSON or exports a supported artifact.
4. Add-in calls Dry CLI/Python binding.
5. Add-in shows metrics, verification findings and generated G-code/IR.

Commercial angle: best polished demo host for hardware teams, consultancies and advanced makers.

Rhino / Grasshopper

Rhino/Grasshopper is the best procedural-toolpath host because users already build geometry and process logic as graphs or scripts.

MVP:

1. Grasshopper components produce Dry path primitives or Dry IR.
2. Components call Dry to simulate, verify and emit.
3. Results render as preview curves, metrics and findings.
4. Example definitions cover custom infill, lattices and non-planar/robotic deposition.

Commercial angle: best early proof and research channel; package as support, workshops or advanced components.

Onshape

Onshape is cloud-native, exposes REST APIs, and supports FeatureScript custom features. Dry's best first move is a cloud integration with a small FeatureScript helper where useful.

MVP:

1. User selects a part, sketch, curve or Dry-specific custom feature.
2. Dry cloud integration reads document/element/version/workspace context through Onshape APIs.
3. Dry creates a review/compile job with machine/material profile selection.
4. Report, Dry IR and G-code artifacts are linked back to the document/app workflow.

FeatureScript role: express path primitives or manufacturing metadata close to the CAD model.

REST/API role: authentication, document context, export/import and artifact links.

Commercial angle: strongest cloud/enterprise story, but heavier product surface than Fusion or Grasshopper.

SOLIDWORKS

SOLIDWORKS has a mature desktop API and high industrial relevance, but the delivery burden is higher.

MVP:

1. Windows add-in or bridge exports selected sketches, curves or bodies.
2. Dry runs as local CLI/service.
3. Report and generated artifacts are attached to the project/workflow before deep UI integration.

Commercial angle: high-value later target after proof from simpler hosts.

Blender

Blender is useful for artistic and non-traditional deposition rather than classic CAD-first manufacturing.

MVP:

1. User selects curve, mesh or generated path object.
2. Add-on converts supported paths into Dry input.
3. Dry verifies, simulates and emits.
4. Blender shows preview and report metadata.

Commercial angle: demo channel for clay, concrete, food, silicone, composites and artistic FFF.

FreeCAD

FreeCAD is a good open-source validation host because it uses Python heavily and supports workbenches/macros.

MVP:

1. Workbench selects sketches, wires or paths.
2. Workbench exports Dry-compatible path/design data.
3. Dry CLI/Python binding verifies and emits.
4. Workbench displays verification summary and generated artifacts.

Commercial angle: adoption and community proof more than immediate revenue.

Recommended MVPs

MVP 1

Fusion "Compile with Dry"

Selected sketches/curves, one FFF profile, metrics, verification findings and G-code/IR export.

Exit: compile, verify and export in under 5 minutes.

MVP 2

Grasshopper components

Path primitives, profile selection, verify, simulate, emit and visual findings.

Exit: one definition generates a validated Dry toolpath without hand-written G-code.

MVP 3

Onshape cloud proof

Document context, FeatureScript metadata where useful, Dry cloud job and linked report/artifacts.

Exit: one Onshape document round-trips to Dry report and artifact links.

Commercial Packaging

CAD Connector Pilot

Buyer: hardware R&D team, advanced print lab or CAD/CAM integrator.

Price test: $7,500-$25,000 for a 4-6 week connector pilot.

Deliverables:

• one host integration;
• one profile;
• one validated workflow;
• one report template;
• documented limitations and next-step backlog.

Embed SDK for CAD/CAM Vendors

Buyer: CTO, VP Engineering or platform product owner.

Price test: $15,000-$75,000/year support/license, with custom OEM pricing if Dry ships inside a commercial product.

Deliverables:

• native/wasm/CLI integration path;
• conformance fixture;
• report schema mapping;
• compatibility/versioning agreement.

Source Notes

• Autodesk Fusion API overview
• Autodesk Fusion API documentation
• Autodesk Platform Services API documentation
• Onshape REST API introduction
• Onshape FeatureScript documentation
• Onshape custom features
• SOLIDWORKS API reference
• Rhino and Grasshopper developer docs
• Blender Python API
• Blender add-on tutorial
• FreeCAD Python scripting tutorial

The implementation playbook is maintained with the private product source.