Singapore

SOUTH KOREA BUYER PATH · ENGLISH

Turn an early chip plan into a reviewable MPW path

A visual, non-confidential path for South Korea fabless, startup and research teams—from chip idea to human fit review without exposing design IP.

Start a non-confidential inquiryCheck MPW readiness
English reviewNo design-file uploadHuman-confirmed routeNo public capacity promise
Shared silicon wafer and engineer handling prototype chip samples for an MPW fit review
Prototype outcome first; node and shuttle claims remain case-specific.

DIRECT ANSWER

How should a South Korea team start an MPW inquiry?

Share the chip function, design stage, die-area range, timing and required sample outcome. MST screens the next questions; foundry acceptance, PDK/NDA, slot, capacity, price and schedule remain human-confirmed.

FOUR REVIEW GATES

Make the prototype path executable before discussing a slot

These four decisions turn an abstract chip ambition into a requirement that engineering and commercial teams can review.

01

Application and process fit

Lead with chip function and device needs—not a node label alone.

02

Design and PDK readiness

Name the stage: concept, schematic, layout, DRC/LVS or clean GDSII.

03

Package and test outcome

Choose bare die, packaged samples, wafer probe or electrical test.

04

Schedule, commercial and compliance fit

Share the target window, die-area range, sample quantity and end use.

Not sure where your design stands?Run the readiness check →
Three integrated-circuit layouts representing different process-fit decisions

OPEN ONLY WHAT YOU NEED

Two checklists. No public design files.

01What to prepare for first review
  1. Company or institution, work email and South Korea location
  2. Chip function and non-confidential end-use summary
  3. Target node or process family, if already known
  4. Current stage: concept, schematic, layout, DRC/LVS or GDSII-ready
  5. Estimated die-area range rather than confidential layout data
  6. Target shuttle or prototype-silicon timing
  7. Bare-die, package, wafer-probe and test expectations
  8. PDK/NDA status and the next decision your team needs to make
02What not to send or assume
  • No GDSII, OASIS, RTL, netlists, source code or PDK files.
  • No assumption that 90nm, 55nm or 40nm means route availability.
  • No public promise of PDK access, slot, price, capacity, yield or schedule.
  • No assumption that submitting the form is foundry or order acceptance.
  • No confidential end-customer, circuit or controlled technical detail.
Send two details to MST
NON-CONFIDENTIAL EXAMPLEA useful first message is short and decision-readyOpen message template →
South Korea fabless team developing a mixed-signal control IC.
Target: mature-node feasibility review; 55nm is a preference, not a confirmed fit.
Stage: schematic complete, layout not started; no GDSII yet.
Outcome: packaged engineering samples with basic electrical test.
Timing: target prototype window in H1 2027.
Need from MST: process-fit, PDK/NDA path and package/test next-step review.
Engineers coordinating wafer, die, package and test decisions around a worktable

PUBLIC EVIDENCE · ROUTE STILL HUMAN-CONFIRMED

Use public process signals as questions, not availability claims

Public 90nm, 55nm and 40nm process signals help frame the discussion. They do not prove HHGrace MPW availability, acceptance or capacity.

Read the 2025 public evidence (HKEX) →

BUYER QUESTIONS

Questions to resolve before confidential exchange

Can a South Korea team start an MPW inquiry before GDSII is ready?

Yes. Initial screening can start from a non-confidential chip function, process preference, design stage, die-area range, target timing and package/test outcome. The public page is not a design-file handoff channel.

Does a 90nm, 55nm or 40nm label mean an MPW route is available?

No. Public node and process signals do not prove route availability, design fit, PDK access, slot, capacity, data acceptance or tapeout eligibility. Those points require case-specific human confirmation.

Can MST promise PDK or NDA access?

No public page can make that promise. Tell MST whether your team already has access, needs an approved access path or only needs feasibility screening before confidential exchange.

Should a buyer upload GDSII, RTL, netlists or PDK files?

No. Do not submit GDSII, OASIS, RTL, netlists, source code, PDK files or controlled technical data through the public website. Sensitive handoff must wait for the approved NDA and secure partner path.

What happens after the two-field inquiry?

MST places the request into a human-review queue, checks the missing process, readiness, package/test, schedule and compliance facts, and follows up. Submission is not foundry acceptance or a manufacturing commitment.

NEXT STEP · HUMAN REVIEW

Move from “can this be built?” to a reviewable path

Send only the non-confidential facts above. MST will ask for the missing decisions before any sensitive design exchange or route confirmation.

Published 2026-08-06 · Reviewed by MST Singapore Engineering Review
Send two details to MSTEmail sales@mst-sg.com