NEWAgents now safely read schematics, firmware, parts, assemblies & BOMs

The orcherstration layer for hardware engineering.

The digital thread for deeptech hardware team where all engineering artifacts (mechanical, electrical, electronics, firmware, and manufacturing) are synced, typed, reviewed and versioned with AI-native capabilities.

Book a demo →See the product →
SOC 2 Type IISelf-host availableDeveloper friendly API/SDKAgent-native MCP
ECO VIEW

The problem

Your hardware team doesn’t move slowly because they are bad engineers.

They move slowly because your current tools and processes prevent them from working effectively.
Your hardware team is still running design reviews in sync meetings with PowerPoint and PDF presentations and reconciling file versions in shared drives. While software teams have AI agents that write, refactor, and review code; GitHub to sync code; and CI/CD pipelines to deploy code anywhere in a matter of seconds.

01 · NO GRAPH

The artefacts are disconnected.

A part on the BOM, a footprint on the PCB, a net in firmware, a cutout in the STEP file — the same object, stored in four tools that don't know each other exist.

02 · NO AGENTS

PLM was built for file vaults, not AI.

Windchill, Teamcenter, Arena can store artefacts. They can't read them, reason about them, or let an agent propose a safe change across all of them.

03 · NO VELOCITY

65% of eng time is lost to reconciliation.

That's the senior designer chasing the right rev, the EE on a Slack thread about a pinmap, the PM stitching BOMs from three spreadsheets. It's not engineering — it's filing.

Connected workflow

One orchestration layer. Every tool, artefact, and agent connected.

ProductFlo reads the source files your team already creates, turns them into shared product context, and gives humans and agents one governed way to understand and change the product.

01 · ENGINEERING SOFTWARE

In-host plugins

ProductFlo appears inside the tools engineers already use and keeps their source artefacts in the loop.

  • Altium
  • SolidWorks
  • GitHub
  • KiCad
  • Onshape

KiCad and Onshape integrations are in development.

02 · SOURCE UNDERSTANDING

Artefact parsers

Native engineering files become typed, queryable objects instead of opaque files in a vault.

  • MCAD
  • ECAD
  • Firmware
  • BOM
  • Docs
  • Source code

03 · DEVELOPER ACCESS

SDK + API + MCP

Connect internal systems, automate workflows, and build on the same governed product context.

  • API and SDK
  • Agent MCP
  • Webhooks
  • Scoped tokens
  • Custom connectors

PRODUCTFLO CORE

Typed product graph

Parts, assemblies, nets, pins, requirements, BOM lines, firmware symbols, and decisions become one versioned source of engineering context.

PARSEDTYPEDLINKEDVERSIONED

04 · REASON

Built-in agents

ProductFlo agents read the graph, run scoped checks, and propose changes for human review.

  • Impact analyzer
  • Pin-map guard
  • BOM reconcile
  • Supply watch
  • Compliance sentinel

05 · EXTEND

MCP gateway

Give external agents governed graph context and scoped tools without handing them unrestricted source access.

MCP SERVER

Context + tools

  • External agents
  • Engineering copilots
  • Custom automation

06 · GOVERNED OUTPUT

Decisions return to the workflow.

SYNC BACK THROUGH PLUGIN OR API

  • Impact analysis

    Cross-discipline blast radius before a change is approved.

  • Engineering Design review

    A proposed change with evidence, rationale, and owners.

  • Governed Change Orders

    Human approval, routing, and a signed change record.

  • Audit evidence

    A versioned trail of what changed, why, and by whom.

Product tour

Five disciplines. One graph. Every artefact.

Click through the actual product. Every screen below is live — it's the same code we ship to customers.

productflo.io / robot-alpha / graphLIVE
GRAPH VIEW

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 →

How it works

A graph, a set of agents, and a review gate.

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.

01
GRAPH

One typed model

Parts · nets · signals · tolerances · suppliers · revs — one queryable graph across MECH / ELE / FW / MFG.

02
AGENTS

Safe proposers

Scoped agents watch the graph, draft ECOs, and write diffs — never commits. They propose, humans approve.

03
REVIEW

ECOs as diffs

Every change is a reviewable, reversible diff with the right reviewers auto-selected by discipline & ownership.

04
SYNC

Bidirectional, live

Merged ECOs flow back into Altium, SolidWorks, Git, and your BOM system. No export. No drift.

agent.session() · productflo/v1
// 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

Same API. Human or agent.

