Back to vendors
C

Cosmon

Also known as: Cosmon Nexus, Cosmon AI, Nexus Engineering OS

Visit site
Entry priceSubscription with multiple tiers plus custom build outs (B2B licenses); no public list pricing foundFull pricing detail

Agentic engineering platform whose Nexus agent works inside installed CAD and simulation tools — SolidWorks, Ansys, COMSOL, Abaqus, Star-CCM+ — automating modeling, drawings and simulation setup from natural language, drivable from a documented Python SDK and runnable locally so design IP stays in the customer's network.

Cosmon builds Nexus, an agentic AI Engineering OS for mechanical and hardware engineering that sits above individual CAD, simulation (CAE), and PLM tools and automates not just tasks within each silo but the transitions between them.

Because the agent combines semantic understanding of requirements, geometric understanding of CAD, and physics understanding of solvers, it can run closed loop workflows that were previously impossible: a requirement change in SysML can autonomously trigger CAD updates, re run simulations under strict governance, and generate a traceable review package, all without human intervention until final sign off.

Nexus translates natural language requirements in tools like Jama or Cameo into exact boundary conditions and pass or fail criteria, performs physics aware geometry cleanup for meshing without deleting critical structural features, and indexes the actual physics and geometry of files so engineers can query prior art conceptually (for example past thermal analyses of battery packs with a specific cooling geometry).

It interprets PLM metadata so certification simulations only run on the correct released revision, and it optimizes the whole chain, balancing requirement margins, manufacturing constraints, and compute cost. Every AI decision is visible, traceable, and fully reversible and grounded in the customer's engineering sources of truth, engineers stay in control and grant permission for actions, and Nexus can run in the cloud or locally so proprietary engineering IP never leaves the customer's network.

Vendor details

Canonical URL

https://cosmon.com

Category

Enterprise operations agent

Funding status

Founded 2025 in San Francisco. Raised roughly $31M in venture funding (round dated April 29, 2026). CEO Aguiar, with a background spanning research and a prior computer vision and hardware engineering startup. Nexus is reported to be used by thousands of hardware engineers globally.

Company status

independent

Use cases & customers

Primary use cases

CAD automation and drawing generationsimulation (CAE) setup and analysisrequirement to design to simulation propagationPLM and engineering change managementdesign validation and optimization

Target customers

mechanical engineershardware and design teamsautomotiveaerospacemanufacturing and energy

Deployment options

SaaSon-premlocal (customer infrastructure)

Integrations

Integrates directly with the engineering toolchain: CAD (SolidWorks today, with CATIA, Inventor, Fusion 360, and Creo planned), CAE and solvers (for example Hypermesh, Ansys), PLM, and MBSE requirements tools like Jama and Cameo (SysML), navigating multi vendor APIs and offering custom build outs.

In practice

A requirement changes in SysML, and Nexus carries it through CAD updates and simulation reruns under governance to a traceable review package for the engineer's final sign off.

An analyst asks Nexus to run a static study on a SolidWorks bracket, and it cleans the geometry for meshing, assigns materials and boundary conditions, runs the solver and drafts the report for review.

An engineering team scripts Nexus from Python with the Agent SDK to run parametric variations in a nightly pipeline, with the work staying inside its own network.

Agentic Index coverage score

8.5 / 14 capabilities · 61%

Integrations & Tool Calling Full

Nexus writes into named engineering applications, connecting to SolidWorks, Ansys, COMSOL, Abaqus and Star-CCM+. The SDK adds Fluent and Ansys Mechanical, the change log adds Fusion 360 and Catia V5, NX is also named, and Jama and Cameo are named on the requirements side, eleven commercial applications across CAD, CAE solvers and requirements or MBSE tooling. The writes carry weight, with automated geometry edits, parametric variations, dimensioned drawings with GD&T and BOMs authored natively inside SolidWorks, mesh generation, material and boundary condition assignment, simulation runs and PDF export.

