The AI-native system for product engineering
New customer requirement. New variant. Done.
SourcePilot computes the architecture, physics, specifications and eBOM. Your engineers review and approve.
It computes
Other AI reads your documents. SourcePilot computes the engineering.
Physics, sizing and specifications are calculated on one model, not summarised from files. What comes back is an engineered design, not a better-organised one.
Minutes
Requirements to a first system model and eBOM, run autonomously.
Days
With your engineers' detailed review and sign-off.
Every part
Traced to a requirement and checked against the physics.
Agents on branches
Many architectures explored in parallel. The best ones ranked.
Agents each work on their own branch of the whole design, testing a different architecture against the physics and the requirements. You get a ranked proposal with the trade-offs. Your engineers choose and merge.
Variants without starting over
Branches from the validated parent; only the deltas are re-engineered.
Change without the rework
The full consequence set, computed before the change board meets.
Optimise with the trade-offs visible
Set −10% cost or max 800 g; get ranked options and what each costs you.
The eBOM
The eBOM is the hard part. Physics is how we get there.
The physics derives the exact attributes, the attributes become part specifications, and the specifications select the right components from your libraries and approved suppliers. Every line traced to the requirement behind it.
- Physics
- Exact attributes
- Part specification
- The right component
The specification layer
The first layer of automated engineering.
SourcePilot reads from and writes back to the tools you run today. AI-generated CAD, simulation and automated manufacturing all build on its specification, and their results come back to be checked against it.
Your tools · read and write back
- RequirementsDOORS, Polarion or requirement documents
- PLM and ERPWindchill, Teamcenter, 3DEXPERIENCE
- Component librariesParts, datasheets and existing BOMs
- Accredited supplier listsApproved suppliers and parts
SourcePilot
Specification layer · version-controlled
- Requirements and acceptance criteria
- System architecture and interfaces
- Sized parameters, checked against physics
- Fully traced eBOM
SysML v2 · JSON · XML · RDF
Built on the specification
- Detailed designCAD, including AI-generated CAD
- Simulation and verificationCAE, AI simulation and test
- SourcingRFQs on approved parts
- ManufacturingProcess planning, automated production
An engineering engine
An engine you adapt. Not an app you adapt to.
The whole stack is generated from one schema. Declare what your products and processes need, and the database, APIs, interface, access rules and agent tools follow. Try it.
Declare a data model
// illustrative: a customer-specific node type node TypeTest { standard Standard // IEC/EN 60947-4-1 parameter string // AC-3 endurance report Document valid_until date } TypeTest ─covers→ Component TypeTest ─evidences→ Requirement
Regenerated from the declaration
- Databasetables, relationships, indexes—
- REST APItyped endpoints for every node and relationship—
- Type-safe frontend clientviews and forms stay in step with the model—
- Security filteringrole-based access applied to the new data—
- Realtime syncacross users, branches and merges—
- Agent toolswell-typed, permission-scoped, traceable—
A new domain is mostly a schema edit.
Applying SourcePilot to your products and processes means declaring node types, relationships and attributes. Configuration, not a rebuild.
Your own agents from typed building blocks.
A new agent inherits a tool surface generated from the schema, so an agent for your process is assembled from existing parts.
Already running this way.
Engineering method (RFLP), product data (PDM) and a modelling standard (SysML v2) run today as modules on one shared base.
Apply it to your products.
Bring one product family. We build its model on your data and show you the engineering work coming back.
FAQs
Didn’t find an answer to your question?We’re here to help. Send it to us at:
hello@sourcepilot.aiWhat products is it for?
Complex, variant-rich industrial products engineered to requirements: power tools, pumps and valves, machine tools, robots, automation stations, HVAC and energy equipment, rail subsystems.
How reliable are the results?
Requirements are checked against INCOSE rules, the design against system-level physics, and a requirement only passes when a real part’s specification satisfies it. Every proposal is staged for your review before it merges.
Does it replace our PLM or requirements tools?
No. It sits upstream and exports into them: SysML v2, JSON, XML or RDF to Windchill, Teamcenter, 3DEXPERIENCE, DOORS or Polarion. Two-way connectors are built with you during rollout.
Can we set standards, certification and supplier rules?
Yes. They are entered at the requirement stage and applied when parts are sized and selected, so the design is built to them rather than checked against them afterwards.
Can SourcePilot be used for defence and other controlled products?
Yes, for defence and security customers under an enterprise agreement, where end use, export controls and data sovereignty are reviewed and agreed per programme. Self-service and web access may not be used for weapons or other export-controlled end uses: our terms prohibit it and the product enforces it.