The surface a designer sees in the dashboard is exactly the surface an agent hits in code — typed, scoped, diffable, audit-logged.

  • →Typed tool-calls over JSON-LD — not files.
  • →Every mutation returns a reviewable diff.
  • →Role-scoped credentials per agent, per product, per rev.
  • →Webhooks on every state change.
  • →MCP-native — wire any model in, out of the box.

Agents

Ships with the agents every hardware team needs.

All agents are scoped, auditable, dry-run-capable, and propose diffs; never commits. Bring your own models, or use ours.

SUPPLY-WATCH

Supply & lifecycle monitor

Watches supplier feeds for EOL, lead-time, and MOQ changes. Drafts alternates keyed to your approved vendor list.

TRIGGER · supplier feed · daily
THERMAL-CHECK

Thermal envelope linter

Cross-checks FW duty cycles against heat-sink geometry and rail current budgets. Flags envelope violations at diff time.

TRIGGER · fw-commit · eco-review
PINMAP-GUARD

Pin-map conflict detector

Validates every pin assignment across schematic, firmware, and mechanical connector pinouts. Single source of pin truth.

TRIGGER · schematic-save · pr-open
BOM-RECONCILE

BOM & AVL reconciler

Keeps the design BOM, the mfg BOM, and the PLM BOM in sync. Flags drift, proposes AVL additions, routes to procurement.

TRIGGER · bom-save · nightly
CERT-SENTINEL

Compliance & cert watcher

Knows which artefact changes re-open FCC / UL / 510(k) / IEC cert gates. Flags the cost before the merge, not after.

TRIGGER · eco-review
IMPACT-ANALYZER

Cross-discipline impact

Answers "what breaks if…" in seconds. Powers the impact view and gives every ECO its blast-radius estimate.

TRIGGER · query · eco-draft
REV-NARRATOR

Rev summary author

Turns every rev into a human-readable changelog. Groups ECOs by theme, writes release notes, drafts MRB memos.

TRIGGER · rev-cut
CUSTOM

Bring your own agent

Write a custom agent in 20 lines. Scoped tokens, typed tool-calls, dry-run mode, audit log — all out of the box.

TRIGGER · any webhook · any model
COMING SOON

Design-for-X linter

DfM · DfA · DfT · DfR — drafted by the agents that own each concern, reviewed by you.

2026 · design partners first

In-host plugins

Lives where your engineers already work.

No migration. No new tool to learn. No rip-and-replace. ProductFlo shows up as a side panel in Altium, a task pane in SolidWorks, and a bot on GitHub — serving the same live graph.

ALTIUMAVAILABLE

Schematic side panel

Shows ownership, cross-discipline impact, and open ECOs on whatever the engineer clicks. Propose a part swap without leaving the editor.

v1.4 · 2.1k installs
SOLIDWORKSAVAILABLE

Assembly task pane

See electrical and firmware dependencies on every part in your assembly. Clash-check against the live PCB outline. Commit ECOs in-place.

v1.2 · 1.4k installs
GITHUBAVAILABLE

PR bot & merge gate

Every firmware PR that touches a pin is automatically cross-checked against the schematic. Merge is gated until the hardware graph agrees.

App · 38 repos
KICADIN DEV

Schematic & layout sync

Bi-directional sync between KiCad projects and the ProductFlo graph. Net changes, footprint swaps, and BOM updates flow both ways.

Coming 2026
ONSHAPEIN DEV

Document panel

Surface cross-discipline dependencies inside Onshape documents. See which electrical and firmware artefacts depend on every part and assembly.

Coming 2026
CADENCEIN DEV

OrCAD & Allegro bridge

Import schematics and board layouts from Cadence tools into the unified graph. Pin-map validation and net-level impact analysis included.

Coming 2026
FUSION 360IN DEV

Design workspace add-in

Link Fusion 360 components to the product graph. Mechanical changes automatically cascade to affected electrical and firmware artefacts.

Coming 2026
ZEPHYR RTOSIN DEV

Devicetree & Kconfig sync

Map Zephyr devicetree bindings to the hardware graph. Pin reassignments and peripheral changes are validated against the schematic before merge.

Coming 2026
WINDCHILLIN DEV

PLM bi-directional sync

Keep Windchill part structures and BOMs in sync with the live graph. ECOs authored in ProductFlo propagate to Windchill change notices.

Coming 2026
ARENAIN DEV

BOM & change order bridge