Changing geometry in a customer's CAD model is a write into their system of record, and a riskier one than a CRM update. The integrations are versioned and maintained. Release 0.1.22 moved the SolidWorks FEA agent into production, let Fusion 360 author drawings and export PDFs and expanded validated workflows for CATIA V5, alongside corporate proxy support, and a COMSOL AI agent shipped separately. There is no integrations page, supported version matrix or connector catalog.

Sourcedocs.cosmon.com front page, batch22a and batch19a change entries, pypi.org cosmon-agent-sdkread 2026-09-13

Workflow Orchestration Full

Nexus orchestrates across tool boundaries, which is the product's whole thesis. Cosmon places engineering AI above the individual platforms, automating not just tasks inside each silo but the transitions between them, from requirements tool to CAD to solver to PLM. A closed loop runs the full chain, from a requirement change in SysML through CAD updates and simulation reruns under governance to a traceable review package.

The steps are set out one by one, from turning natural language requirements into exact boundary conditions and pass or fail criteria, through geometry cleanup for meshing that understands the physics and keeps critical structural features, material and boundary condition assignment and solver runs, to results interpretation and report drafting.

In the SDK, a single client.run() call such as "Run a static study on bracket.sldprt" emits a sequence of typed ToolCall events, and runs can work for many minutes. Agents are addressed by name (agent="solidworks"), so work is routed to specialized agents, and a SolidWorks FEA agent and a COMSOL agent moved into production separately.

Because the SDK lets a customer batch, script and embed Nexus in their own pipelines, the customer composes the sequence and its surrounding logic in their own Python instead of accepting a fixed pipeline.

Sourcedocs.cosmon.com CAD and CAE sections, pypi.org cosmon-agent-sdk run model, cosmon.com Engineering OS positioningread 2026-09-13

Knowledge Grounding & RAG Full

Nexus indexes engineering artifacts, not just documents. Cosmon describes indexing the actual physics and geometry of files so engineers can query prior work by concept, for example past thermal analyses of battery packs with a particular cooling geometry, which is retrieval keyed on geometry and physics against a stored corpus.

Nexus works directly inside the customer's engineering software, understanding designs and running simulations, and Cosmon names multimodal geometry technology that understands CAD structure, physics and design intent. In the SDK, "What's the max von Mises in bracket.sldprt?" is answered from a model file.

Grounding comes from the customer's systems of record, geometry in CAD files, results in solver output and requirements in Jama or Cameo, with PLM metadata interpreted so certification simulations run only on the correct released revision. Natural language requirements become exact boundary conditions and pass or fail criteria, so the numbers come from the requirement document, not the model.

Outputs are grounded in the customer's engineering sources of truth and produce a traceable review package, so a result can be traced back to the requirement and revision it rests on. Cosmon does not disclose its index technology, embedding approach or retrieval mechanism.

Sourcedocs.cosmon.com front page, cosmon.com multimodal geometry section, pypi.org cosmon-agent-sdk worked exampleread 2026-09-13

Human Oversight & Guardrails Full

Oversight is a setting, and the interactive path is review and approve. In the SDK, whether a run is attended is set when the client is built, by whether handlers are supplied, so a caller decides in code whether the agent may proceed alone or must call back to a person. Cosmon sets the gate for each workflow.

Nexus diagnoses solver issues and proposes fixes that a person reviews and approves before any change is made, flags manufacturability, assembly risks and cost issues for the engineer to decide on, and interprets simulation results and drafts reports for review and sign off.

Engineers grant permission for actions, and even the closed loop case, where a requirement change carries through CAD updates and reruns simulations under strict governance, runs without human intervention only until final sign off. Every AI decision can also be reversed. Cosmon frames it as engineers deciding the direction while Nexus executes.

There is no approval queue, no risk tiering by action, no record of who approved what, and no policy at the organization level that forces attended mode, so whoever writes the client chooses, and an engineer can opt out of their own oversight.

