Physical AI · Wafer-fab autonomy

The fab runs itself. You decide how far.

Waferira is an agent operating system for semiconductor front-end fabs. Specialist agents control litho and overlay, etch and deposition, CMP and implant, classify defects from inline, e-beam and SEM inspection, measure every wafer virtually, dispatch the WIP and move the carriers, rehearsed on an as-run fab twin and bounded by a policy engine the fab controls. IP never leaves the fab.

SUCCEEDED run_7b2e9c scenario complete10 steps · 1 approval gateModule M2 · lot L-48213

run_7b2e9c · agent graph · module M2 · scenario 10 nodes · 1 approval gate
01 · orchestrator ingest.lot ✓ SUCCEEDED 02 · fabtwin twin.simulate ✓ SUCCEEDED 03 · litho_overlay litho.correctables ✓ SUCCEEDED 04 · etch_depo etch.uniformity ✓ SUCCEEDED 05 · cmp_implant cmp.removal ✓ SUCCEEDED 06 · defect_inspect inspect.classify ✓ SUCCEEDED 07 · metrology_vm vm.score ✓ SUCCEEDED 08 · orchestrator approve.human ◆ APPROVAL 09 · yield_dispatch dispatch.route ✓ SUCCEEDED 10 · quality_conf lot.release ✓ SUCCEEDED

Illustrative scenario: Module M2 · 300 mm · metal-1 · lot L-48213, one lot through metal-1, one approval gate

Design partners wanted · 2 to 4 IDMs or foundries · modules we are looking for

Litho cells Etch and deposition modules CMP Inline inspection Metrology and FDC WIP dispatch and AMHS

Pre-launch. No customers, pilots or logos are claimed. The first cohort gets a paid, IP-isolated pilot on one module against a baseline agreed in writing.

Run timeline · scenario

One scenario run, step by step

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.

run_7b2e9c Module M2 · 300 mm · metal-1 · lot L-48213 illustrative scenario SUCCEEDED
  1. 01 ingest.lot SUCCEEDED 0.7 s

    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.

  2. 02 twin.simulate SUCCEEDED 38 s

    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.

  3. 03 litho.correctables SUCCEEDED 1 m 20 s

    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.

  4. 04 etch.uniformity SUCCEEDED 58 s

    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.

  5. 05 cmp.removal SUCCEEDED 46 s

    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.

  6. 06 inspect.classify SUCCEEDED continuous

    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.

  7. 07 vm.score SUCCEEDED 2.1 s

    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.

  8. 08 approve.human APPROVAL 1 m 04 s

    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.

  9. 09 dispatch.route SUCCEEDED 4.3 s

    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.

  10. 10 lot.release SUCCEEDED 1 m 05 s

    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.

Tool calls · scenario

The agent shows its work

Every tool invocation, argument and result is written to an append-only, IP-isolated, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the fab.

