On 5 November 2026, Let's Encrypt announced new Sovereign Tech Agency funding for its post-quantum Merkle Tree Certificate authority. The contract supports standardization, production preparation and subscriber rollout through 2027. It funds an existing roadmap; the announcement does not establish that production issuance is available.
What the investment builds
The funder's project page specifies €1,072,000 for 2026–2027. Work includes issuance infrastructure, publisher and mirror services, realistic staging, failover, browser-requirement reviews and operator documentation. General availability is planned for 2027. The agency's announcement says the final launch also depends on browser requirements.
Why certificate operators should care
Let's Encrypt's June roadmap describes MTCs as batch-based certificate authentication: one signature covers a batch, browsers obtain signed landmarks separately, and a handshake can carry an inclusion proof. A larger standalone form handles stale landmark state. This concerns authentication, which is distinct from post-quantum key exchange.
That roadmap already targeted late-2026 staging and a production-ready environment in 2027, with changes needed across browsers, libraries and ACME clients. Those targets should not be read as confirmation that each milestone has been delivered.
Our suggested watch list
The useful next step is to assign ownership of the transition questions. We suggest a short record attached to your certificate pipeline, rather than a production change based on the funding headline:
- Issuance: Who will check official staging availability and document which client versions they actually test?
- Serving: Who owns the web server, reverse proxy or CDN configuration, and where will compatibility evidence be recorded?
- Acceptance: Which clients matter to your service, what failures would block a rollout, and who approves the rollback plan?
- Evidence: Keep announced targets, published support and results from your own environment in separate fields.
These are proposed planning checks, not results from a hands-on deployment. The funding gives teams a concrete project to follow; production decisions still need evidence for their own systems.