Secrets + TLS automation

Secrets management software for teams that also own TLS certificates

CertLocker brings secrets, certificate lifecycle management, scoped delivery, endpoint probes, SSH/RDP access, and audit evidence into one operational workflow for DevOps and platform teams.

The problem is not just secret storage

A TLS certificate workflow contains secrets at almost every step: private keys, ACME account keys, DNS provider tokens, deployment credentials, machine tokens, PEM bundles, and service reload permissions.

If those secrets live in one tool and certificate automation lives somewhere else, the team still has to wire ownership, rotation, delivery, reload, verification, and audit together by hand.

CertLocker keeps those pieces connected. A host receives a scoped token. A certificate renews. The new material is delivered. The endpoint is probed. The audit trail shows the chain of events.

One workflow, six controls

Store
Keep PEM material, API keys, deployment credentials, ACME account keys, and environment configs under RBAC and audit.
Issue
Create or renew TLS certificates through ACME and lifecycle workflows instead of one-off scripts.
Deliver
Let each host or automation job pull only the certificate or secret it is allowed to use.
Reload
Connect certificate delivery to the service action that makes the new material live.
Verify
Probe the endpoint and record what production is actually serving after renewal.
Audit
Tie secret reads, certificate changes, token use, host access, and probe results into evidence.

Built for mixed infrastructure

Most teams do not run one clean platform. They run cloud, Kubernetes, HAProxy, IIS, Nginx, Apache, old VMs, internal portals, supplier systems, branch networks, and deployment scripts. CertLocker is built for that mess.

Secrets management

Store passwords, API keys, private keys, PEM files, config values, and deployment credentials with RBAC, version history, and audit logs.

Secrets feature

Certificate lifecycle

Track TLS certificates from issuance through renewal, delivery, expiry, ownership, endpoint probes, and audit evidence.

Lifecycle feature

Scoped access

Give hosts, CI jobs, and agents limited tokens for exactly the secret, certificate, or access workflow they need.

Access feature

What this replaces

A lot of teams currently hold this together with a vault, a certificate spreadsheet, a certbot cron job, a few Ansible tasks, GitHub Actions secrets, manual HAProxy reloads, a monitoring check, and a Slack thread when something expires.

CertLocker does not remove every specialized tool. It gives the platform team a control plane for the parts that need to agree: credentials, certificates, delivery, access, probes, and evidence.

A useful evaluation target

Bring one expiring public certificate, one internal certificate, one deployment secret, one SSH or RDP access workflow, and one audit question. If the platform can handle those together, you are testing the real problem.

Test secrets and TLS automation together

Bring your certificate, secret and infrastructure access workflows to a hosted walkthrough with our engineers. We will help plan the next operational step.