tool-call stream · run_7b2e9c
  1. 03:02:10mes.read_lot({ lot: "L-48213", layer: "M1", module: "M2" })
  2. 03:02:11ok 25 wafers · reticle R-M1-114 · overlay and CD spec locked
  3. 03:02:11twin.simulate({ candidates: 64, horizon: "lot" })
  4. 03:02:49ok best set #41 · overlay residual 2.6 nm · excursion risk 0.05
  5. 03:02:50policy.evaluate({ set: 41, autonomy: "L3" })
  6. 03:02:50ok 7 recipe writes inside qualified window · 1 move requires human approval
  7. 03:02:51secs.write_recipe({ tool: "SCN-07", correctables: "per_field", dose: "-0.3%" })
  8. 03:04:11ok predicted overlay residual 3.1 → 2.6 nm · CD on target
  9. 03:04:12secs.write_recipe({ tool: "ETCH-12", chamber: "B", pressure: "+1.5%", rf: "-0.8%" })
  10. 03:05:10ok edge-fast drift cleared · predicted uniformity inside window
  11. 03:05:11secs.write_recipe({ tool: "CMP-03", downforce: "-2%", platen: "+1%" })
  12. 03:05:57ok virtual removal rate on target · dishing inside window
  13. 03:05:58vision.stream({ tools: ["INS-02", "EB-01", "SEM-04"] })
  14. 03:09:40repeater: 3 dies · same field position · reticle R-M1-114 · killer class
  15. 03:09:41vm.predict({ lot: "L-48213", steps: ["post_etch", "post_cmp"] })
  16. 03:09:43ok 25 wafers scored · 2 routed to physical metrology
  17. 03:09:44approval.request({ action: "reticle_hold", recipe_move: "outside_window" })
  18. 03:14:27ok approved by module process engineer · OCAP linked · logged
  19. 03:14:28cuopt.dispatch({ wip: 1840, constraints: ["reticle", "chamber", "qual"] })
  20. 03:14:32ok lot routed to ETCH-12/B · AMHS move to stocker ST-14
  21. 03:14:33amhs.move({ foup: "F-20911", to: "ST-14" })
  22. 03:15:21ok carrier delivered · handling exceptions 0
  23. 03:15:22mes.log_lot({ lot: "L-48213", genealogy: "full" })
  24. 03:16:27ok scenario complete · 10 steps · 1 hold reviewed · released

Reasoning trace

Plan, thought, action, observation, exactly as the orchestrator would record it.

GoalRun lot L-48213 through metal-1 on module M2, hold overlay and…

Run lot L-48213 through metal-1 on module M2, hold overlay and CD inside the layer spec, catch any excursion before physical metrology, and dispatch on cycle-time target.

PlanSimulate the lot on the twin first. Lead with litho so the cor…

Simulate the lot on the twin first. Lead with litho so the correctables are right before etch, then trim etch and CMP against virtual metrology, keep inspection continuous, and hold anything outside the qualified window for a human.

ThoughtThe previous lot's overlay residual on SCN-07 trended toward t…

The previous lot's overlay residual on SCN-07 trended toward the control limit. On the twin, a per-field correctable update with a small dose trim brings the predicted residual back to 2.6 nm without touching focus.

Actiontwin.simulate(candidates=64) returns set #41: per-field correc…

twin.simulate(candidates=64) returns set #41: per-field correctables and dose minus 0.3% on SCN-07, chamber B pressure and RF trims on ETCH-12, downforce minus 2% on CMP-03.

ObservationSet #41 predicts overlay residual 2.6 nm, CD uniformity inside…

Set #41 predicts overlay residual 2.6 nm, CD uniformity inside window and excursion risk 0.05. Nine candidates cut cycle time further but routed the lot to an unqualified chamber and were discarded.

ActionExecute set #41 under autonomy level L3: seven recipe writes i…

Execute set #41 under autonomy level L3: seven recipe writes inside the qualified window, the reticle hold and the out-of-window move routed to the module process engineer.

ObservationReticle-repeater signature on three dies at 03:09:40 from the …

Reticle-repeater signature on three dies at 03:09:40 from the fused inspection stream. Virtual metrology routed two wafers to physical measurement on predicted variance.

OutcomeScenario complete. Overlay and CD predicted inside spec, the r…

Scenario complete. Overlay and CD predicted inside spec, the repeater held and reviewed with the OCAP linked, the lot dispatched to a qualified chamber and released with full genealogy.

How it works

A goal becomes a plan becomes a run

Nothing about a Waferira run is implicit. The goal is declared, the plan is simulated on the fab twin, each step is typed and bounded to a qualified recipe window, and the outcome is written to the lot record.

Active path

The orchestrator plans, the agents act

A run starts as a goal, becomes a plan, and executes as a graph of typed steps across litho, etch, CMP, inspection, metrology and dispatch. The active path is always visible, always logged, always reversible.