Sourcepypi.org cosmon-agent-sdk attended versus unattended, cosmon webinar workflow descriptions, docs.cosmon.comread 2026-09-13

Security, Identity & Governance Partial

There is no attestation, but a thin access model for each user exists. There is no SOC 2, ISO 27001 or GDPR statement, no named auditor or report and no trust center. Local deployment that keeps IP inside the network is a deployment property, interpreting PLM revision rules is integration with the customer's PLM, and keeping designs confidential is a promise, not a mechanism.

The SDK's identity model is a real control customers use. Each user works with their own login and credits, code never holds a key, capability is bound to the signed in installed app instead of a shared secret, and Developer access is a setting a user must turn on before the local MCP server can be driven. There is no SSO, SAML, RBAC, SCIM or admin console.

Sourcedocs.cosmon.com, pypi.org cosmon-agent-sdk authentication modelread 2026-09-13

Observability & Auditability Full

Each run exposes a step by step trace, and agent actions can be undone. Cosmon says every AI decision stays visible, traceable and fully reversible, and the SDK supplies the mechanism, since iterating a Run yields typed ToolCall and TextChunk events, with the example printing each tool step as it happens (print(f"[{event.summary}]")) while the answer streams token by token. A caller can watch which tools the agent used, in order, with a summary of each, while the run is in progress.

Reversibility means an agent action on a CAD model can be undone, which requires the platform to know what it changed, and on a product that edits geometry in a customer's system of record, that is the auditability that matters. A closed loop change produces a traceable review package that keeps the record of what was done for sign off. Coverage reports, solver diagnostics and manufacturability findings describe the customer's part, not the agent. There is no retention period, saved run history a customer can browse later, or admin audit log across users, and the trace is available to whoever calls a run.

Sourcepypi.org cosmon-agent-sdk event streaming, cosmon.com traceability and reversibility claimsread 2026-09-13

Memory & State Persistence Not documented

Indexing and recalling past analyses as institutional knowledge is a retrieval corpus about the customer's designs, which is knowledge, not state the agent keeps about its own work. No agent carries state across runs.

There is no memory scope by user, project or agent, no published lifetime or retention, no expiry or purge path, no way to read or write accumulated state, and no recall of a previous run as distinct from a previous file. The SDK points the same way.

A run is created by Client.run(), yields typed events and returns an answer, nothing in the client saves, names, resumes or refers to an earlier run, and attended or unattended mode is set for each client, not carried forward.

Sourcedocs.cosmon.com, pypi.org cosmon-agent-sdk run modelread 2026-09-13

Deployment & Data Residency Full

The customer chooses where Nexus runs, in the cloud or locally, so proprietary engineering IP never leaves the customer's network. Nexus ships as an installed desktop application, with release notes on a desktop app subdomain, an SDK that needs an installed, signed in Cosmon app, and capability that comes from the CAD software on the engineer's machine. Software running on the engineer's own workstation against locally installed CAD puts the software where the customer is, which is different from a residency promise about a vendor cloud.

Release 0.1.22 added corporate proxy support for managed networks, which a vendor builds only because customers run the product inside controlled corporate networks. Geometry and simulation results from before a product's release are among a hardware company's most closely held assets. No region, region list, country or residency commitment is named for the cloud option, and nothing describes what local deployment involves.

Sourcedocs.cosmon.com, pypi.org cosmon-agent-sdk installed-app model, batch22a change entry on corporate proxy supportread 2026-09-13

Prebuilt Agents / Templates / Packs Partial

Named agents for each tool can be selected, but no catalog exists. Agents are addressed by name in the SDK (client.run("...", agent="solidworks")), so a customer chooses which agent does the work, and the change log names them as separate shipping units, with the SolidWorks FEA agent moved into production and a COMSOL AI agent released separately.

