Design. Prove. Ship.

An agent that designs robots from real parts,
inside the workspace your team already reviews in.

See the loop

Design partner program · open

Scroll down

Hardware revs weekly.The model doesn’t.

The handoff from mechanical to simulation is a zip of meshes, hand-edited XML and tribal knowledge. A 510-respondent survey of URDF users by Tola and Corke found the format cannot express the closed chains humanoids are actually built from — so every engine gets its own private fix. Changes land with no diff, and the training run finds out first.

The four-bar knee, run both ways.

Today

The knee is a closed chain, so URDF cannot express it. Every engine gets its own hand-maintained hack, and the three disagree.

CadSyn

The loop is an equality constraint in the MJCF core. Export to URDF and the report says what did not carry over.

OutcomeThe model stops trailing the hardware — every rev compiles, every change is reviewable, and the same model is the one that reaches the customer.

See the plans
weeks hand-built sim model
per hardware rev
= same rev
15 min compiled from CAD
valid in MuJoCo

Design target from the CadSyn spec · measured from CAD connect to first valid model

One workspace · eight pillars

  • AGENTDesign
  • SYNCDesign
  • MODELDesign
  • SIMProve
  • REVIEWProve
  • CATALOGSource
  • SCENEShip
  • PLATFORMShip

Start with the model.Everything else follows.

One living model of the robot — every engine, every reviewer and every customer reading from the same revision.

1 / 3

Design

Describe the robot, or upload a CAD bundle. The agent drafts the kinematic tree, picks parts your team has signed from the catalog, and compiles MJCF and URDF with the closed chains intact.

2 / 3

Prove

Settle, payload, actuation and, on floating designs, drop checks run in MuJoCo before a human looks. The agent refuses what it can’t build and lists what it dropped.

3 / 3

Ship

The change arrives as a reviewable diff with the sim evidence and the BOM attached. Approve it, then share the same model as a link a customer can open.

The eight pillarsCadSyn ships behind.

Pillars cut along the question an engineer is actually asking — can I get it into a model, can I prove it, what is it made of, who else can see it.

The front door — describe the robot and it drafts the structure, picks parts your team has signed and runs the checks in simulation before a human reads a line of it.

  • Supplier‑groundedPayload, reach and DOF resolve to parts a person on your team has signed; budget works once the catalog holds prices
  • Simulation is the compilerSettle, payload and actuation checks, plus drop on floating designs, run before a human reviews
  • Changes as pull requestsAgent actions land in the same history humans use, never silently
  • Lint on pastePaste a URDF and get the lint and its deterministic one-click fixes
  • Deterministic templatesArms, a 12-joint quadruped and a pan-tilt head. It refuses what it can’t build and lists what it dropped
  • Model Q&AAsk a model about its reach, mass, reflected inertia or what its parts cost
  • Prompt‑to‑sceneEnvironments from text across five hand-built types
  • Dogfooded toolingThe agent uses the same MCP tools third-party agents get

CAD stays the source of truth, so the model is compiled from it rather than rebuilt by hand every rev.

  • CAD bundle uploadBundles from a CLI extractor, with a mapping UI for the assembly
  • Sync diffingDiffs per revision, and each later sync opens a review
  • Onshape & SolidWorksThe Onshape connector and the SolidWorks add‑in are in development

MJCF at the core, because the closed chains a humanoid knee actually uses cannot be written in URDF at all.

  • MJCF‑first coreClosed chains as equality constraints, with a degradation report on export
  • Variants without macrosNamed configurations you can preview and export, not Xacro macros
  • ImportURDF, MJCF, Xacro and SDF, by folder, archive, single file, drag and drop, or pasted text
  • Asset & path managerMeshes as managed assets, with package:// and relative paths rewritten in each export archive
  • Collision & inertiaConvex decomposition per link on click, inertia from CAD mass properties, unit checks and one-click autofix
  • Self‑collision matrixA matrix view of contact exclusion pairs, instead of reading them out of XML
  • Model lintingLint on every compile, with deterministic one-click fixes
  • Frames & posingFrame editing, distance and clearance measurement, pose libraries and a reach figure
  • Sensor placementCameras, lidars and IMUs placed on the model, with FOV frustums