RUNNING APPROVAL SUCCEEDED
<200 ms priority defect triage at the tool edge · design target
10 to 50 inspection streams per pilot module · design target
1 to 5 s virtual-metrology scoring per lot-step · design target
1 to 5 min dispatch re-optimisation cadence · design target
Human in the loop

Autonomy is graduated, not switched on

L1 advisory, L2 supervised writes, L3 bounded autonomy inside the qualified recipe window, L4 reserved for loops the fab has qualified. Each fab sets the level per agent, per tool, per shift, and every hold, out-of-window move and lot release waits for a named approver. The four figures above are design targets, not measured results.

Agent roster

Ten agents, a twin and an orchestrator

Each agent owns a module or a function of the fab, a bounded tool set and a metric the fab already measures. They negotiate for shared tools and recipes through the orchestrator, never directly. Five of them ship as named products.

agent.litho_overlay · shipped as Lithera

Litho-and-Overlay

Photolithography, overlay, focus and dose, CD

Predicts overlay, CD and focus-dose response per scanner, reticle and layer from metrology and inline defect signals, and closes run-to-run control by writing corrected correctables and focus-dose recipes over SECS/GEM, with computational-lithography context for mask-aware moves.

secs.write_recipemetrology.read_overlayculitho.context

agent.etch_depo

Etch-and-Depo

Etch and deposition uniformity, rate, film properties

Controls etch and deposition uniformity, rate and film thickness, stress and composition across the wafer from tool-sensor and FDC signatures, with Vmetra's virtual metrology grounding every move and the fab twin validating it before the lot runs.

fdc.read_chambervm.predictsecs.write_recipe

agent.cmp_implant

CMP-and-Implant

CMP planarisation, implant dose and uniformity

Holds CMP removal rate, dishing and erosion and implant dose and uniformity within window, scoring excursion risk in real time from FDC signatures and virtual metrology and trimming recipes inside the qualified bounds.

fdc.read_platenvm.predictsecs.write_recipe

agent.clean_diffuse

Clean-and-Diffuse

Cleans, diffusion and thermal budget

Controls cleans, diffusion and thermal budget against the process window, tracking particle and chemistry signals and the energy, gas and chemical use the fab pays for at every step.

fdc.read_furnacechem.read_bathsecs.write_recipe

agent.defect_inspect · shipped as Scanira

Defect-and-Inspect

Defect classification, particles, reticle excursions

Fuses inline optical, e-beam and SEM imagery at the tool edge to classify and predict defects, particles and yield-limiting excursions, auto-dispositions nuisance against killer defects, triages reticle and pattern excursions and raises inline holds.

vision.streamdefect.classifyhold.raise

agent.metrology_vm · shipped as Vmetra

Metrology-and-Virtual

Virtual metrology, run-to-run and advanced process control

Predicts metrology for etch, deposition, CMP, implant, clean and diffusion on every wafer from tool-sensor and FDC signatures, scores excursion risk, decides which wafers go to physical metrology, and closes run-to-run APC by handing corrected recipes to the process agents.

vm.predictfdc.read_lotstepapc.update_model

agent.yield_dispatch · shipped as Dispira

Yield-and-Dispatch

Yield, WIP, scheduling, dispatch, cycle time

Re-optimises WIP, scheduling and dispatch under reticle, chamber, qualification, route and hot-lot constraints, weighting every move by live yield and excursion risk from Scanira and Vmetra, with the fab twin validating the plan before it commits.

cuopt.dispatchmes.read_wiptwin.validate

agent.robot_handling · shipped as Dispira

Robot-and-Handling

FOUP, AMHS and wafer handling

Drives FOUP and AMHS moves and wafer handling so lots arrive when the dispatch plan expects them, with motion perception and exception detection at the fab edge and handling validated in simulation before it touches a carrier.

amhs.moveisaac.plan_pathstocker.read

agent.quality_conf

Quality-and-Conformance

Excursion response, non-conformance, wafer and lot genealogy

