Instead of DigiCert Trust Lifecycle Manager
Review your DigiCert Trust Lifecycle Manager spend. Own your certificate operations desk.
We build your version around your services, bring your DigiCert certificate records across and run the agreed system for you. Your certificate authority and deployment tools remain part of the plan.
DigiCert lists Essentials at US$40 per seat on a 12-month auto-renewing subscription, with a 25-seat minimum. Advanced and Premium require a sales quote. Confirm billing terms at checkout.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription covers
Know which part of certificate management you are paying for
DigiCert combines inventory, reporting, certificate issuance and automation. This free version gives you an editable operations record. We scope the connections your business needs before any switch.
A seat for each managed certificate
The Essentials pricing page counts each managed certificate as a seat and displays a US$40 unit price on a 12-month subscription. Your own inventory records are not charged by certificate count.
Inventory and discovery in one plan
Essentials includes cloud discovery, certificate transparency sources and imported records. The free version starts with your exported inventory. New discovery connections are agreed as part of your custom version.
Alerts and reporting
DigiCert includes tags, alerts and custom reporting. Here, your weekly review combines service ownership, expiry, overdue renewals and missing verification evidence in one database you own.
Certificate issuance and automation
Essentials includes issuing and managing DigiCert certificates and supported automation methods. These are real services to account for. We agree how your issuers and deployment tools connect to your version.
Multiple authorities and complex infrastructure
DigiCert positions Advanced for more complex environments and management across certificate authorities. It is quoted privately. Your own operations desk can hold imported records from different authorities without claiming to issue their certificates.
Enterprise connections and support
Premium adds enterprise integrations, migration support for new cryptography and a support agreement. We review the integrations you actually use and scope the operating responsibilities in Omni by Enterprise DNA.
What you own
The service record, the change plan and the evidence
Accountability
An owner for every service
Connect a certificate record to the service it supports and the people responsible for it.
- check Primary and backup service owners
- check Critical services marked for review
- check Endpoint records tied to certificate fingerprints
- check Ownership review dates that appear when overdue
Renewal work
Every instance stays on the list
A renewal starts with a fixed list of recorded endpoints, a replacement certificate and rollback instructions.
- check An owner and due date for the renewal
- check A recorded human approval with its evidence
- check Installation records for each listed endpoint
- check Closure only when every target has current matching verification
Current evidence
A later failure stays visible
A previous passing check does not hide a later failure or an installation that changed the expected certificate.
- check Checks matched to the expected fingerprint
- check Stale checks returned to the attention list
- check Closed renewals flagged when their evidence becomes stale or fails
- check Public certificate validity checked against the limit for its issue date
Your working record
Paperwork that follows your rules
Change the ownership rules, evidence checks and handover documents around your business. The included analysis answers the ten demonstrated questions below.
- check Service certificate registers in your brand
- check Renewal handovers with approval and rollback details
- check Read-only weekly and ownership reports
- check Full record exports and original import columns retained
Make it yours
Design your own DigiCert Trust Lifecycle Manager replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from DigiCert Trust Lifecycle Manager. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your DigiCert Trust Lifecycle Manager data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Certificate Operations for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Certificate Operations for Claude Code
Connected to your own database
Which services need a certificate review now?
LEGACY
- Service
- INTERNAL
- Health
- expired
- Not_after
- 2026-10-25T22:43:29.875Z
PORTAL-A
- Service
- PORTAL
- Owner
- Mere
- Health
- verified
- Not_after
- 2026-11-07T22:43:29.875Z
PORTAL-B
- Service
- PORTAL
- Owner
- Mere
- Health
- stale-check
- Not_after
- 2026-11-07T22:43:29.875Z
| Code | Service | Owner | Health | Not_after |
|---|---|---|---|---|
| LEGACY | INTERNAL | expired | 2026-10-25T22:43:29.875Z | |
| PORTAL-A | PORTAL | Mere | verified | 2026-11-07T22:43:29.875Z |
| PORTAL-B | PORTAL | Mere | stale-check | 2026-11-07T22:43:29.875Z |
Ask it anything
Ten questions this working version answers
These answers come from the included demonstration records. DigiCert also offers custom reporting and natural-language analysis. Your version lets us change the records and review rules together.
Switching
How to switch from DigiCert Trust Lifecycle Manager
A move usually involves exporting a custom certificate report, mapping and checking its records, then testing the replacement workflow alongside DigiCert before you switch over.
- 1
Export a custom certificate report
Export a custom certificate report with the records you want to move, in a format your account allows, usually CSV or Excel. Check with DigiCert Trust Lifecycle Manager if you are unsure what your account can export. Include the certificate identity and validity information used to track each record. The report does not show where a certificate is installed or prove an approval.
- 2
Load the records with a test run
Have the records loaded into the database, and start with a test run before saving anything. The import reads certificate identity and validity fields, keeps the original columns, and combines rows sharing a fingerprint into one certificate. Repeating an identical import changes nothing. Conflicting metadata stops the import as a transaction, so review the test results before proceeding.
- 3
Review flagged records
Review every issue the import flags before relying on the records. Check trust scope and ownership after import, then add primary and backup owners and endpoint bindings explicitly. A certificate export does not establish where a certificate is installed, which service owns it, or whether a renewal was approved. Resolve mismatches against your service records and leave uncertain mappings open for review.
- 4
Run both systems side by side
Keep DigiCert Trust Lifecycle Manager running while you use the replacement workflow alongside it for a short period. Compare the inventory, ownership, renewal planning and supplied evidence with your expected records and process. Keep DigiCert issuance, discovery and deployment automation running if you rely on them. The replacement manages certificate operations records, but does not issue certificates, scan systems or install certificates.
- 5
Switch off DigiCert when ready
Switch off DigiCert Trust Lifecycle Manager only after the replacement workflow is tested and you have confirmed which DigiCert services remain in use. Keep the certificate authority, discovery and deployment services you still need. The replacement manages inventory, ownership, renewal planning and supplied evidence, but it does not handle keys or prove live service health.
Where the real effort goes
The import itself is only part of the move. Most of the work is mapping your fields, service owners, endpoint bindings, trust scope and review rules, then deciding how much history to bring and reconciling conflicts. Exported certificate rows do not supply deployment evidence or prove approvals. If you have Enterprise DNA run it, Enterprise DNA maps the exports and reconciles the records as part of the build.
Not ready for a call?
Get your DigiCert Trust Lifecycle Manager switch plan by email
We will send you the step-by-step plan for moving your business off DigiCert Trust Lifecycle Manager, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your DigiCert Trust Lifecycle Manager switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Do it yourself, customise it, or have us run it
Open source
Do it yourself
Free, open source
- 1 Clone the repo and run npm install
- 2 Run npm run demo and review the fictional records
- 3 Open the folder in Claude Code, Codex, OpenCode or Cursor
- 4 Preview your DigiCert CSV import, reconcile the records and add your service owners
Built around your business
We customise it
An agreed setup fee
- check Your fields, service owners and evidence rules
- check Your DigiCert records mapped and reconciled
- check A web front end or different stack if agreed
- check Your issuer and deployment connections scoped before switching
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed and operated through Omni by Enterprise DNA
- check Your agreed systems connected with clear responsibilities
- check Your reports and review rules maintained as the business changes
- check Backups, operating checks and agreed support managed for you
Questions
Instead of DigiCert Trust Lifecycle Manager, answered
Does the free version replace everything in DigiCert Trust Lifecycle Manager? expand_more
It replaces the certificate operations record: inventory, ownership, renewal planning and supplied evidence. DigiCert also issues certificates, discovers assets and automates deployment. We review those dependencies and build the agreed connections into your version. Keep the services you need running until the replacement workflow is tested.
Can we bring our existing certificate records? expand_more
Yes. DigiCert can export a custom certificate report. The free version imports its certificate identity and validity fields, keeps the original columns and offers a test run before saving. Repeated fingerprints are reconciled. Owners and endpoint bindings are added explicitly because an exported certificate alone does not prove where it is installed.
Will it tell us that an installation really worked? expand_more
It records the result and evidence supplied by your operator. A renewal stays open until every listed endpoint has an installation record and a current passing check for the expected certificate. It does not scan your systems or prove live service health. We scope live checks and notifications into the managed version when required.
How does the price compare? expand_more
DigiCert displays US$40 per Essentials seat on a 12-month auto-renewing subscription with a 25-seat minimum. Advanced and Premium are quoted privately. Confirm the applicable term and currency with DigiCert. The free version has no licence fee. Enterprise DNA charges an agreed setup fee, then a retainer for the managed service. Certificate issuance and infrastructure costs remain part of the agreed operating plan.
Who controls our records and changes? expand_more
You own the database and can export your records. The free version records changes and supplied actor names, but that history is not tamper-proof or an authenticated approval signature. Enterprise DNA agrees your access, backup, retention and approval requirements when building your version. Private keys stay in your existing secure systems.
Bring your certificate bill and one renewal handover
Book 30 minutes with Sam. We will look at the service owners, exports and automation you use, agree what your version needs and scope the setup and ongoing operation.
Certificate Operations for Claude Code is free and open source, published by Enterprise DNA.
Done paying for DigiCert Trust Lifecycle Manager?
Get your version built