Open Source · Public-by-default

Designs worthy of trust.

We believe in open-source for the foundational layers where a leap of faith isn't good enough. We are major contributors to Pavona, an open-source silicon ecosystem. Design, cryptography, and toolchain are public-by-default, so customers, researchers, and regulators can read the same code we do.

Why open

Trust comes from inspection.

Closed silicon asks customers to take a vendor's word for it. Open silicon hands them the source — and the audit trail that goes with it.

> auditable

Read what runs

Every block in the Pavona platform — from the boot ROM to the cryptography accelerators — lives in a public repository. Researchers, customers, and certification labs read the same source.

> portable

No vendor lock-in

The design is portable across foundries and tooling, without modification restrictions. Open-source IP doesn't disappear when a roadmap shifts or a supplier is acquired.

> durable

Outlives any one company

15+ year device lifecycles need a trust anchor that outlives any single vendor. A healthy open-source platform provides exactly that (enhanced with cryptographic ownership transfer).

What we publish

The work that lives in the open.

Pavona is more than a chip — it's a stack. Here's what's public.

> pavona

Pavona — the platform

An open-source silicon platform that is secure-by-design. RTL, threat model, docs and verification collateral — all reviewed in public and hosted by GlobalPlatform, a neutral non-profit.

Pavona Repo ↗
> cryptography

Pavona cryptography stack

Production-grade classical and post-quantum cryptography — ML-KEM, ML-DSA, SLH-DSA, AES, HMAC, and more — written for resource-constrained silicon and reviewed in the open.

Pavona cryptolib ↗
> tooling

Silicon CI & verification

The toolchain that makes “design silicon like software” actually work: verification rigs, simulation harnesses, and the verifications flows the Pavona project runs on every commit.

Pavona CI ↗
> specs

Specifications & protocols

The threat models, hardware specifications, and support infrastructure that go alongside the code, so the community can build compatible parts and run independent audits.

Pavona Docs ↗
Get involved

Three ways to plug in.

/ 01

Read & review

The fastest way to help is to read the code, file issues, and review proposed changes. Once Pavona repositories are public, everything happens in the open.

/ 02

Build & tape out

The design is open hardware. Implementers, foundries, and silicon programs are welcome — the path from clone to silicon is documented.

/ 03

Join the conversation

Pavona makes technical decisions in public forums. Join the mailing lists to participate in the conversation. Organizations serious about open silicon have a seat at the table.

// get involved

Build on open silicon, with us.

Whether you want to ship product on Pavona, contribute upstream, or just understand what we run — we're easy to reach.

Start a conversation →info@zerorisc.com