Runs excursion response and OCAP linkage, non-conformance and wafer and lot genealogy, gates lot release against the layer spec and assembles the traceability record every action on the lot has to leave behind.

mes.log_lotocap.linkaudit.write

agent.fab_knowledge

Fab-Knowledge

Recipes, integration specs, SEMI standards, OCAPs, engineer Q&A

Answers process-integration and yield questions from recipes, integration specs, SEMI standards and excursion and OCAP procedures, with every answer cited to its source and retrieval scoped to the tenant.

rag.retrievesemi.citeocap.lookup

twin.fabtwin · shipped as Fabtwin

Fab Twin

As-run wafer and fab twin, process and flow

Fuses process (litho, etch, deposition, CMP, implant, thermal) and flow (WIP, tools, AMHS, routes) into an Omniverse-based twin that simulates candidate recipes, correctables, WIP and dispatch moves, as-run against as-designed, and returns the predicted yield, uniformity and cycle time before the lot runs.

twin.simulatetwin.compare_asruntwin.validate

agent.orchestrator

Fab Orchestrator

Planning, arbitration, human approval

Plans the run, arbitrates between agents competing for the same tool or recipe, enforces the autonomy level, recipe bounds and tool-state checks, and routes anything outside the qualified window to a named approver.

plan.composepolicy.evaluateapproval.request
Where it pays

Four loops, four metrics

Waferira is not a dashboard. Each agent closes a loop a fab already measures in yield points, excursions, scrapped lots, review hours and cycle time. The tables show what each loop watches and what it is allowed to move.

Overlay and CD

Correct the scanner before the residual reaches the limit

Overlay residuals and CD drift are predicted per scanner, reticle and layer from metrology and inline defect signals. When the trend heads for the control limit the agent updates correctables and focus-dose inside the qualified window instead of waiting for a rework lot.

  • Overlay, CD and focus-exposure response modelled per scanner and layer
  • Computational-litho context so a correctable move is mask-aware
  • Every correctable and its later yield written into the training set
agent.litho_overlay SUCCEEDED
Correct the scanner before the residual reaches the limit: signals watched and recipes moved
SignalWatchesMoves
Overlay residualPredicted per field from metrology trendPer-field correctables
CDVirtual and sampled metrologyDose trim inside window
FocusFocus-exposure matrix driftFocus offset or hold
Unmeasured wafers

Measure every wafer, virtually

Physical metrology is sampled, so most wafers go unmeasured while uniformity drifts. Vmetra predicts the measurement from tool-sensor and FDC signatures on every wafer, routes the uncertain ones to the metrology tool and hands corrected recipes to the process agents.

  • Virtual thickness, uniformity and removal rate on every wafer
  • Sampling plan driven by predicted variance, not a fixed rate
  • Run-to-run APC fed on every lot-step rather than every sampled one
agent.metrology_vm SUCCEEDED
Measure every wafer, virtually: signals watched and recipes moved
SignalWatchesMoves
Film thicknessPredicted from FDC per waferDeposition time and rate trims via Etch-and-Depo
UniformityPredicted edge-to-centre profilePressure and RF trims inside window
Removal ratePredicted from platen telemetryDownforce and platen trims via CMP-and-Implant
Killer or nuisance

Disposition the defect before the engineer opens the image

Inspection tools produce more images than any review team can look at. Scanira fuses optical, e-beam and SEM at the tool edge, classifies each event, auto-dispositions nuisance against killer, and raises a hold on a reticle or pattern excursion while the lot is still in the module.

  • Optical, e-beam and SEM fused into one classification
  • Reticle repeater and pattern excursion detection with inline holds
  • Rare defect classes augmented synthetically and validated against real distributions