Sync Arena BOMs, approved manufacturer lists, and change orders. ProductFlo ECOs can draft Arena ECOs with matched line items.

Coming 2026
SAP / ERPIN DEV

Material master sync

Bridge the engineering BOM to SAP material masters and production BOMs. Cost and lead-time data flows back into impact analysis.

Coming 2026
API / SDK / MCPAVAILABLE

Any outside connection

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.

Docs available

Scenarios

Three failure modes. Three fixes. One afternoon.

These aren't hypotheticals. They're the top three reasons products slip, pulled from design-partner data.

01 · AGENT-TRIGGEREDA connector goes EOL mid-product.Supply-watch · Mira (proc) · Devon (EE)
BEFORE · WITHOUT PRODUCTFLO

4 days. Supplier email lands. Procurement digs through 3 BOMs. EE manually checks schematic for every usage. Someone forgets to tell firmware. Board spins.

WITH PRODUCTFLO

3 minutes to draft. Supply-watch agent sees the EOL feed, queries the graph, drafts a swap ECO with an alternate that fits the footprint and the stocking strategy.

REVIEW & MERGE

Auto-routed to Devon (EE) and Mira (proc). They approve the diff in the same morning. PCB, MECH, FW, BOM, and MFG all update in-place.

OUTCOME4 days → 1 morning · 0 spinsread full scenario →
02 · ENGINEER-TRIGGEREDA thermal envelope breaks under real duty cycle.Kai (ME) · thermal-check · Devon (EE)
BEFORE · WITHOUT PRODUCTFLO

2 weeks of back-and-forth. Kai sees temps on bench. Files a bug. Devon needs the same STEP + schematic + firmware logs. Three meetings to align.

WITH PRODUCTFLO

Single query resolves it. Kai asks "what dissipates into the chassis wall near the IMU?" Graph returns the heatsink, the driver IC, the 3.3V rail, and last week's FW change that raised the PWM duty.

REVIEW & MERGE

Thermal-check agent co-authors the fix. Kai proposes a vent cutout; Devon lowers the rail current limit. Both diffs reviewed together in one ECO.

OUTCOME2 weeks → 2 days · cross-discipline alignment in one threadread full scenario →
03 · REVIEW-GATE-TRIGGEREDTwo engineers edit the same subsystem on the same afternoon.Kavya (FW) · Devon (EE) · conflict-detector
BEFORE · WITHOUT PRODUCTFLO

Found at MRB, 6 weeks later. Kavya reassigns a GPIO. Devon reassigns the same pin to a new sensor. Merge order wins. Production build DOA.

WITH PRODUCTFLO

Caught at review. Both ECOs touch pin PA4. Conflict-detector surfaces the overlap in the review gate before either can merge.

REVIEW & MERGE

Three-way resolve in the UI. The owning engineer arbitrates, picks the winning assignment, the loser becomes a new task on the backlog. Both ECOs merge together.

OUTCOME6 weeks saved · 0 DOA boardsread full scenario →

In their words

Design-partner teams are already shipping faster.

"We cut our ECO cycle time by 74% in the first month. My engineers stopped arguing about file versions and started arguing about the robot again."

Thibault Corens
CTO · Presso
−74%
Median ECO cycle time, pilot teams
300K
Artefacts under management today
<1hr
Time to first value, median
9
Design partners · robotics, medical, consumer, EV

Founders

Built by engineers who have shipped real hardware.

FOUNDED
2024 · Atlanta
PRIOR LIVES
Presso ·
HAX · ANTLER
BACKED BY
[Atlanta Ventures]
[Notable hardware founders]

We watched the same $80M product slip by six months for the seventh time in fifteen years. Different company, different vertical, same root cause: a mechanical rev, an electrical rev, and a firmware rev that nobody stitched together until the line stopped.

PLM didn't fix it. Slack didn't fix it. Another spreadsheet didn't fix it. The problem isn't that hardware teams need better tools — it's that they need one graph underneath the tools they already have, and a set of agents that can finally do the reconciliation work a human shouldn't.

That's ProductFlo. We're building it with nine design partners across robotics, medical, consumer and EV, and we're opening the cohort to ten more teams through 2026.

Trust & security

Your IP stays yours. Every change leaves a trail.

Built for the compliance reviews we know you'll run us through. Self-hosted where you need it. Audit-logged everywhere else.

Compliance posture