The capabilities fall into families, CAD (modeling, drawings, DFMA, tolerance stack up and reverse engineering) and CAE (simulation preprocessing, troubleshooting and postprocessing). There is no agent gallery, lasting page for each agent, template library, enable or install action, or entitlement language, and documentation of what the product can do is not a set a customer picks from. Custom build outs are professional services.

Sourcedocs.cosmon.com CAD and CAE sections, pypi.org cosmon-agent-sdk agent parameter, batch22a and batch19a change entriesread 2026-09-13

Triggers & Channel Coverage Partial

Nexus can run unattended from a customer's pipeline, but it is not confirmed that it starts on its own from an engineering event. Cosmon's insights pages describe change carried through the toolchain by events, where a requirement change in SysML can autonomously trigger CAD updates, rerun simulations under strict governance and generate a traceable review package.

There are two ways in, both started by the caller, working with the agent in the app or driving the same agent from the customer's own Python with the Agent SDK. Unattended runs are supported, and the SDK exists to batch, script and embed Nexus in pipelines, so a pipeline can call Nexus on a commit or a nightly build with no person involved, though the scheduling belongs to the customer's CI, not to Cosmon. Nothing shows Cosmon itself watching a requirements tool or PLM revision and firing.

Sourcedocs.cosmon.com invocation paths, pypi.org cosmon-agent-sdk unattended moderead 2026-09-13

Model Flexibility & Routing Not documented

The customer does not choose the model, and none is named. Cosmon describes multimodal geometry technology that understands CAD structure, physics and design intent, trained on thousands of synthetic engineering problems across domains, which points to proprietary geometry models, and a vendor that trains its own models has a coherent reason to fix the stack.

There is no model selector, admin control, model setting per agent or run, disclosed routing, or bring your own model or key path, and the SDK's run signature takes a prompt and an agent name with no model argument. No provider, model family or version is named, and Cosmon contrasts Nexus with generic agents built on LLMs without saying what sits underneath. A hardware company sending geometry before release cannot learn which model reads it.

Sourcecosmon.com multimodal geometry section, docs.cosmon.com, pypi.org cosmon-agent-sdk run signatureread 2026-09-13

APIs / SDKs / MCP Extensibility Full

Cosmon publishes a Python SDK for driving its agent. Agent SDK is one of five top level cards in the documentation, offering to drive Nexus from Python to batch, script and embed it in pipelines, with its own section at /sdk/overview, and the product can be used in two ways, interactively in the app or driven from the customer's own Python.

The package is cosmon-agent-sdk on PyPI, published from support@cosmon.com, with four releases through 0.1.3, installed with pip install cosmon-agent-sdk. Its client surface includes Client(), client.run(prompt, agent=...), a Run object with .text(), typed ToolCall and TextChunk events for streaming, attended or unattended mode set by whether handlers are supplied, and a cosmon doctor diagnostic command.

Under the hood the SDK is a small MCP client that finds the running app, connects to the local MCP server it exposes and drives the agent through one run tool, once the user turns on Settings > Developer access. The caller's code brings the request and the installed app brings the capability (the user's login, credits and local CAD software), so the code never holds a key. The SDK is marked alpha at 0.x, with breaking changes expected.

Sourcedocs.cosmon.com Agent SDK section, pypi.org cosmon-agent-sdk published by support@cosmon.comread 2026-09-13

Testing, Debugging & Optimization Not documented

Nothing tests the agent itself. Cosmon's testing is about the customer's design, since running a simulation to prove a bracket survives a load, flagging manufacturability and draft issues, checking tolerance stack up and diagnosing a solver that failed to converge all evaluate the customer's part, not Nexus. Design validation, issue detection and holistic optimization are not agent evaluation.

There is no harness for agent output, scored cases, regression suite over generated geometry, golden set, judge, comparison between agent configurations or accuracy figure for the agent's own work. Cosmon says Nexus is trained on thousands of synthetic engineering problems across domains and delivers best in class outcomes where generic agents built on LLMs fall short, with no benchmark, comparator or number. Being able to undo a decision is control after the fact, not a test before it.