agent.defect_inspect SUCCEEDED
Disposition the defect before the engineer opens the image: signals watched and recipes moved
SignalWatchesMoves
Defect eventsClassified and dispositioned in real timeHold recommendation, signal to control agents
Reticle repeatersSame field position across diesReticle inspection hold via approval
Particle excursionsTool and step correlationSignal to Clean-and-Diffuse and dispatch
Cycle time

Rehearse the dispatch, then move the lot

Dispatch runs on rules and WIP bubbles anyway. Dispira re-optimises the dispatch list every few minutes under reticle, chamber and qualification constraints, weighted by live yield risk, and the fab twin checks the plan for cycle-time and yield effect before the AMHS moves a carrier.

  • Constrained optimisation across the whole WIP, not one bay
  • Hot lots and yield-risk lots weighted explicitly
  • Dispatch plan validated on the twin before commit
twin.fabtwin SUCCEEDED
Rehearse the dispatch, then move the lot: signals watched and recipes moved
SignalWatchesMoves
WIP by stepLive from MESDispatch list to qualified chambers
Reticle and chamber stateTool and qualification statusRouting within constraints
Predicted cycle timeTwin simulation of the planPlan accepted or re-optimised
Multi-agent handoff

Agents negotiate, they do not collide

Two agents will want the same chamber or the same lot. The orchestrator arbitrates on the run goal, not on who asked first, and the handoff is logged like any other step.

Contested move: ETCH-12 chamber B

  1. 01yield_dispatch.request(route L-48213 → ETCH-12/B) SUCCEEDED0.2 s

    Yield-and-Dispatch wants chamber B for lot L-48213 because it has the shortest predicted queue and the lot is on cycle-time watch.

  2. 02etch_depo.request(hold ETCH-12/B, trim) SUCCEEDED0.2 s

    Etch-and-Depo wants chamber B held for one lot to write a pressure and RF trim after FDC showed an edge-fast uniformity drift.

  3. 03orchestrator.arbitrate SUCCEEDED0.4 s

    A uniformity excursion on 25 wafers outranks minutes of queue time under the run goal "no excursion past metrology". Etch-and-Depo holds the chamber for one trim cycle.

  4. 04yield_dispatch.handoff(returned) SUCCEEDED58 s

    Chamber returned with the trim written and predicted uniformity recovered. Dispatch routes the lot in; the twin confirms the cycle-time target still holds.

Illustrative scenario.

Arbitration rules

  • Run goal first. Every request is scored against the declared goal, not the requesting agent's local objective.
  • Yield and excursion outrank cycle time. A scrapped lot costs more than minutes in a queue.
  • Time-boxed ownership. An agent holds a contested chamber or recipe for a bounded window, then must re-justify.
  • Everything is logged. The losing request, the score and the reason all appear in the run record.
  • Deadlocks escalate to a human rather than resolving by timeout.

See the agent roster

Autonomy

Four levels, set per agent and per tool

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.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · AdvisoryRecommends recipe moves, dispositions and dispatch, with citationsEnters every change manuallyShadow mode, first on the design-partner cell
L2 · SupervisedProposes a recipe write or hold; it executes on approvalApproves each move in the review consoleAssist mode, where accuracy and ROI are proven
L3 · BoundedWrites inside the qualified recipe window, tool-state checks and OCAP linkageApproves holds, out-of-window moves and lot releaseGraduated autonomy for low-risk APC, defect and metrology loops
L4 · Qualified loopsRuns a qualified loop without prompting, inside its envelopeSets the envelope; reviews the shift recordPlanned; reserved for loops the fab has qualified
Targets

Design targets, stated as targets

These are the figures in our compute plan. None is a measured result. Every pilot measures against the fab's own baseline, reproduced from the fab's own yield, excursion and cycle-time records, not from our telemetry.

500 to 2,000 GPU-hours per process family per quarter for retraining · design target
1,000 to 10,000 process and dispatch simulations per fab per day on the twin · design target
100k to 1M synthetic rare defect and excursion variants per module · design target
nightly virtual-metrology and FDC model retraining as recipes and chambers drift · design target
Segments

