Pricing

Priced per module. Justified per yield point.

Module, Fab and Enterprise. The Module tier covers APC, defect or virtual-metrology AI on one process module or tool fleet. Fab covers the whole loop and the twin. Enterprise is for multi-fab IDMs and foundries. Annual prepay carries a 15 to 20% discount and outcome components are available on yield-point value, excursions and cycle time.

Module · $30,000 per module / monthFab · $220,000 / monthEnterprise · $2M to $20M ACV

Packaging logic

Land, expand, monetise the value

  1. Land. Low-friction, IP-isolated entry on one module with a clear ROI metric, on the Module tier.
  2. Expand. Modules, tool fleets, fabs and autonomy level, into Fab and Enterprise.
  3. Monetise value. Usage and outcome pricing capture upside as the agent does more of the work; a yield point is worth a great deal at fab scale.

Floor pricing is protected. Discounts are traded for term length and a reference where IP allows.

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
Compare

What is in each tier

Products are licensed per module or tool fleet on the Module tier and bundled on Fab and Enterprise.

What is in each tier
CapabilityModuleFabEnterprise
Modules covered1All in the fabAll fabs in the group
Agents1 of 5 productsAll agentsAll agents + custom models
As-run fab twin (Fabtwin)NoIncludedCustom process and flow models
Fab-edge nodeIncludedPer moduleFleet managed
Bounded recipe writesQualified window, one moduleAll qualified windowsGroup policy
Wafer and lot genealogyIncludedIncludedIncluded + export
Autonomy levelsL1 to L2L1 to L3L1 to L4 on qualified loops
SSO and RBACNoPlannedPlanned, with approval chains
On-prem control planeNoOptionalIncluded
SupportBusiness hours24/724/7 + named engineer
Indicative price$30,000/mo$220,000/mo$2M to $20M ACV
ROI

The arithmetic a fab runs

We do not publish savings percentages because we have not measured any yet. These are the inputs a fab brings to the pilot baseline, and the outputs the pilot measures.

Inputs you already have

  • Yield by layer and the value of a yield point at your wafer starts
  • Excursions per quarter and the lots scrapped or reworked per excursion
  • Defect-review hours per week and the nuisance rate on the inspection cell
  • Metrology sampling rate and the wafers and steps that go unmeasured
  • Cycle time and on-time delivery in the area under review
  • Engineer hours spent on manual APC, disposition and dispatch

What the pilot measures

  • Defect-classification and excursion-prediction accuracy and virtual-metrology error against the engineer and metrology baseline
  • Yield improvement on the wedge module
  • Excursion and cycle-time reduction
  • Scrap-lot reduction and engineer-load reduction
  • A hard ROI metric tied to yield-point value and the Module price
  • Conversion of the design partner to paid
Run timeline · scenario

What you are actually buying

A run engine that produces this record on every lot, every shift, on every module you license.

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.

Segments

Which plan fits

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.

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

Start with one module

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.