Built for Actalis
Actalis is on the issuer list in every CertKit account. Add your ACME credentials once. No scripting required.
Actalis is an Italian certificate authority and a qualified trust service provider, which is why it turns up on shortlists where jurisdiction matters: European organizations, public sector buyers, and anyone whose procurement asks where the trust service is established. It supports ACME with External Account Binding, so issuance automates cleanly.
Deployment does not. The certificate still has to reach every server and appliance that presents it, in that platform's format, and be replaced again on a cycle that keeps getting shorter. CertKit holds your Actalis EAB credentials, renews on schedule, and the CertKit Agent installs each renewal and confirms it is live.
Actalis is on the issuer list in every CertKit account. Add your ACME credentials once. No scripting required.
CertKit gives Actalis customers one place to issue, renew, and deploy every certificate. Connect your Actalis ACME account once, and CertKit renews each certificate on schedule.
The CertKit Agent installs each renewal on servers, firewalls, load balancers, and cloud services, and only makes outbound connections. Then CertKit checks every endpoint to confirm it is serving the new certificate.
If you chose an EU trust service provider deliberately, the next question your own procurement will ask is where everything else sits. A certificate authority established in Italy does not help much if the automation around it holds your private keys somewhere you cannot point to on a map.
CertKit issues and renews centrally, and private keys can stay on infrastructure you operate. The CertKit Keystore, an optional component available on Enterprise plans, holds the keys on your own systems, so what leaves your estate is the certificate request and what comes back is the signed certificate. The agent is source-available, so the code handling keys on your servers can be read rather than trusted.
That distinction is worth getting straight early, because it is the one an auditor returns to. Actalis answers who vouches for the certificate. Where the key material lives and who can reach it is a separate question with a separate answer, and both need one.
The do-it-yourself version, once you have EAB credentials:
The second and sixth items are the ones that matter most here: key material placed by accident, and a compliance story that only holds up if the deployment record does too.
At 47 days, renewal has to run itself — and prove that it did. Here's how CertKit does both for Actalis.
Actalis CertKit Your systems
┌──────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ │ │ │ │ │
│ ACME ◄─────────── EAB creds │ │ ┌─────────────┐ │
│ │ │ (stored once) │ │ │CertKit Agent│ │
│ │ issues│ │ │ │ └──────┬──────┘ │
│ ▼ │ │ Track expiry, │ │ │ │
│ Certificate ───►│ renew early │ │ ▼ │
│ │ │ │ │ │ nginx [x] │
│ │ │ ▼ │ │ Apache [x] │
│ │ │ Deploy ───────────►│ appliances [x] │
└──────────────┘ └─────────────────┘ └──────────────────┘
EU trust one CNAME deployed and
service provider delegation verified
Validation runs through a single delegated CNAME, so renewals never require another DNS change and CertKit never holds credentials for your DNS provider.
Ever since the news of the Certificate expiration dates being compressed down to 47 days we have been looking for an MSP friendly solution, CertKit were the clear winners as their platform is easy to use, MSP friendly & cost effective. We’ve been really impressed with the team from a technical support perspective as they’re super quick to respond and we’ve never had a certificate we couldn’t provision!
Andrew Charlesworth, Technical Director, NCS
When an organization picks an EU trust service provider, the reason is usually about where the issuing entity is established and which supervisory regime it answers to. That is a property of the certificate authority. It is not a property of the software that requests certificates, and conflating the two produces odd procurement conversations.
Worth separating clearly: the certificate authority is what your compliance position rests on, and the automation layer is what decides whether renewals happen reliably. They are different jobs with different requirements, and neither one substitutes for the other.
CertKit keeps them separate. Actalis signs the certificates and anchors the compliance story; CertKit makes sure every renewal lands where it should, on time.
Most estates end up with more than one CA, often for exactly this kind of reason. CertKit issues from Actalis alongside GlobalSign, Sectigo, DigiCert, and Let's Encrypt, and from a private CA for internal hostnames and mTLS client certificates. Monitoring spans every issuer from one inventory.
Free 30-day trial. No credit card required. Direct access to our engineering team to get you set up.