Where fabs start

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.

Advanced logic and foundryLitho-bound, overlay and CD

Advanced logic and foundry

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.

Memory: DRAM, NAND, HBMHigh-volume, 3D complexity

Memory: DRAM, NAND, HBM

High-aspect-ratio etch and deposition uniformity and CMP planarisation on long flows. Vmetra and Scanira where excursions are most expensive.

Analog and mixed-signalMature nodes, long tails

Analog and mixed-signal

Many products, many recipes, few engineers per tool. Virtual metrology and defect disposition to cover more wafers with the same team.

Specialty and compound semiconductorDifferent materials, same loop

Specialty and compound semiconductor

SiC, GaN and photonics fabs with their own defect and uniformity physics. Scanira and Vmetra models trained per process family.

New fabs and node rampsBlind commitments

New fabs and node ramps

Reshored and greenfield capacity ramping under schedule pressure. Fabtwin de-risks the ramp before lots run.

Accelerated computing

Physical AI, at the tool

Computational lithography, defect classification on e-beam and SEM imagery, per-wafer virtual metrology and a full-fab twin are among the most compute-intensive workloads in manufacturing. Waferira keeps IP-sensitive inference and feature storage at the fab edge and runs training, simulation and optimisation on GPUs the fab controls.

Metropolis · DeepStream · Holoscan · TensorRT

Inspection vision

Inline optical, e-beam and SEM imagery and sensor fusion on fab-edge GPUs. 10 to 50 inspection streams per pilot module and sub-200 ms priority defect triage are the design targets.

CUDA · RAPIDS · Triton

Virtual metrology and FDC

High-volume multivariate tool-sensor and FDC time-series scoring on every wafer, 1 to 5 seconds per lot-step in the design, with nightly retraining as recipes and chambers drift.

DGX or HGX · CUDA · cuDNN

Training

Defect, virtual-metrology and process-response models retrained per process family; 500 to 2,000 GPU-hours per family per quarter is the design target. Dedicated capacity is planned.

Omniverse · OVX

Fab twin

As-run process and flow simulation, 1,000 to 10,000 candidate recipe, metrology and dispatch scenarios per fab per day in the design. OVX access is planned.

Cosmos · Omniverse Replicator

Synthetic rare events

Rare defect, particle, overlay-drift, CMP-dishing and film-uniformity variants generated and validated against real distributions before promotion. Planned.

cuOpt · RAPIDS

Dispatch optimisation

Constrained WIP dispatch re-optimised every 1 to 5 minutes across reticle, chamber, route, tool-state and cycle-time constraints.

Jetson Orin · Isaac · TensorRT

AMHS and handling

Local FOUP and robot perception and exception detection at the fab edge. Jetson Thor is planned for higher sensor density.

NIM · NeMo · Retriever · Guardrails · AI Enterprise

Process reasoning

Tenant-isolated process Q&A and OCAP reasoning over recipes, SEMI procedures and audit logs, with citations enforced on every answer.

Developers

Define an agent, bound it, run it

The Waferira SDK is typed Python. Tools are declared with schemas and recipe-window limits and the policy engine enforces them at call time, not in a review meeting. This is a design preview; the API will change before release.

What you get

  • Typed tool definitions with recipe-window and rate limits per parameter
  • Deterministic replay of any historical lot against a new model
  • Local twin harness so a recipe move is simulated before it is shipped
  • Autonomy policy as code, versioned and reviewed like any other change

Read the docs Developer guide

scn07_litho_agent.py
# Design preview. Bound the litho agent to scanner SCN-07.
from waferira import Agent, Tool, Limit, Autonomy

recipe = Tool(
    name="secs.write_recipe",
    tool="SCN-07",
    params=["correctables.per_field", "dose"],
    limits=[Limit(window="qualified", max_step="0.5%", per="lot")],
)

