Sky130 and Open-Source Silicon MPW Options After eFabless

Answer block: Open-source silicon teams using Sky130 or TinyTapeout-style flows should evaluate shuttle eligibility, PDK compatibility, design-rule status, package/test expectations and commercial access before choosing a new fabrication path. MST can help screen mature-node and MPW route fit from a non-confidential brief, but MST is not a foundry and does not confirm a specific open PDK shuttle without partner review.

Open-source silicon has made chip prototyping more accessible, but fabrication access still depends on real shuttle programs, process rules, sponsor terms and partner eligibility. TinyTapeout publicly references support for projects affected by the eFabless shutdown on its official site, which is why many teams are now asking where Sky130 or open-source designs can go next.

Start with the design flow, not the slogan

“Open-source silicon” can mean different things: a TinyTapeout project, a Sky130 educational design, an OpenLane-based digital block, a university tapeout, or a startup prototype that began in an open flow. Each case has different constraints. The route must match process, design rules, IP policy, packaging and end-use requirements.

Questions to ask before choosing a route

• Is the design tied to a specific PDK such as Sky130, or can it migrate to another mature-node process?
• Are DRC/LVS reports available from the correct rule deck?
• Is the design educational, research, open-source, commercial or customer-funded?
• What package and test setup does the team need after silicon?
• Are there export-control, country, university or company eligibility constraints?
• Does the team need only a shuttle slot, or also review, packaging and logistics coordination?

Why migration is not automatic

A layout built for one open PDK is not automatically portable to another process. Device models, layers, design rules, IO cells, memories, ESD, pad ring and analog behavior can change. For simple digital educational designs, migration may be manageable. For analog, RF, high-voltage, sensor or mixed-signal designs, process fit must be reviewed carefully.

How MST can help

MST can help turn an open-source silicon request into a partner-readable brief: node/process dependency, design size, flow status, package/test assumptions, organization type and timeline. The goal is to identify whether a mature-node MPW coordination route is plausible before any private layout is shared.

FAQ

Can MST fabricate a Sky130 design directly?

MST is not a wafer foundry. MST coordinates RFQ screening and partner routing. Specific PDK and shuttle compatibility must be confirmed case by case.

Can I start with an OpenLane or TinyTapeout-style design?

Yes, for initial route screening. Share non-confidential flow status, design type, size and goals, not private GDS or design IP at intake.

What if my design must stay on Sky130?

Then the search is narrower. Route screening should focus on programs that explicitly support the required process and rule path.

For general planning, start with the MPW shuttle guide, the open MPW tools and the MST MPW coordination page.

← Back to News