Sourcecosmon.com product claims, docs.cosmon.comread 2026-09-13

Browser / Computer-use Not documented

Nexus drives desktop CAD on the engineer's machine, but nothing shows it doing so through the screen. It ships as a desktop application that works directly inside the customer's engineering software, connecting to SolidWorks, Ansys, COMSOL, Abaqus and Star-CCM+, the capability is local (the installed app brings the user's login, credits and local CAD software), and the change log adds a Nexus Connector and corporate proxy support for managed networks. An agent driving locally installed desktop CAD comes close to local computer control, but the interface decides it.

Every CAD and CAE application named, including SolidWorks, Ansys, Abaqus, COMSOL, Fluent, Star-CCM+, Fusion 360 and Catia, exposes a scripting or automation API, the ordinary way software drives them, and the published outputs are what those APIs produce, fully dimensioned engineering drawings, multiple views, sections, GD&T and BOMs inside SolidWorks, mesh and boundary condition setup, and PDF export. Nothing from Cosmon describes screen capture, cursor control, pixel reading or targeting interface elements.

Sourcedocs.cosmon.com front page, pypi.org cosmon-agent-sdk, cosmon.com SolidWorks drawing outputsread 2026-09-13

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Product updates

·IntegrationsVerified

Argus, Cosmon's CAD agent, now works in CATIA V6, running it alongside CATIA V5 as separate application instances. Version 0.1.35 also adds Creo 9 and 10 to the Creo 11, 12 and 13 releases it already handled. When a user presses Stop, the agent now keeps the work in progress instead of throwing it away.

Bears on: Browser/computer use

View source
·IntegrationsPartially Verified

Cosmon's Argus agent can now drive AutoCAD, added to the CAD and simulation tools it already works in, in desktop release 0.1.31. The same release adds chat export and per chat model and effort controls.

Bears on: Browser/computer use

View source
·IntegrationsPartially Verified

Nexus version 0.1.22 expands CAD tool support, moving the SolidWorks FEA agent into production and enabling Fusion 360 to author drawings and export PDFs. The update also adds corporate proxy support for managed networks and expands validated workflows for Catia V5.

Bears on: Integrations

View source
View all 4 Cosmon updates →Tracked since Aug 2026 · Verified from public vendor sources

Pricing

Subscription with multiple tiers plus custom build outs (B2B licenses); no public list pricing found

subscription tiers plus custom build-outs (B2B licenses)

Cost watchouts

Custom build outs for additional CAD/CAE/PLM integrations and local (on premise) deployments likely add to cost. Pricing scales with seats and the breadth of integrated engineering tools.

Variable cost rationale

Cost scales with seats, the number of integrated engineering tools, and any custom build outs or local deployments, though a subscription base caps the core fee.

Sales call required

Mixed (some tiers require a call)

Free / trial

No public free tier confirmed; paid B2B product

Lowest paid plan

Not retrieved this session

Key ambiguities

Subscription tiers exist but exact prices were not retrieved. Split between standard subscription and custom build out fees is not disclosed.

Agentic Index verified 2026-07-08

Alternatives to Cosmon

The closest documented capability profiles to Cosmon among enterprise operations agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.

  • Enboarder9.0 / 14Adds documented Testing, Debugging & Optimization
  • Rapta9.0 / 14Adds documented Testing, Debugging & Optimization
  • VantedgeAI9.0 / 14Fuller documented coverage on Prebuilt Agents, Templates & Packs and Triggers & Channel Coverage
  • Board9.5 / 14Adds documented Memory & State Persistence
  • Clio10.5 / 14Adds documented Memory & State Persistence
  • Coupa9.5 / 14Fuller documented coverage on Security, Identity & Governance and Prebuilt Agents, Templates & Packs

Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded

Head to head

Contact us

Found a vendor we missed? Have feedback on the index? We'd love to hear from you.