MPW Singapore and Asia Access: What Overseas Fabless Teams Should Prepare
How overseas fabless, university and research teams can prepare a non-confidential MPW access brief before discussing nodes, PDK, NDA, packaging and logistics.
- →What engineers should clarify first
- →Why geography belongs in an MPW brief
- →What MST can and cannot claim
- →Good first brief
- →How this connects to MST
Answer-first summary: MPW access for overseas teams starts with a non-confidential readiness brief: node target, process family, die area, package/test expectations, schedule and geography constraints. MST positions Singapore as a coordination desk, not a foundry, and routes MPW cases only after feasibility, NDA and partner-confirmed review.
A fabless startup or university team outside the usual US and European shuttle channels often has the same first question: where do we start without sending the design? The practical answer is not a GDS upload. It is a clean access brief that lets a coordinator screen process fit, confidentiality path, packaging and logistics before confidential data is exchanged.
What engineers should clarify first
| Question | What to prepare | Why it matters |
|---|---|---|
| Where is the team located? | Country, export/logistics constraints, preferred contracting region | MPW access is not only technical. It also depends on routing, documentation and partner eligibility. |
| What is the chip goal? | Prototype, research silicon, customer sample, risk-reduction run | A research shuttle and a commercial pre-production path have different review expectations. |
| What process family is needed? | Digital CMOS, analog, mixed-signal, RF, BCD, high-voltage, eNVM or MEMS need | The process family narrows whether a mature-node MPW route is plausible. |
| What can be shared first? | Node target, die area, IO count, package/test direction, timeline | High-level fields allow screening without GDS, RTL, netlist or layout IP. |
Why geography belongs in an MPW brief
Teams in India, Southeast Asia, the Middle East or smaller research ecosystems may not fit neatly into a domestic university shuttle or a US-centered broker workflow. Geography affects contracting, documentation, import/export handling, sample shipment and support time zone. It should be treated as a scoping variable, not an afterthought.
What MST can and cannot claim
MST is not a wafer foundry and does not sell reserved foundry slots. The coordination role is to turn a high-level MPW request into a reviewable package, screen whether it belongs on an MPW path, and move to NDA/PDK steps only when the case is partner-confirmed.
Good first brief
A good first brief says: target node or node range, process family, estimated die area, shuttle urgency, packaging direction, sample quantity, test expectations and geography/logistics constraints. It does not include GDS, RTL, netlists, schematics or confidential customer drawings.
How this connects to MST
Start with a non-confidential MPW access brief: node range, process family, die area, package/test direction and timeline. MST uses this article as an intake guide, not as a promise of partner access, compliance certification, fixed sample count, fixed pricing, or automatic production approval.
FAQ
Can a non-US or non-European team use MPW?
Often yes, but eligibility and routing depend on the specific process, partner path, export/logistics constraints and contracting requirements. Treat geography as an early screening field.
Should I send GDS in the first email?
No. The first contact should be a high-level non-confidential brief. Confidential design files belong after NDA, PDK and partner-confirmed review.
Is MST a foundry?
No. MST is a Singapore coordination desk for sourcing, MPW scoping and engineering workflows. Foundry access is case-by-case and partner-confirmed.
Public references for engineering context
准备定义您的项目？
发送节点、工艺类型、芯片面积、数量和时间线 - 不包含设计 IP。我们筛选后对接合格伙伴，并返回伙伴确认后的下一步。