REBELPDK

Each foundry distributes its Process Design Kits (PDK) through its own systems, with its own access model, security assumptions, and tooling constraints. For foundries, that means the burden of secure distribution never truly goes away. PDKs are treated like files, so protection depends on downstream environments, network controls, and internal policy. Once a PDK leaves the foundry's control plane, enforcement becomes procedural, visibility drops, and risk rises. The only lever left is friction: more gates, longer approvals, tighter restrictions, and still no cryptographic guarantee that the PDK can't be copied or misused.

For chip designers, the fragmentation is equally punishing. Teams evaluating or building across multiple processes must navigate different portals, credentials, approval paths, and infrastructure setups for every foundry and node. Environments multiply, workflows diverge, and engineers lose days to access logistics and compliance overhead. Evaluations slow down, iteration cycles stretch, and time-to-market takes the hit.

Therefore, it is our pleasure to announce RebelPDK.

RebelPDK solves this problem by turning PDK access into a governed, cloud-native service instead of a file handoff. Engineers request the exact foundry, node, and PDK version they need through one platform, follow a consistent approval workflow, and then work inside streamed cloud environments where the PDK stays protected. Access is enforced cryptographically, so decryption and use are only possible in approved, verified conditions.

The result is a better deal for everyone. Foundries gain stronger control, better auditability, and a safer distribution model that scales. Chip designers get faster access, a consistent workflow across processes, and less operational drag. RebelPDK makes advanced-node work feel immediate, while keeping PDKs protected by design.