
Want to see what the Agent finds in your environment?
Register for a free trial or book a presentation with our team

The Certiligent Agent covers exactly this step. It runs on your servers, finds the certificates that are already there, maps each one to the service that uses it, and, once you approve, puts it on automated renewal.
Think of a facility manager who takes over a large office building. The service contract is signed and the maintenance schedule is ready. Then the previous tenant hands over a box of unlabelled keys. Nobody is quite sure which door each key opens, and some doors are not on the floor plan at all. The schedule is useless until someone walks the building, door by door.
TLS certificates work the same way. The renewal engine is rarely the issue. The challenge is the walk through the building.
Most certificate-related outages are not due to the certificates a team tracks. They come from the ones nobody tracks. A typical environment holds certificates that sit in one or more of these blind spots:
Outside the inventory. Issued years ago, never added to the spreadsheet or CMDB.
Without an owner. The person who installed them changed teams or left the company.
Embedded in scripts and applications. Bundled into a config file or an application package, invisible from the outside.
On network and security equipment. Load balancers, VPN gateways and appliances that rarely appear in a server list.
Issued without documentation. Requested in a hurry, installed, and forgotten.
Copied across servers. One wildcard certificate, deployed to many machines, each copy expiring on the same day.
Spreadsheets and CMDBs describe the environment as planned. Production is the environment as it actually is. The gap between the two is where the risk sits, and it is also what stands between you and automated renewal.
Putting one existing certificate under automated renewal is a small integration project. Done by hand, it usually looks like this:
None of these steps is hard on its own. The problem is repetition. An organization with 100 certificates faces 100 of these small projects, spread across different teams, operating systems and maintenance windows. Each one competes with day-to-day work, so onboarding drags on for months.
Wildcard certificates add a twist. One certificate may protect dozens of servers. Renewing it is easy; making sure the new copy lands on every server that uses it is not. Miss one machine and that service fails on the old expiry date, even though the certificate was "renewed".
Until onboarding is finished, the automation platform manages only part of the estate. The rest still depends on calendars, reminders and whoever remembers.
The Certiligent Agent is a component installed on your own servers. It takes over the walk through the building: it discovers the certificates already in place and brings them under automated renewal, without a separate ACME client on every machine.
The process runs in four steps:
Two capabilities matter most for onboarding at scale:
The result is that onboarding stops being 100 separate projects. It becomes one installation per server, followed by a review and an approval.
Any software that touches production certificates must earn the security team's trust first. The whole purpose of the Certiligent Agent is to pass that review:
Minimal server privileges. It runs with only the permissions it needs to do its job.
No inbound ports. Nothing new is opened on the server, so the attack surface does not grow.
Digitally signed distribution. The Agent package is signed, so you can verify it has not been tampered with.
Review before execution. Planned actions can be inspected before they run. Your team decides what happens and when.
Installs in minutes. No lengthy deployment project before the first results.
Automation does not mean handing over control. It means the routine work runs on its own, while the decisions stay with your team.
With the Agent in place, the certificate inventory is built from what is actually running, not from what someone remembered to write down.
| Manual onboarding | With the Certiligent Agent | |
| Finding certificates | Server by server, by hand | Automatic discovery on each server |
| Knowing what uses a certificate | Asking around, checking configs | Certificates mapped to servers, applications and services |
| Setting up renewal | ACME client configured per server | No separate ACME client needed |
| After renewal | Manual reloads and restarts | Post-renewal actions run automatically |
| Wildcard certificates | Copied to each server by hand | Distributed to every server that uses them |
| Inventory | Spreadsheet or CMDB, often outdated | Central, live view in Certiligent |
Once certificates are on the platform, Certiligent handles the rest of the lifecycle: monitoring, alerts for upcoming expirations or failed renewals, and an audit trail of every operation for NIS2, DORA or internal audit.
Back to the facility manager. The maintenance contract was never the hard part. The hard part was knowing which key opens which door, and finding the doors that were not on the plan.
The Certiligent Agent does that walk for you. It finds the certificates already in production, tells you where each one is used, and moves them onto automated renewal once you say yes. From then on, renewals happen on schedule, on every server that needs them, without tickets or late-night interventions.

Register for a free trial or book a presentation with our team