CertLocker

Securely manage TLS certificates, secrets, and infrastructure access through AI agents using MCP.

Hosted MCP Server

npx add-mcp 'https://trust.certlocker.io/rest/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Certificates, secrets, AI agents and access for real infrastructure

Get your certificates, secrets and AI agents under control today.

Renew, deploy and check certificates, secrets and scoped AI agent access across Windows and Linux. Built for DevOps and infrastructure teams.

Trust Platform — on-prem, as a service, or as a managed service.

There is no charge to get started with hosted CertLocker. We agree the scope, capacity, support and commercial terms with you before any paid service begins. See the services page for the available paths.

Keep records together Certs, keys, PEMs, secrets

Control the workflow ACME, tokens, hosts, AI agents

Check the result Probes, RBAC, audit trail

Product overview

CertLocker in 40 seconds

Auto playing

Your browser does not support the video tag.

Certificates, secrets, scoped access, probes, and audit in one workflow.

A quick walkthrough for first-time visitors who need to see how the pieces fit together.

Get started

CertLocker is security infrastructure for developers and AI agents. Powered by the Trust Platform, it brings certificate lifecycle management, secrets, hosts, scoped AI agent access and endpoint checks into one control plane you can run on-prem, as a service, or as a managed service. Teams issue and renew through ACME, use Automations to deliver certificate material over standard SSH/SFTP without a CertLocker target agent, check what production serves, and review access and audit history across Windows, Linux and mixed infrastructure.

Trust Platform

A unified control plane deployed on-prem, as a service, or as a managed service.

Delivery needs credentials, a route to the host and permission to make the change. Explore how ACME, tokens, hosts and AI agents connect to the same records and access controls.

Why it matters

The risk is not just an expired certificate.

An expired certificate is the visible failure. Unscoped AI agent credentials are the quieter one. The business risk is fragmented trust: cryptographic material, admin paths, machine tokens, and agent credentials living in different tools until something breaks or someone asks for proof.

Operations lose time

Teams spend the first part of an incident finding owners, files, endpoints, keys, and old deployment scripts.

Access outlives the job

SSH keys, RDP paths, supplier access, and machine tokens keep working long after the original task is finished.

Executives get unclear answers

When asked what changed, who had access, or what production served, the answer often requires manual archaeology.

Technical teams need credibility

CertLocker keeps the detail engineers expect: artefact custody, scoped credentials, real endpoint checks, RBAC, version history, and audit events.

What changed

Certificate expiry is only the visible failure.

The deeper problem is a missing control plane: certs in one tool, keys and PEMs in another, SSH keys on laptops, RDP handled separately, secrets in scattered stores, AI agents asking for credentials, and audit evidence stitched together after the fact.

Ops teams need live truth

Inventory is not enough. CertLocker checks what endpoints actually serve, which tokens exist, and which hosts are in scope.

Security teams need scope

Machines, users, and sessions should only get the artefact, secret, or host access they need.

Leaders need platform clarity

CertLocker is not an SSL dashboard. It is the unified control plane for cryptographic artefacts, access, probes, and audit evidence.

Auditors need evidence

Every artefact change, token, bastion session, and access event belongs in one reviewable trail.

Review SOC 2 evidence → ISO 27001 → Operator Trust →

Control plane

One workflow for artefacts, access, AI agents, and proof.

Start with the gateway causing pain: ACME and certificate lifecycle, secrets, SSH/RDP access, endpoint verification, scoped tokens, or AI-agent credentials. Use the same RBAC, audit, and scoping model across them.

CertLocker certificate inventory and expiry status

Artefact lifecycle & ACME

Issue, renew, rotate, deliver, and verify TLS certificates and related cryptographic material across HAProxy, Nginx, IIS, OpenVPN, MT4/MT5, internal services, and ACME clients — including short-lived and PQ-ready profile paths.

  • Scoped certificate tokens for machine pull
  • ACME profiles for classical, short-lived, and future MTC/PQC shapes
  • Live endpoint probes that recognise ML-DSA and MTC material Explore certificate lifecycle →

CertLocker private secrets management

Secrets & artefact custody

Keep PEM material, private keys, credentials, configs, and operational secrets under the same control model as certificates - not a separate vault workflow.

CertLocker bastion environments and host access

Hosts, tokens & agents

Replace long-lived shared SSH keys with token-scoped host access, and let MCP agents request artefacts through the plane instead of env files.

  • Time-limited SSH, VNC, and RDP paths
  • Tokens restricted by protocol, IP, 2FA, and group
  • Access logs for incident review and compliance

Integrations through Automations

Fit the automation to your infrastructure.

Automations are saved deployment procedures. They deliver the certificate and run your service’s installation and reload commands over standard SSH/SFTP. Your team controls the steps, with scoped access and execution results in CertLocker.

There is no CertLocker deployment agent to roll out on the target. Linux uses its normal SSH service; IIS uses Windows OpenSSH Server and PowerShell. Configure the access route and permissions, then verify what the live endpoint serves.

No CertLocker deployment agents to install on your servers. → Explore integrations and Automations →

How CertLocker works

Centralize custody. Scope every gateway. Verify production.

CertLocker gives teams a practical trust operating model without forcing every server, load balancer, Windows box, vendor workflow, or admin path into a new custom agent.

View All Features

1

Bring cryptographic artefacts into one store

Certificates, keys, PEMs, secrets, hosts, tokens, channels, and teams live in one governed product surface.

2

Issue scoped credentials instead of broad access

Machine tokens, ACME clients, host sessions, and agents get narrow permissions that can be rotated or revoked.

3

Deliver and verify where infrastructure runs

Servers keep using familiar ACME and SSH paths while CertLocker records delivery, endpoint checks, and access events.

CertLocker audit log with certificate, secret, token, host, and probe events

Audit evidence

Answer access and artefact questions without rebuilding the timeline.

When something changes, CertLocker records the event close to the workflow: artefact issuance, token updates, ACME activity, secret access, host import, bastion access, and endpoint verification.

Who had access?

Review user, token, role, and group activity from one place.

What was served?

Probe production endpoints and compare live TLS against intended state.

What changed?

Trace artefact, secret, token, and host workflow changes over time.

What can be revoked?

Remove token or session access without chasing keys across machines.

Where it fits

Built for teams that own production infrastructure.

CertLocker is built around infrastructure buyers who need a unified trust control plane - reliability, access control, and evidence - before compliance or outages force the issue.

DevOps and platform teams

Stop spreading artefact, secret, and access work across shell scripts, spreadsheets, cloud consoles, and chat messages.

Read use case →

Financial infrastructure

Run trust workflows for trading systems, portals, and regulated infrastructure with clear evidence.

Read use case →

Zero trust SSH

Give operators fast access without leaving long-lived keys scattered across laptops and servers.

Read use case →

Bare metal infrastructure

Certificates, secrets, scoped access and AI agent credentials for estates that are not clean cloud-only.

Read use case →

Start with the records you already have.

Create your account and start with your certificate, secret and AI agent inventory. If you need help with spreadsheets, legacy tools or the next operational step, talk to an expert.