Welcome to agentic systems engineering.
synapse™ is the operating system for fast-moving hardware teams. One live SysML v2 model where agents and engineers design, verify and deliver complex systems.
An animated walk through synapse™ on a satellite project. An engineer asks the agent to swap the payload camera. The agent makes the change on a branch, reruns the budgets and reports that one power requirement no longer holds. The same change then shows on the dashboard, in the architecture, in the requirement tree and in the workflow that regenerates the interface control document.
What does the camera swap do to the payload line?
Marc replied 2m · started by Isa
Isa
Marc2m
Claude Codesynapse MCP
> check the HR-250 swap against power
●synapse · get_part (Payload)
●synapse · run_workflow (Mass & Power Budget)
●synapse · check_requirements
⎿REQ-CUST-006 violated: 96 W > 90 W
●synapse · update_attribute (duty_cycle)
⎿payload_power 88 W. 124 requirements hold.
SEN-482In progress
Rework the payload harness for the HR-250 camera
Created by synapse™ from
AAltium 365Synced
PDU board, revision C
Trace width now checked against
Payload Power Availability
On orbit average the payload shall draw
186.1kg+3.7
The operating system
Model-based systems engineering for hardware, on one connected model.
synapse™ keeps architecture, requirements, verification and documents on one SysML v2 model. Agents work on a branch, and an engineer reviews every change before it merges.
Engineers build the system in trees, tables and diagrams. synapse™ writes the SysML v2 model underneath, so the whole team works on one architecture and nobody learns a language first.
Learn more
01Model in SysML v2
Engineers build the system in trees, tables and diagrams. synapse™ writes the SysML v2 model underneath, so the whole team works on one architecture and nobody learns a language first.
02Watch the system react
Budgets, margins and derived values are formulas on the model. Change a part and every rollup updates and every requirement rechecks, so you see the impact propagate live.
03Trace every requirement
Every requirement links to the parts and values that satisfy it. When a value changes, synapse™ checks the constraint and shows what went out of date, all the way up to the mission.
04Version your system
Explore design options in parallel branches, review each change with partners and customers on the model itself, and keep the design decisions tracked.
05Automate your workflows
Workflows run your code on live model data, write the results back and produce the documents. An interface changes and the ICD is regenerated, not rewritten.
06Delegate to agents
Ask in plain language. The agent reads the model, makes the change on a branch, runs the checks and hands you a review, with the same permissions as the engineer who asked.
07Build once, reuse everywhere
Anything you model once can be imported into any project as a versioned library. When a new version is published you see the full diff and its impact on your requirements and budgets.
The system is broken
Your system is described in five places, and none of them agree.
A requirement changes. The mass budget sits in a spreadsheet, the interface in an ICD, the analysis in a script. Nothing flags what just went out of date, and the gap surfaces in manufacturing, when it is too late.
Up to
0%
of engineering time can be regained with synapse™.
synapse™ is the only MBSE platform with
The entire value chain
Most teams start in a spreadsheet, move to a requirements tool, then migrate again when the programme needs a real model. synapse™ covers the whole path, from your first requirements and system parameters to SysML v2 modelling and full V&V. You grow into it. You never migrate off it.
MBSE
One SysML v2 model underneath every view. Import and export .sysml files any time.
Requirements management
Requirements tied to the design values that satisfy them, with the trace kept for you.
V&V
Verification planned, run and evidenced against the same model the design lives in.
Automation
Workflows rerun when the model changes. Budgets, analyses and ICDs stay current.
Observability and governance
It logs itself. Every change has an author, a reason and a review, human or agent.
Integrations and MCP
Your tools finally talk. Jira, Altium, Python and any AI client connect through the API and MCP.
Get started
See it on your own system.
A 30-minute walkthrough on a system like yours. No modelling language to learn.
- Deployed in days, not monthsNo methodology training
- SysML v2 compliantImport and export .sysml files
- Agents under your rulesSame permissions, same review
