ProductFlo is the orchestration layer for mission-critical hardware engineering. Agents read your schematics, firmware, CAD, and BOMs in place — catching pin mismatches, BOM drift, and cross-discipline ECO conflicts before they cost you a respin. Agents propose diffs. Humans approve. No migration. No rip-and-replace.
The graph — every part, every net, every dependency across mechanical, electrical, firmware, and manufacturing. Click any node to see everything it touches.
Open demo tab →AI design reviews & change control
ProductFlo turns every source file your team creates into shared context, and gives humans and agents one governed way to understand, review and validate changes across disciplines.
01 · ENGINEERING SOFTWARE
ProductFlo appears inside the tools engineers already use and keeps their source artefacts in the loop.
Onshape document panel is live. Altium, SolidWorks, GitHub, and KiCad integrations are in development.
02 · SOURCE UNDERSTANDING
Native engineering files become typed, queryable objects instead of opaque files in a vault.
03 · DEVELOPER ACCESS
Connect internal systems, automate workflows, and build on the same governed product context.
PRODUCTFLO CORE
Parts, assemblies, nets, pins, requirements, BOM lines, firmware symbols, and decisions become one versioned source of engineering context.
04 · REASON
ProductFlo agents read the graph, run scoped checks, and propose changes for human review.
05 · EXTEND
Give external agents governed graph context and scoped tools without handing them unrestricted source access.
MCP SERVER
Context + tools
06 · GOVERNED OUTPUT
Cross-discipline blast radius before a change is approved.
A proposed change with evidence, rationale, and owners.
Human approval, routing, and a signed change record.
A versioned trail of what changed, why, and by whom.
How it works
ProductFlo reads your existing tools in place, builds a typed graph of every part and connection, runs agents that draft safe changes, and gates every commit through the humans who should see it.
Parts · nets · signals · tolerances · suppliers · revs — one queryable graph across MECH / ELE / FW / MFG.
Scoped agents watch the graph, draft ECOs, and write diffs — never commits. They propose, humans approve.
Every change is a reviewable, reversible diff with the right reviewers auto-selected by discipline & ownership.
Approved ECOs are packaged as reviewable proposals for each target system. Native write-back is in development — ProductFlo never pushes changes silently.
// Supplier says J12 is EOL. Cascade everywhere it lives. const diff = await pf.propose.swapPart({ from: "J12", to: "J12-ALT-B", product: "robot-alpha", cascade: true }); await diff.requestReview({ auto_select: true }); ↳ eco-2041 · 7 artefacts · 5 disciplines · 3 reviewers
The surface a designer sees in the dashboard is exactly the surface an agent hits in code — typed, scoped, diffable, audit-logged.
Agents
All agents are scoped, auditable, dry-run-capable, and propose diffs; never commits. Bring your own models, or use ours.
Turns every rev into a human-readable changelog. Groups ECOs by theme, writes release notes, drafts MRB memos.
Answers "what breaks if…" in seconds. Powers the impact view and gives every ECO its blast-radius estimate.
DfM · DfA · DfT · DfR — drafted by the agents that own each concern, reviewed by you.
Keeps the design BOM, the mfg BOM, and the PLM BOM in sync. Flags drift, proposes AVL additions, routes to procurement.
Cross-checks FW duty cycles against heat-sink geometry and rail current budgets. Flags envelope violations at diff time.
Validates every pin assignment across schematic, firmware, and mechanical connector pinouts. Single source of pin truth.
Knows which artefact changes re-open FCC / UL / 510(k) / IEC cert gates. Flags the cost before the merge, not after.
Watches supplier feeds for EOL, lead-time, and MOQ changes. Drafts alternates keyed to your approved vendor list.
Write a custom agent in 20 lines. Scoped tokens, typed tool-calls, dry-run mode, audit log — all out of the box.
In-host plugins
No migration. No new tool to learn. No rip-and-replace. ProductFlo shows up as a task pane in SolidWorks, a bot on GitHub, and a panel in Onshape — serving the same live graph. The Altium side panel is in development for 2026.
Connect any tool and AI agent with our REST API/SDK/MCP. Define a schema, map fields to graph nodes, and ProductFlo keeps it in sync with webhooks or polling.
Firmware PRs that touch a pin are cross-checked against the schematic and reported as check runs with file-and-line annotations. Your branch protection decides what blocks — ProductFlo advises; it never blocks a merge.
See electrical and firmware dependencies on every part in your assembly. Clash-check against the live PCB outline. ECOs are proposed in ProductFlo and approved by you — in-place commit is in development.
Surface cross-discipline dependencies inside Onshape documents. See which electrical and firmware artefacts depend on every part and assembly.
Link Fusion 360 components to the product graph via the cloud connector. Mechanical changes surface as governed impact proposals — the in-host design workspace add-in is in development.
KiCad projects flow into the ProductFlo graph — net changes, footprint swaps, and BOM updates. Anything flowing back is a human-gated proposal, never a silent sync.
Shows ownership, cross-discipline impact, and open ECOs on whatever the engineer clicks. Propose a part swap without leaving the editor.
Import schematics and board layouts from Cadence tools into the unified graph. Pin-map validation and net-level impact analysis included.
Map Zephyr devicetree bindings to the hardware graph. Pin reassignments and peripheral changes are validated against the schematic before merge.
Planned: Windchill part structures and BOMs flow into the live graph, and ECOs authored in ProductFlo will draft Windchill change notices for your approval — nothing sent without a human.
Planned: sync Arena BOMs, approved manufacturer lists, and change orders. ProductFlo ECOs will draft Arena ECOs with matched line items.
Bridge the engineering BOM to SAP material masters and production BOMs. Cost and lead-time data flows back into impact analysis.
ProductFlo inside PTC Creo — cross-discipline dependencies on every part and assembly.
ProductFlo inside Autodesk Inventor — cross-discipline dependencies on every part and assembly.
In their words
"We cut our ECO cycle time by 74% in the first month. Our engineers stopped arguing about changes in each revision and started arguing about the robot again."
Figures self-reported by pilot teams. Read the methodology.
Trust & security
Built for the compliance reviews we know you'll run us through. Self-hosted where you need it. Audit-logged everywhere else.
ROI calculator
Our caluculator estimates recovered engineering capacity, annual value, and payback without assuming headcount reduction.
Estimated annual impact
Recovered capacity value from approximately 2,304 hours returned to engineering each year.
Directional estimate based entirely on the assumptions you enter. Recovered capacity is not the same as audited savings or guaranteed financial performance.
Design partner product
We're in controlled rollout through 2026. Fixed scope. Fixed fee. Named solutions engineer. You see the graph on your own BOM in week one.
One product. Three artefact sources. Joint success metrics. Fixed.
For 10–50 hardware engineers shipping real products. Full graph, all agents, all plugins.
Self-host, compliance, or volume. For defense, medical, aerospace.
FAQ
Ready when you are
30-minute scoping call. We map your artefact sources, pick one active product, and show you the graph — live — by the end of the week.