Waferira is pre-launch. We have no customers to name and will not borrow logos. This page says who the product is for, what a design partner commits to, and who we deliberately do not target.
Logic and foundry, memory (DRAM, NAND, HBM), analog and mixed-signal, and specialty and compound-semiconductor IDMs and foundries running litho, etch, deposition, CMP, implant, diffusion, clean and metrology and inspection modules.
The criteria we check, in order.
Two to four IDMs or foundries that operate high-value litho, etch, deposition, CMP or inspection modules and agree to baseline yield, excursion, cycle-time and engineer-load metrics before any recommendation is enabled.
We have no customer quotes to show yet and will not invent any. These are the three roles in a fab we build for, and the problems they bring to the first meeting.
What this person is dealing with today
What this person is dealing with today
What this person is dealing with today
Logic and foundry, memory, analog and mixed-signal, specialty and compound semiconductor, and new fabs ramping a node. Most fabs pick one module and one wedge, prove the number, then expand.
Sub-3 nm, gate-all-around and backside-power nodes where overlay and CD budgets decide yield. Lithera and Vmetra on the litho and etch modules first.
High-aspect-ratio etch and deposition uniformity and CMP planarisation on long flows. Vmetra and Scanira where excursions are most expensive.
Many products, many recipes, few engineers per tool. Virtual metrology and defect disposition to cover more wafers with the same team.
SiC, GaN and photonics fabs with their own defect and uniformity physics. Scanira and Vmetra models trained per process family.
Reshored and greenfield capacity ramping under schedule pressure. Fabtwin de-risks the ramp before lots run.
Every Waferira run is an ordered, inspectable sequence. This is run_7b2e9c on Module M2 · 300 mm · metal-1 · lot L-48213. Scenario completes in 10 steps with one approval gate. Overlay and CD predicted inside spec, one reticle-repeater signature caught and held for review, dispatch re-optimised, lot released with full genealogy.
Fab Orchestrator · Pulled lot L-48213 from fab MES: 25 wafers, 300 mm, metal-1 layer, route, reticle, overlay and CD spec and the standing cycle-time target. Locked the target envelope for the run.
Fab Twin · Simulated 64 candidate correctable, recipe and dispatch sets on the as-run fab twin and ranked them on predicted overlay residual, CD uniformity, excursion risk and cycle time.
Litho-and-Overlay · Per-field overlay correctables and a focus-dose trim written to scanner SCN-07 over SECS/GEM after the previous lot's residual trended toward the control limit. Predicted overlay residual back inside spec.
Etch-and-Depo · Chamber B on etcher ETCH-12 showed an edge-fast uniformity drift in FDC. Pressure and RF trims written within the qualified recipe window; predicted CD uniformity recovered.
CMP-and-Implant · Downforce and platen-speed trim on CMP-03 against the virtual removal-rate estimate to hold post-CMP thickness and dishing inside the window.
Defect-and-Inspect · Inline optical, e-beam review and SEM imagery fused at the tool edge. 1,412 events classified, most dispositioned nuisance; one reticle-repeater signature on three dies flagged for review.
Metrology-and-Virtual · Virtual metrology scored every wafer at post-etch and post-CMP from tool-sensor and FDC signatures. Two wafers routed to physical metrology on predicted variance; the rest sampled at plan.
Fab Orchestrator · The reticle-repeater signature called for a reticle inspection hold and a recipe move outside the qualified window. Held for the module process engineer and approved at 03:14:27.
Yield-and-Dispatch · Dispatch re-optimised across 1,840 lots in WIP under reticle, chamber and qualification constraints. The lot routed to the qualified chamber with the shortest predicted queue; AMHS move issued to the stocker.
Quality-and-Conformance · Lot L-48213 moved on: genealogy written (recipe moves, correctables, FDC signatures, VM scores, defect map, approvals) and checked against the layer spec.
A fab does not go from manual APC to unattended control in one step. Waferira makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then graduated autonomy for low-risk APC, defect and metrology loops.
| Level | What the agent does | What the human does | Where it sits in a pilot |
|---|---|---|---|
| L1 · Advisory | Recommends recipe moves, dispositions and dispatch, with citations | Enters every change manually | Shadow mode, first on the design-partner cell |
| L2 · Supervised | Proposes a recipe write or hold; it executes on approval | Approves each move in the review console | Assist mode, where accuracy and ROI are proven |
| L3 · Bounded | Writes inside the qualified recipe window, tool-state checks and OCAP linkage | Approves holds, out-of-window moves and lot release | Graduated autonomy for low-risk APC, defect and metrology loops |
| L4 · Qualified loops | Runs a qualified loop without prompting, inside its envelope | Sets the envelope; reviews the shift record | Planned; reserved for loops the fab has qualified |
The questions fab directors and process engineers ask in the first meeting.
Yes, over SECS/GEM, but only inside the qualified recipe window for that tool, with per-parameter limits and tool-state checks, and only at the autonomy level your fab has set. Level 1 is advisory: Waferira recommends and an engineer enters everything. Design partners start there, in shadow mode.
The tool stays on its own controller and its last qualified recipe. Waferira is a supervisory layer on top of the APC, inspection, metrology and MES systems you already run, never a replacement for them, so an outage leaves the module running the way it runs today.
No. Inference and feature storage stay at the fab edge, recipes, device designs, defect libraries and process memory are isolated per tenant, and an on-prem control plane is available for IP-sensitive fabs. Any cross-fab learning is planned, contract-gated and privacy-preserving, and none of it moves recipes or designs.
Advisory recommendations start from the existing APC, metrology and ADC data on the wedge module. Defect classification, virtual metrology and excursion prediction improve as labelled events and lot outcomes accumulate per process family. Rare excursions are augmented synthetically only after validation against real distributions.
You are, the same as with any APC strategy, which is why every write is policy-checked, bounded to the qualified window, logged and reversible, and why holds, out-of-window moves and lot release wait for a named approver with the OCAP linked.
A paid pilot on one process module or tool fleet, scoped to one wedge workflow with a baseline agreed in writing. Shadow mode first, observing and measuring the baseline. Then assist mode, where the agent recommends and your engineer approves and accuracy and ROI are measured. Then bounded autonomy for low-risk APC, defect or metrology loops if the fab is satisfied.
Tell us the module, the metric and the baseline you would sign. We will tell you honestly whether the wedge fits.
↑↓ navigate↵ openesc close