litho = Agent(
    id="agent.litho_overlay",
    goal="overlay residual < 3 nm, CD inside M1 window",
    tools=[recipe, Tool("metrology.read_overlay", read_only=True)],
    # bounded writes; humans still gate holds and out-of-window moves
    autonomy=Autonomy.L3,
    # simulate on the fab twin before every write
    verify="twin",
)

run = litho.start(lot="L-48213", layer="M1")
for step in run.stream():
    print(step.name, step.status, step.duration)
CLI

Start a run from anywhere

The same run engine, the same policy checks, the same IP-isolated audit trail, from the terminal, the review console or the SDK. Design preview.

waferira · cli · scenario
$ waferira run "lot L-48213 through M1 on module M2" --autonomy L3

→ plan composed          10 steps · 1 approval gate
→ twin.simulate          64 candidates · best #41 · excursion risk 0.05
→ policy.evaluate        7 recipe writes inside window · 1 held for human
→ executing              litho.correctables .. ok   1m20s
→ executing              etch.uniformity .... ok   58s
→ executing              cmp.removal ........ ok   46s
→ executing              vm.score ........... ok   2.1s
! approval required      reticle_hold · recipe move outside window
→ approved               module process engineer · 03:14:27
→ scenario complete      1 hold reviewed · lot L-48213 released

$ waferira lots show L-48213 --format genealogy
Pricing

Priced per module, per fab, per group

Land on one workflow with a measured baseline. Expand by module, tool fleet, fab and autonomy level. Outcome components are available on yield-point value, excursions and cycle time. Annual prepay carries a 15 to 20% discount.

Billing period
Module $30,000 per process module or tool fleet / month · billed monthly

APC, defect or virtual-metrology AI for one module: litho, etch, deposition or CMP. For fabs validating ROI on the wedge, IP-isolated from day one.

  • One module or tool fleet, one agent
  • Fab-edge inference node included
  • SECS/GEM, APC, inspection and metrology connectors
  • Run log, IP-isolated audit trail, lot genealogy
  • Business-hours support
Start a pilot
Enterprise Custom land $2M to $20M ACV

Multi-fab IDMs and foundries standardising on Waferira, with custom process, device and yield models and a managed fab-edge fleet.

  • Multi-fab fleet management
  • Custom process, device and yield models
  • Fab-edge fleet with on-prem control plane
  • Group autonomy policy and approval chains
  • SLAs, SSO and RBAC, dedicated engineer
Contact us
Who it is for

Built for the people who run the fab

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.

Fab, Operations or Yield Director

Owns yield, throughput, cycle time, excursion response and cost per wafer.

What this person is dealing with today

  • Reactive process control that lets overlay, uniformity and CMP excursions destroy yield
  • Multi-million-dollar lot scrap from undetected excursions
  • A severe, scarce process and yield engineering shortage that caps the ramp

Process Integration or Module Engineer

Owns litho, etch, deposition, CMP and implant recipes, process windows and APC.

What this person is dealing with today

  • APC, defect, metrology and MES siloed and reactive across the fab
  • Correctables that lag because metrology is sampled
  • Rule-based dispatch and WIP management that inflate cycle time

Yield, Defect or Metrology Engineer

Owns defect classification, metrology, virtual metrology, yield analytics and wafer and lot genealogy.

What this person is dealing with today

  • Manual, engineer-bound defect classification and SEM review drowning in data
  • Metrology bottlenecks and sampling gaps that miss yield-limiting excursions
  • Genealogy stitched by hand across tool, metrology and MES data
Integrations

It speaks SECS/GEM, not cloud

Waferira reads and writes through the systems already in the fab. No rip and replace, no parallel historian, no new HMI to learn. Vendor names are examples of systems found in front-end fabs; connector availability is confirmed per site.

Tool integration

SECS/GEM on scanners, etchers, deposition, CMP, implanters, furnaces and wet benches

Recipe reads and bounded recipe writes

APC and run-to-run