Physics in the browser tab, validation in MuJoCo, and exports for the rest of your pipeline.

  • In‑canvas physicsMuJoCo WASM play, pause and joint drag, with contact, center-of-mass and inertia overlays. Closed chains are kept
  • Validation in MuJoCoValidation runs in MuJoCo; MJCF from a clean download loads there for 109 of 113 corpus models. Isaac and Gazebo runners are planned
  • Export presetsMJCF, URDF, SDF, MJX, ROS 2 package and USD archive, each with its meshes and a report of what did not carry over
  • Domain randomizationA randomization form, exported to Isaac Lab and MJX
  • Trajectory playbackCSV, MCAP including zstd and lz4, and rosbag2 MCAP replayed on the model
  • System identificationJoint friction and damping fitted from telemetry
  • Hardware mirrorA Web Serial mirror of joint state, wired and not yet tested on hardware

Branches, diffs, comments and approvals — the review flow the software half of your team already has.

  • Cloud model, share linksViewer, commenter, customer and supplier links, with no account
  • Supplier collaborationVendors comment on the parts they supply, through a link, not in an email thread
  • Branches & mergeBranches to work on and save to, required approvers, and an Update from main with a conflict picker that shows both values
  • 3D visual diffStructural tree diff plus changed-geometry highlighting between any two revisions
  • Pinned commentsResolvable threads attached to a link, a joint or a point on a part
  • CI integrationWebhooks your own CI can listen to
  • Local syncA sync CLI mirrors the workspace to files on disk in your own repo

Real parts from public datasheets, signed by a person on your team before the agent can use them — the reason a generated design comes with a bill of materials.

  • Seeded catalog21 actuators from public datasheets, unverified until a person on your team signs each one
  • Your parts, your pricesEnter prices and lead times and add your own parts. The seed holds no prices, lead times, torque curves or thermal data
  • Joint‑to‑SKU referencesA joint can cite a part your team has verified, not an abstract effort number
  • Vendor programA claim flow for actuator makers is planned
  • Bill of materialsEach agent design opens for review with its BOM
  • Auto‑generated datasheetsOne-click spec sheet — kinematics, mass properties and BOM — as a PDF

The share link becomes the sales tool: a customer configures and views the robot in a browser tab, with no CAD seat and no zip file.

  • Parameterized sharesParameter controls on a customer-facing link, with no account
  • Scenario authoringEnvironments from text across five hand-built types, object sets and spawn randomization, all versioned
  • Embeddable viewerA white-label viewer with your logo, embedded in your own site

Reachable by code — and by the agents your team already runs. None of it is published publicly yet.

  • Python SDK & registryAny robot at any version, pulled programmatically — semantic versioning included
  • Model hubWorks inside a workspace, with license and provenance. A public hub is planned
  • MCP server & render APIAgents read, lint, modify and screenshot models; the same tools power the in-house design agent
  • Foxglove interopPublish to Foxglove; take MCAP logs back
  • Enterprise readinessRBAC, audit trails and a self-hosted Docker stack
Read the full spec

The complete CadSyn product spec, all eight pillars · released on request

Open where it counts.Hosted where it matters.

Loaders, viewer, SDK and the sync CLI are planned to be open source; nothing is published yet. Cloud sync, diff, review, the agent, the catalog and the configurator are ours to run, with a self-hosted Docker stack for teams that need their own.

Start a design partnership

Tiers are planned. Three to five design partners for the first cohort.

  1. 01 · Connect

    A CAD bundle, or your URDF, MJCF, Xacro or SDF. Onshape and SolidWorks connectors are in development.

  2. 02 · Compile

    Joints, actuators, closed chains — linted every time, with fixes.

  3. 03 · Review

    Every change, human or agent, is a diff with sim evidence attached.

  4. 04 · Share

    One link to a teammate, a supplier, or your customer’s browser tab.

One model,every place the robot has to exist.