PDK, NDA and GDS: What Happens Before MPW Tapeout?
Before MPW tapeout, teams need the right NDA and PDK path. GDS should come later, after process fit and review path are confirmed.
- →Why the order matters
- →What is a PDK?
- →What is an NDA?
- →What is GDS?
- →A safer MPW sequence
Answer-first summary: The safe MPW sequence is outline RFQ first, then process-fit and compliance screen, then NDA/PDK path, then controlled technical review and GDS exchange. GDS, RTL, netlists and proprietary design IP should not be sent at public intake.
In MPW planning, teams often ask whether they should send GDS first. For a disciplined RFQ process, the safer answer is no. The first step should be high-level screening. Detailed design files should come later, after the proper NDA, PDK and partner-confirmed review path are clear.
Why the order matters
A chip design file is not a casual sales attachment. GDS, OASIS, netlists, RTL, schematics, PDK files and proprietary scripts can reveal valuable design IP. Sending them before the correct review path exists creates unnecessary risk for both buyer and coordinator.
The correct first step is to confirm whether the request is plausible, whether the process family is in range, whether the geography and end-use context can be reviewed, and whether the request can move toward an NDA and PDK path.
What is a PDK?
PDK stands for process design kit. It contains design rules, models, layers and process-specific information needed to design a chip for a particular process. PDK access is sensitive and normally controlled by agreement.
Without the right PDK path, a team cannot responsibly prepare final layout for a specific manufacturing process.
What is an NDA?
NDA stands for non-disclosure agreement. It sets the confidentiality framework for exchanging sensitive technical and commercial information. For MPW, the NDA path should be clarified before detailed design information, PDK material or layout files are exchanged.
What is GDS?
GDS or GDSII is a layout file format used to represent the physical mask layout of an integrated circuit. It can contain sensitive design information. It should not be sent casually during an initial inquiry.
At the earliest stage, teams can use non-confidential metadata instead: estimated die area, top-level dimensions, process family, sample count, package assumptions and timeline.
A safer MPW sequence
- Submit a high-level RFQ brief.
- Screen customer, country, end-use and process fit.
- Clarify possible mature-node or specialty-process routes.
- Establish the NDA and PDK path if the case is qualified.
- Proceed to controlled technical review.
- Exchange design detail only under the right conditions.
How AI can help without seeing design IP
AI can help structure the first brief, detect missing RFQ fields, separate public planning questions from NDA-gated questions and prepare a package/probe/test checklist. It should not be used as an excuse to upload confidential design files into a public intake channel.
How MST applies this boundary
MST supports the early coordination layer for mature-node MPW RFQs. Qualified requests are routed toward case-by-case partner confirmation. The public intake is intentionally limited to non-confidential scope so that design files move only when the path is clear.
FAQ
Can I ask about MPW before I have PDK access?
Yes. The first RFQ can screen whether the project direction is plausible before a PDK path is established.
Should I upload GDS at intake?
No. A public first RFQ should not require GDS, netlist, RTL, schematics or confidential layout files.
Can a local GDSII inspector help?
Yes. A local-only tool can extract non-confidential metadata such as top cell, die size and layer count without uploading the file to a server.
Next step: Start with an outline MPW RFQ and keep design IP private until the NDA, PDK and partner-confirmed review path are clear.
Related Articles
Ready to scope your run?
Send node, process family, die area, volume and timeline - no design IP. We screen it, route to a qualified partner, and return an indicative quote.