How is CertKit different from Certbot and free ACME clients?
Certbot runs on each server and renews that one server. You own a script, a job, and the
restart logic on every machine, and nothing covers appliances that can't run ACME.
CertKit issues every certificate from one account and deploys it out to your servers and
appliances, so there is one place to see what is valid and what is not.
See the architecture
Do I have to switch certificate authorities?
No. CertKit works with Let's Encrypt, your current CA, or any ACME-compatible authority,
and you are never locked in. Most teams move to free Let's Encrypt certificates once
renewal is automated, but you don't have to.
How issuance works
Will it work with my servers and appliances?
The CertKit Agent runs on Windows, Linux, and Docker, and pushes certificates into
appliances like F5, Palo Alto, Citrix, and Cisco. You set the format and location each
system needs, and CertKit keeps them current.
See deployment integrations
What access does CertKit need to my DNS?
One CNAME record, set once. You point _acme-challenge at CertKit so we can
validate certificates, with no DNS API credentials handed over. Your credentials stay with
you, and the worst case is a failed challenge, not a hijacked domain.
Why no DNS API
How does the free trial work?
Every paid plan starts with a 90-day free trial, no credit card required. That is long
enough to watch your certificates renew on their own and know the system fits your
infrastructure. If you are not ready at the end, your account moves to the free Community
plan.
See pricing