A ctlplne studio product
22 October 2026 · 3 min read

Self-hosted PKI and data residency

A list of every certificate you own is a list of every service you run, its name, its expiry and, often, who is responsible for it. That is reconnaissance, packaged. Before handing it to a service, ask what else goes with it.

Self-hostingAudit and ownershipKey protection

What the inventory reveals

Certificate management data looks harmless because each row is public-ish: a hostname, a validity window, an issuer. Together the rows are your internal service map, your naming conventions, the timing of every rotation, and the addresses of the management interfaces nobody should know about. Add the private keys, if the service holds them, and it is the ability to impersonate all of it. Add the audit trail and it is a record of who has authority over what.

Your infrastructure boundary containing the inventory, keys, audit trail and the license check; outside it, only what you choose to send your infrastructure inventory and graphCA keys, in the signeraudit trail and exportslicense check, offline database, event log, signer: all on hosts you run, in the region you choose nothing leaves unless you send it outside the authorities you enroll with
The only outbound conversations are the ones you configure: authorities, DNS providers, deployment targets and the integrations you turn on.

What a hosted service learns

A hosted certificate lifecycle service sees the inventory by definition, because that is the product. Depending on the design it may also generate or store private keys, hold the credentials that let it deploy certificates into your load balancers and clouds, and keep the audit trail of your operations in its own systems, in its own jurisdiction. None of that is wrong. It is a transfer, and transfers are the thing data-residency rules regulate: under the European regime, personal data may only leave the region under specific conditions.1 The service map in a certificate inventory is not personal data, but the audit trail of who did what is, and the credentials that reach into your infrastructure are the most sensitive operational data you have.

What self-hosting has to guarantee

Running the software yourself is only an improvement if the software behaves like a guest in your house. The guarantees to ask for:

  1. No phone-home. Including for licensing. trstctl's license is an offline Ed25519-signed document verified by local signature math, with a 30-day grace period at expiry; there is no license server to reach.2
  2. Keys that never leave a process you run. CA private keys in a separate signer with no network listener by default, referenced by handle, never exported to the control plane, let alone to a vendor.3
  3. Outbound connections you can enumerate. The authorities you enroll with, the DNS providers you validate through, the targets you deploy to, the alerting and discovery integrations you turn on, and nothing else. A deployment connector should declare exactly which host it may dial.4
  4. Evidence you hold. The audit trail in your database, exportable as a signed bundle you can verify without the vendor, in write-once storage you control.5
  5. Code you can read. Every claim above is checkable only if the source is available. trstctl's is, under a source-available license, with the commercial edition's features gated by the same offline license.6

The trade

Self-hosting costs you operations: the database, the event log, the backups, the upgrades. What it buys is that the map of your infrastructure, the keys to it, and the record of who touched it stay in the region and the hands you choose. For some estates that trade is optional. For a regulated one, or a service provider answering for many customers' estates at once, it is usually the reason the conversation started.

Sources

  1. European Union, Regulation (EU) 2016/679 (GDPR), Chapter V: transfers of personal data to third countries.
  2. trstctl documentation, Editions: the offline Ed25519-signed license, signature verification, and the 30-day grace period.
  3. trstctl, Signing service design.
  4. trstctl documentation, Deployment connectors: the connector sandbox and the network access each connector declares.
  5. trstctl documentation, Compliance: signed, offline-verifiable evidence export.
  6. trstctl, Licensing: source-available core under the Business Source License, commercial edition features under the offline license.