Self-hosting
Running certificate infrastructure on hosts you control: what stays inside, what needs a path out, and what you can verify without trusting anyone's servers.
Self-hosted PKI and data residency
A certificate inventory is a map of your infrastructure, and the keys behind it are your infrastructure's identity. Where that data lives is a security decision and, in many places, a legal one. What leaves your network when certificate management is someone else's service, and what self-hosting has to guarantee to be worth it.
Proving a renewal happened
An auditor does not want to hear that renewals are automated. They want the record: who asked, who approved, what was issued, where it went, when it was verified, and proof the record has not been edited. What that evidence looks like when it is the system's own state.
A private CA in an afternoon
The certificates the public web cannot issue, for internal names, private addresses, client authentication and offline networks, need an authority you run. The tree, the ceremony, the constraints, and the one step that takes a quarter rather than an afternoon.
What an MSP does with 300 customers' certificates
For a managed service provider the 47-day schedule is not a chore, it is a capacity problem: a book of business becomes tens of thousands of renewals a week. What one control plane for many customers has to guarantee, and the isolation you can prove rather than promise.
Why the signer is a separate process
Automation has to sign certificates all day. It should never hold the keys. How trstctl draws that line, what the line guarantees, and what it does not, with links to the code.