SOC 2 Type I●audited · 2025-Q4
SOC 2 Type II●in progress · 2026-Q2
ISO 27001●in progress · 2026-Q2
GDPR · CCPA · DPF●compliant
HIPAA BAA●available · self-host
ITAR / EARself-host only
SOC 2 audit letteron request →

Deploy where it fits.

  • →Cloud. Single-tenant. US, EU, or APAC region. Customer-managed KMS.
  • →Self-hosted. Helm chart. Air-gapped mode. Your Kubernetes, your network.
  • →Hybrid. Graph on your infra. Agents reach out to your approved models only.
  • →Every mutation audit-logged. Who, what, when, which model, which prompt. Exportable.
  • →SSO, SCIM, RBAC, scoped tokens. Per-agent credentials with per-product blast radius.

ROI calculator

Use your own team economics to anticipate your ROI

Our caluculator estimates recovered engineering capacity, annual value, and payback without assuming headcount reduction.

Teams size

Edit any input to update the model.

People doing product engineering work

engineers

Salary, benefits, taxes, and overhead per engineer

$/ engineer

Finding revisions, syncing disciplines, and rework

hours / week

Estimated annual impact

$180,000

Recovered capacity value from approximately 2,304 hours returned to engineering each year.

Gross return
3.8×
Net ROI
275%
Simple payback
3.2 months
Current capacity cost$180,000
ProductFlo investment−$48,000
Estimated net annual value$132,000
Validate this model with your workflow →

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

Start with a 30-day pilot on one active 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.

Pilot

$8k/ 30 days

One product. Three artefact sources. Joint success metrics. Fixed.

  • →Scoped to one active product
  • →Up to 3 source-tool integrations
  • →Weekly review with your team
  • →Zero migration, zero lock-in
  • →Credit applies to annual
Book a scoping call →
DESIGN PARTNER

Team

From $48k/ year

For 10–50 hardware engineers shipping real products. Full graph, all agents, all plugins.

  • →Unlimited products & artefacts
  • →All agents + bring-your-own-agent
  • →All in-host plugins (Altium, SW, Git)
  • →SSO, RBAC, SCIM, audit logs
  • →Pricing locked through 2027
  • →Slack channel with the founders
Join the cohort →

Enterprise

Custom

Self-host, compliance, or volume. For defense, medical, aerospace.

  • →Self-hosted on your infra
  • →SOC 2 Type II + custom DPAs
  • →HIPAA BAA · ITAR (self-host)
  • →Dedicated solutions architect
  • →99.9% SLA
Talk to sales →

FAQ

The questions every VP Eng asks us on the first call.

Do we need to rip out our PLM?+
No. ProductFlo sits on top of your existing tools — Altium, SolidWorks, Git, your BOM system, your PLM. We index in place and build the graph from the artefacts you already have. Turn us off any day with zero lock-in.
How is this different from Windchill, Teamcenter, or Arena?+
Those are file vaults. They store artefacts. ProductFlo is a graph — it understands what's inside the files and how they relate. And it's built for agents, not just humans. We're a layer above PLM, not a replacement for it (yet).
What about IP and security?+
SOC 2 Type II today. ISO 27001 mid-2026. HIPAA BAA available. Self-host for ITAR/EAR. Your artefacts never leave your environment in self-host mode. Every agent call is audit-logged with the prompt, the model, and the diff produced.
How do agents not break things?+
Agents only propose — they never commit. Every output is a reviewable diff, scoped by discipline, routed to the right owners. Dry-run mode is on by default. Scoped tokens limit blast radius to one product or one rev.
Which models do you use?+
Frontier models today (Claude, GPT-5, Gemini) for the agents that benefit from long context. Smaller, local models for the ones that run on every commit. Bring-your-own-model is supported end-to-end — we're MCP-native.
How fast is a pilot?+
First value inside an hour. Full graph on one product in a week. Agents running in production by week three. We bring a named solutions engineer to every pilot — you don't configure anything alone.
What verticals are you optimized for?+
Robotics, medical devices, consumer electronics, aerospace & defense, automotive/EV. Anywhere mechanical + electrical + firmware + manufacturing all ship as one product.
What do you need from us to start?+
Read-only access to one active product's artefacts: your CAD vault, your PCB repo, your BOM sheet, your firmware repo. We build the graph, then you decide what to turn on.

Ready when you are

See ProductFlo run on your own product.

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.

Book a demo →
No migrationSOC 2 Type IILive in < 1 hourSelf-host available