What an MSP does with 300 customers' certificates
One certificate is a chore. Three hundred customers' certificates are a capacity problem, and from 2029 the capacity you need is more than four times what it is today. The only way to staff it is to not staff it.
The arithmetic
Take a modest book: 300 customers with 400 certificates each, 120,000 certificates. Renewed at expiry, today's 200-day lifetime means about 4,200 renewals a week. At 47 days it is close to 18,000 a week, and renewing ahead of expiry, as any sane policy does, pushes the real number higher.1 No service desk does that. It is a machine's job, and the machine has to be trusted with every customer's keys and every customer's evidence at once.
What "one control plane for many customers" has to mean
- Isolation by construction. Every tenant-scoped query runs behind PostgreSQL row-level security, so a missed condition in application code is a test failure rather than a cross-customer incident.2 A silo mode on top of that floor keeps a customer's identities, secrets and audit trail behind their own tenant line, and dedicated deployments exist for customers whose posture requires them.1
- Keys behind a hard boundary. The control plane orchestrates; a separate signer process holds every customer's keys and signs over a constrained channel.3 An operator with control-plane access is never an operator with key material.
- Evidence per customer. Every issuance, renewal and revocation is an immutable event in a tenant-scoped, hash-linked audit log; a customer's history is replayed from the record, not reconstructed from tickets, and can be exported as a signed bundle a customer can verify offline.4
- Delegation, quotas and break-glass. Onboarding and retiring a customer, delegating an operator to them, setting quotas and granting emergency access are operations in the same authority history, not a spreadsheet beside it.1
- Metering that fails closed. Usage per customer is recorded under the same tenant floor for your own invoicing; a period the metering store cannot vouch for is reported as unknown, never as zero.1
The commercial line
An MSP is allowed to do this. trstctl's core license expressly permits running it inside a customer's own deployment as their service provider, and the Provider edition adds the multi-customer operations above as licensed features, with managed-service and resale rights, in an offline-signed license, checked by local signature math with no phone-home.1,5 trstctl is alpha software; the isolation properties above are the product's own tests, and a design partner should read them as claims to verify, with the code available to do it.
The MSP page has the renewal calculator for your own book, and the editions page the Provider edition in the product's own terms.
Sources
- trstctl, For MSPs: the renewal calculator, the Provider edition, siloed isolation, customer lifecycle, metering as invoice evidence, and managed-service rights.
- trstctl documentation, Configuration and Compliance: tenant-scoped rows and audit checkpoints under PostgreSQL row-level security.
- trstctl, Signing service design.
- trstctl documentation, Compliance: completeness, attribution, hash-linked tamper evidence, and signed offline-verifiable export.
- trstctl documentation, Editions: the offline Ed25519-signed license and its 30-day grace period; Licensing.