MSTSingapore
All

MPW buyer question

PDK/NDA access path for MPW screening

Prepare the PDK and NDA context MST needs before routing a mature-node MPW RFQ for partner review.

RFQ non-confidential firstHuman confirmed route

Direct answer

How should buyers discuss PDK/NDA access before MPW?

PDK/NDA access path is part of MPW screening, not something MST promises publicly. Buyers should state whether they already have PDK access, need a partner-approved access path, or only need first-pass feasibility before confidential exchange.

  • MST can separate non-confidential screening from NDA-gated design-file exchange.
  • The first RFQ should describe node, process family, design type and readiness state without attaching PDK files or controlled data.
  • Partner acceptance, NDA route, PDK access and allowed file movement are confirmed case by case.

What to prepare

  1. Current PDK/NDA status: none, in progress, existing access, or partner-specific access needed.
  2. Non-confidential design type and application context.
  3. Company country, customer type and intended end use.
  4. Expected design-stage status: concept, schematic, layout, DRC/LVS, or ready for review.

Public boundary

  1. Public intake is not a PDK download path.
  2. MST does not accept PDK files, mask data or confidential design packages through the public form.
  3. NDA sequence, partner approval and secure file path come after human review.

Next step

Turn this into a reviewable MPW RFQ

Share a short non-confidential brief first. MST screens node, process, PDK/NDA, package/test, schedule, country and end-use before any sensitive design-file path.

MPW hub →
MPW pricing factors

MPW pricing factors without public price promises

What drives MPW pricing before a formal quote?

package/test scope

MPW package/test scope before RFQ

What package/test details matter before an MPW RFQ?

academic and startup MPW

Academic and startup MPW intake

How should academic and startup teams start an MPW inquiry?