Custom features
Panels, automations, and checks for your workflow.
- Custom DRC rule packs
- Workflow-specific panels
- Process automations
- Fab-required checks
ProtoFlow Enterprise
ProtoFlow builtaround your team.
The complete platform, plus the requirements traceability, verification, and private tenancy that turn an EDA tool into your engineering system of record.
ProtoFlow
~2 min
from datasheet to a linked symbol and footprint
17 pages
in one project workspace over the live design
5 formats
KiCad, EAGLE, Altium, Allegro, Siemens
0
telemetry paths open to an enterprise account
Two things every enterprise team gets.
A custom ProtoFlow, built around your team.
Your library standards, your integrations, and a rollout run with you, the same platform, shaped entirely around how your team already works.
ProtoFlow
Custom AI part generation, suited to your needs.
Turn any datasheet into a verified, review-ready part in ~2 minutes, cross-checked by a deterministic CAD layer and exported straight into your library’s format.
ProtoFlow
One workspace over the live design.
Seventeen pages, from requirements to release deliverables, each derived from the actual schematic and board. A design change can never leave a report quietly out of date.
Project workspace
Orientation
Summary
Design
Hardware DesignBlock DiagramSchematicPCB
Parts & supply
LibraryBOMProcurement
Analysis
ReportsPower AnalysisHigh-Speed
Assurance
ValidationVerificationRequirementsReviews
Output
Engineering NotesResults
Derived, not entered
Component counts, rails, stress ratios, budgets, and SI results are computed from the live schematic and board, never typed into a document.
Provenance on every number
Every value says where it came from: datasheet, user entered, or AI proposed. AI facts render amber and stay out of reports until a human approves them.
Three global knobs
Operating mode, derating policy, and ambient range sit on every analytic page. Change one and every report recomputes.
An AI agent per page
Sixteen pages own a scoped agent with its own conversation and tool contract. Agents hand off to each other explicitly.
Requirements traceability that survives an audit.
Requirements tools and EDA tools do not talk to each other, so the gap gets filled by a spreadsheet and somebody's memory. Here, the compliance matrix is a view of the design itself.
Import
ReqIF and reqifz from IBM DOORS, DOORS Next, Polarion, or Jama, with identifiers, headings, and hierarchy preserved.
Bind
Attach the checkable requirements to rail windows, current limits, derating, temperature range, or ERC.
Verify
Verdicts recompute on every design edit: pass, fail, or honestly inconclusive when the evidence is not there.
Attest or waive
Manual attestations go suspect the moment the design or the requirement text moves underneath them.
Export
Compliance matrix as CSV or PDF, or write verification status back into the original ReqIF for re-import.
Honest by construction
Only bound requirements auto-evaluate. A fresh import has no bindings and says so, rather than reporting a false pass. Where the platform cannot compute an answer, the verdict is inconclusive, not green.
Start from the requirement set
Attach the ReqIF and the datasheets when you create a project. A five-step wizard turns them into approved facts, auto-verified requirements, and an architecture diagram before the AI builds anything.
Everything in ProtoFlow, on every seat.
No feature gating by plan. The enterprise agreement adds controls around the product, not access to it.
An AI copilot, datasheet-to-part generation, and automated placement, routing, and review, built into the editor.
AI Copilot (GPT / Claude / Gemini)Datasheet-to-part generationAI Component LabAuto-placement & auto-routingAI-assisted file importAI-powered design reviews
Plus the rest of the platform
Schematic capture
Multi-tab schematic editorSmart wiring & routingPower symbols & net managementDrag-and-drop placementAnnotations & regions
Manufacturing & output
Gerber X2 & Excellon drillsBOM with live pricingCPL / placement filesOne-click JLCPCB reviewKiCad / PNG / PDF export
Analysis & verification
Design Rule Check (DRC)Electrical Rule Check (ERC)Topology analysisGrid-alignment validationSPICE simulation & waveforms (beta)
Platform & desktop
AI-native desktop appKiCad interop & importAuto-save & session recoveryDocking UI & custom themesFull keyboard shortcuts
A ProtoFlow shaped around how you work.
Your library standards
Your conventions encoded, review-ready first time.
- Naming conventions
- Layer & stackup maps
- Courtyard / silkscreen rules
- Approved-parts enforcement
Connected to your stack
Integrated with the systems your team runs on.
- PLM / PDM sync
- ERP & part databases
- Internal component APIs
- CI / automation hooks
A rollout run with you
From install to adoption, with a named contact.
- Live engineer training
- Librarian onboarding
- Library migration
- Named account manager
Design reviews with evidence attached.
Gate templates for the reviews your programme already runs, with automated pre-checks that append live findings before anyone reads the checklist.
Preliminary design review
- Block diagram current
- Power architecture modelled
- External interfaces documented
- Key components selected
- Requirements reviewed against the architecture
Critical design review
- Schematic complete, no placeholders
- ERC clean
- Stress and derating within policy
- BOM fully sourced
- Power budget covered for every mode
Production readiness
- Board DRC clean
- Fabrication outputs inspected
- BOM priced, availability checked
- Second sources for critical parts
- Notes and deliverables complete
Automated pre-checks on every gate
Requirement coverageSignal integrityElectrical rule checkStress & deratingBOM sourcingRail modellingPower budgetBoard layout
Approving a gate freezes a snapshot of the design, its fingerprints, and the checklist as it stood. Compare mode then diffs any later design against that baseline structurally: BOM deltas, stress ratios, rails, and ERC. Templates are starting points, and every gate accepts a programme's own items.
The controls your organization requires.
Most of these are scoped in your enterprise agreement rather than toggled on a pricing page.
Custom seat licensing
Pooled org-wide AI quota with an admin console for seats, roles, and usage, reassign mid-term, no re-procurement.
SSO & SAML
SAML 2.0 with Okta, Entra ID, and Google Workspace. Enforce SSO per domain.
Dedicated AI capacity & SLAs
Reserved inference with uptime and support SLAs, priority on every model.
Private model & data isolation
Transient, never-retained processing, no training, zero-data-retention.
Security & compliance review
Security questionnaire, architecture docs, and a DPA for vendor review.
Onboarding & training
Hands-on sessions to encode your standards and train your team.
Dedicated account manager
A named contact, engineering escalation, and quarterly reviews.
Custom invoicing & procurement
PO purchasing, annual & multi-year invoicing, custom MSA, consolidated billing.
Scoped project access
Invite the team once. Give a contract manufacturer the BOM page and nothing else, with an activity trail of who saw what.
Bring your own key
Route AI calls through your own provider keys instead of pooled capacity.
From datasheet to verified part in ~2 minutes.
$20-30
per part outsourced, plus a business-day wait
30-60 min
per part built by hand
~2 min
per part in ProtoFlow, review-ready
ProtoFlow
Datasheet in, part out
A linked symbol + footprint in ~2 min, no pin-by-pin entry.
Verified, not freehand
A deterministic CAD layer cross-checks pins and dimensions.
Every EDA format
Native export to KiCad, EAGLE, Altium, Allegro, and Siemens.
Refinement built in
Revise with AI or hand-tune in the symbol/footprint editors.
Bulk library migration
One project regenerates thousands of legacy parts into your format and conventions, dimensionally verified.
A privacy boundary enforced twice.
Enterprise privacy is a property of the account and the build, not a setting somebody can leave switched off. Built for NPI work and security review.
Switched off in the client
Every outbound path is disabled before analytics SDKs even initialise:
External analyticsCrash uploadsAI feedback uploadsDesign telemetry & trainingComponent & query telemetryInstall attributionActivity syncCollaboration metricsCloud AI conversation sync
Denied again at the server
Server rules independently deny enterprise accounts the same telemetry paths, so the guarantee does not rest on the binary behaving.
No training, ever
Datasheets are processed transiently and never retained, and your uploads and designs never train any model.
Local-first desktop
Files stay on your machines. Project and collaboration storage are the only paths an enterprise account writes to.
Provable erasure
A historical purge completes only when a fresh inventory finds nothing left, and the audit records counts, never identifiers.
A build that is yours, on a channel that is yours.
A named application, ProtoFlow for your company, with a one-time co-branded welcome. One codebase and one signing identity, so every product improvement keeps flowing into your build.
Provisioned as part of your enterprise agreement.
Entitlement-gated installers
Download links are only issued to an account with an active seat for your organization, and they expire in minutes.
A private release channel
A dedicated release bucket with public access prevention enforced. Consumer storage is never used as a fallback.
Signed, verified artifacts
Promotion re-verifies hash, size, signing identity, notarization, and exact version before your update feed moves.
Your own update feed
The enterprise updater never falls back to the consumer channel.
It fits the AI stack you already run.
An MCP server exposes the editor to agents in Codex, Claude Code, or Langflow. Your own agents can create a project, edit a schematic, route, run checks, and export Gerbers, on the same billing, rate limit, and approval path as the built-in copilot.
Discovery
Entitlement is checked before editor tools even appear to the agent, and rechecked on every tool call.
Bridge start
The desktop starts its local bridge only for an eligible account, pinned to your exact organization.
Every request
Each request revalidates the seat. Revoking it stops the bridge on the next check.
Three independent authorization gates sit between an external tool and the editor, and enterprise accounts can route AI calls through their own provider keys.
Enterprise questions
Pricing is custom, scoped to your team size, AI quota, support level, and rollout, so you pay for what you need. Tell us about your team and we’ll send a quote.
Yes. We build custom features, encode your library standards, and integrate ProtoFlow into your PLM, ERP, and internal tools.
Datasheets are processed transiently and never retained, your designs are never used for training, and the desktop app is local-first. Zero-data-retention and isolation are written into the agreement.
Yes: SAML 2.0 with Okta, Microsoft Entra ID, and Google Workspace, with enforced SSO to disable password sign-in across your domain.
Yes. Import ReqIF and reqifz from IBM DOORS, DOORS Next, Polarion, and Jama with identifiers and hierarchy preserved, bind the electrical requirements to the live design, and write verification status back for re-import.
Yes. An MCP server exposes the editor to agents in Codex, Claude Code, or Langflow behind three independent authorization gates, on the same billing, rate limit, and approval path as the built-in copilot.
We run one-time bulk migrations that regenerate thousands of legacy parts into your target format and conventions, with dimensional verification.
Everything in ProtoFlow: the seventeen-page project workspace, the AI copilot, datasheet-to-part, the full schematic-to-PCB editor, real-time collaboration, and the complete manufacturing output set, plus the enterprise controls above.
Something specific to your rollout?
Talk to us
Scoped to your needs.
Tell us your team size and what you’re building. We’ll scope seats, AI quota, support, and rollout into a quote.
Annual contracts and volume quotas.
admin@protoflow.ai