Tenant PKI #
What a tenant does with Deevnet’s certificates: service certificates under site-less names, a Deevnet Pi that holds them, and devices with certificates of their own. The CAs themselves are TLS Cert Automation.
✓ 7 |
↻ 0 |
⏳ 1
(8 total)
Legend: β Complete | π In Progress | β³ Planned
Value objectives: Works anywhere, Secure by default
- β Tenants’ own services on Deevnet certificates (CHG-0047) 2026-10-11
- β Tenant names not tied to a site, issued by the Deevnet API and Terraform provider (CHG-0054) 2026-10-25
- β The EdS tenant’s certificates reissued under a name not tied to a site (CHG-0055) 2026-11-01
- β The secret store itself refuses tenant certificates for a site’s or the platform’s own names (CHG-0059) 2026-11-07
- β The Raspberry Pi image tenants take home kept current with its setup tool, deevnet-kit (CHG-0049β0051) 2026-10-18
- β The first take-home Pi installed with Deevnet certificates, using a name not tied to a site (CHG-0056) 2026-10-29
- β The take-home Pi image in the tenant downloads, using Deevnet certificates by default or a starter kit for an owner’s own 2026-11-08
- β³ IoT devices issued their own certificates through the Deevnet API
Project plan: Tenant PKI