Engineering teams with complex PCB constraints, delivery-critical timelines and a need for traceable, reviewable design decisions.
Program
Private Beta Engagement for Small-Batch, High-Consequence Programs.
The private beta pairs the @I Design pipeline with architect-led review for a small number of engineering programs at a time.
Admission favours teams that can state requirements, constraints and acceptance criteria at the start, which are the conditions under which the pipeline does its best work.
- Selective intake.
- Architect-led operating model.
- Deployment pathway agreed at intake.
Program Fit
Who This Program Is Built For
The strongest fit is an organisation where hardware design decisions carry immediate cost, schedule, reliability or compliance consequences.
We prioritise teams that can define objectives, risk boundaries and acceptance criteria at intake, because that is what lets the rule engine and the optimiser do useful work.
- Complex multi-constraint board programs.
- Reliability, safety or compliance requirements that call for traceable decisions.
- Teams that want faster iteration without giving up review control.
Collaboration Model
Execution Workflow
Programs move through four stages, with a review at the end of each.
- Stage 1, Intake: requirements, constraints, acceptance criteria and review cadence agreed.
- Stage 2, Synthesis: component selection and schematic generation, reviewed with your engineers.
- Stage 3, Layout and verification: placement, routing and rule checks converge on a DRC-clean design.
- Stage 4, Handoff: release package delivered, followed by a program retrospective.
Deliverables
What You Receive
A release package your engineers can review, modify and send to fabrication from their own toolchain.
- Schematic and netlist in KiCad-compatible formats.
- Placed-and-routed PCB layout file.
- Structured bill of materials (BOM).
- DRC report with open issues ranked by severity.
- Industry-standard Gerber fabrication files.
- Decision log linking requirements to design choices.
Exact formats and toolchain integration are confirmed at intake.
Delivery Options
Deployment and Security Options
The deployment pathway is chosen to fit your security and governance requirements and is confirmed at intake.
- Cloud-hosted design workspace.
- Integration with enterprise engineering environments.
- Managed turnkey design delivery.
Availability of each pathway depends on program stage and technical fit.
FAQ
Program Questions
Answers to the questions engineering and procurement teams ask most often.
The program is not intended for open-ended experimentation, undefined project scopes, or teams that cannot provide clear requirements, constraints and acceptance criteria.
A release package containing the schematic and netlist, PCB layout, BOM, DRC report and Gerber files, produced through four reviewed stages: intake, synthesis, layout and verification, and handoff.
No. The AI proposes, a deterministic rule engine enforces safety, manufacturing and design rules, and your engineers approve the result. Uncertain requirements and unresolved rule conflicts are flagged for human review.
They come from an internal benchmark of 500 design scenarios, each completed with conventional EDA workflows and with the @I Design pipeline. They are benchmark results, not guarantees; the validation page sets out the method and limits.
How submitted engineering data may be used, including for model improvement, is agreed in writing for each engagement before any project data is shared.
Depending on security and governance requirements, programs may use a cloud-hosted workspace, integration with enterprise engineering environments, or managed turnkey delivery. Availability depends on program stage and technical fit.
The system is the subject of New Zealand patent application 820555, which is pending.
Program Summary
Selective by Design
The program is kept deliberately small so every engagement stays reviewable, explainable and architect-led.