Advanced and run-to-run process control systems (Applied Materials APF and APC, PDF Solutions, in-house IDM APC)

Model state, correctables, control limits

Defect inspection

Inline optical, e-beam and SEM inspection and review tools (KLA, Applied Materials, Hitachi High-Tech, Onto Innovation class systems)

Images, defect maps, ADC classes

Metrology

Overlay, CD, film and OCD metrology (KLA, Onto Innovation, Nova class systems)

Sampled measurements that ground virtual metrology

FDC and tool sensors

Fault-detection and tool-sensor streams per chamber

Per-wafer signatures for virtual metrology and prognostics

Yield management

Yield and defect analytics (PDF Solutions Exensio, Synopsys, Siemens Camline, INFICON class systems)

Yield, bin and genealogy context

MES and scheduling

Fab MES and schedulers (Applied SmartFactory, Siemens Camstar, Critical Manufacturing, INFICON FPS class systems)

Lots, routes, WIP, dispatch lists

AMHS

Stockers, vehicles and FOUP handling (Daifuku class AMHS)

Carrier moves and handling exceptions

See all integrations

Guardrails

An agent that can move a recipe needs a leash

Waferira writes to production tools over SECS/GEM. Every capability is scoped to a qualified recipe window, every write is policy-checked against tool state, and every action is written to an append-only, IP-isolated audit log the fab owns.

  • Recipe bounds. Each agent writes only inside the qualified recipe window for that tool, with explicit per-parameter limits.
  • Policy and tool-state checks before every write. Autonomy level, tool state, qualification, interlocks and shift are evaluated before a recipe moves.
  • Human-in-the-loop gates. Holds, out-of-window moves and lot release wait for a named approver, with OCAP linkage on every excursion.
  • Immutable, IP-isolated audit log. Append-only and exportable. Every action records source signals, retrieved procedures with citations, predicted impact, allowed range, rollback condition, approver and lot scope.
  • Rollback. Declared rollback conditions return a recipe to its previous qualified version; loss of the edge node leaves the tool on its own controller and recipe.
  • Tenant and IP isolation. Recipes, device designs, defect libraries and process memory never cross a customer boundary. Inference and feature storage stay at the fab edge; an on-prem control plane is available for IP-sensitive fabs.

Compliance posture

Compliance and certification status
ItemScopeStatus
SOC 2 Type I and fab-security reviewControl plane QUEUED Planned, first 6 months
SOC 2 Type IIControl plane QUEUED Planned, 6 to 12 months
SSO and RBACConsole and approvals QUEUED Planned, 6 to 12 months
IP-isolation and security assurance packageFab security and IT and OT review QUEUED Planned, 6 to 12 months
SEMI-standards-cited reasoningRecipes, integration specs, OCAPs RUNNING In the design, every answer cites its source
Per-tenant IP isolationData, models, memory RUNNING In the design from day one
On-prem and fab-edge deploymentIP-sensitive fabs RUNNING Design option

Read the security overview

Enterprise

Standardise autonomy across the group

One policy model, one audit trail, one benchmark across every module in every fab, with the process, device and yield models kept private to each site.

Talk to us Enterprise details

  • SSO and role-based access down to the recipe parameter, planned for the 6 to 12 month release
  • Group-wide autonomy policy with per-fab override and approval chains
  • Cross-fab benchmarking on yield, excursions, cycle time and virtual-metrology accuracy without moving recipes across tenants
  • On-prem control plane and fab-edge deployment for IP-sensitive fabs
  • Edge autonomy that survives control-plane loss by leaving each tool on its own controller and qualified recipe
  • Dedicated deployment engineer and quarterly model review per fab
FAQ

Straight answers

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.

Get started

Bring autonomy to your fab

Start with one process module or tool fleet and one measurable baseline. A paid, IP-isolated pilot on defect classification, virtual-metrology-driven overlay and CD control or uniformity APC shows the number before you commit further.