Deliverables
What you actually receive
Real files, in formats your fabricator and your toolchain already accept. Nothing is trapped inside the platform.
The five artefacts
Five things leave the platform
Each one is complete on its own. If you stop after any stage, you keep what that stage produced.
A specification you can argue with
Functional behaviour, electrical and mechanical envelopes, interfaces, environment, and the things the product must never do. Written as requirements, not as prose, so a disagreement is about a line rather than a mood.
Schematics and board layout
Full schematics and multi-layer layout, with the reasoning behind each choice kept beside it. In eight months you can still find out why a part was chosen.
A bill of materials, graded
Every line carries a grade, so you know at a glance which parts are settled and which need a human decision before you commit money.
Firmware and board support
Board support, peripheral configuration, drivers and application firmware produced against the same model as the schematic. The firmware and the hardware cannot disagree about a pin.
A manufacturing package
Fabrication outputs, assembly data, test information, sourcing references and the documentation that has to travel with a product. One handover, not a thread of emails.
The graded BOM
Three grades, and the third is the useful one
A bill of materials that says nothing about confidence is a list of hopes. Every line here carries a grade.
Verified
The part is settled. Specification, footprint and availability all line up, and nothing about it needs a decision from you.
Flagged
The part works, but something about it deserves your attention — a constraint, a tolerance, a sourcing question. Flagged is not a warning that something is wrong. It is a request for a decision only you can make.
Excluded
The part was considered and rejected, and the reason is recorded. You can see what was ruled out and why, which is usually more useful than the list of what was kept.
Most tools hand you a list and let you find out at the fabricator which lines were guesses. Grading every line is the difference between a document you have to re-check and one you can act on.
Formats
Everything opens without us
The test we hold ourselves to: if you walked away tomorrow, could you carry on? The answer has to be yes, or the format is wrong.
Schematic and layout sources, fabrication outputs, drill data, assembly drawings and pick-and-place data — in the standard interchange formats fabricators and assemblers have accepted for decades.
3D models in neutral interchange formats, so the enclosure team, the mechanical engineer and the manufacturer are all looking at the same geometry.
Source, build configuration and board support, laid out the way an embedded engineer expects to find them. You can open the project and read it.
Specification, decision record and manufacturing documentation as ordinary documents. Nothing that needs our software to open.
Ownership
Your design is yours
Ownership is set out in the agreement you sign before onboarding, and you read it before you commit to anything. We will not surprise you with it later, and we will not describe it more favourably here than it is written there.
If a term in that agreement does not match a sentence on this website, the agreement is right and this page is a defect. Tell us and we will fix the page.
Read it before you commit
The agreement goes to you to read before onboarding begins. There is no stage at which you are asked to accept something you have not seen.
Questions
Five straight answers
Do I need your software to open any of this?
No. Everything leaves in standard formats. If you stopped working with us tomorrow you would still be able to open, edit and manufacture what you have.
What does a flagged line in the bill of materials actually mean?
That the part works, and that something about it deserves a decision from you before money is committed — a constraint, a tolerance, a sourcing question. It is a prompt, not a fault.
Can I take only the specification, or only the schematic?
Yes. Each stage produces complete outputs. If you only want the specification, you take the specification and go.
Will you sign an NDA before I send you anything?
Yes. Say so in the access request and it happens before you send us a file.
What happens if an output is wrong?
Tell us, and send the case. Every output is yours to review and we expect you to review it — the platform assists your engineering judgement, it does not replace it.
See it on something you are building
The onboarding session runs your own project through the stages that are ready for it, and you keep what comes out.