Automate your internal certificates using your existing ADCS PKI.
Certeasy exposes your ADCS as a
standard ACME server inside your own network.
You install Certeasy on an internal server in front of ADCS, then point
your ACME clients (like certbot) to
https://acme.your-domain.local/directory
or any internal URL you choose.
Certeasy does not add a new PKI: it automates the one you already have.
The problem today
In most organizations, ADCS issues certificates for Windows machines… but almost never for Linux servers, proxies, or internal appliances.
Teams want a Let’s Encrypt–style workflow for internal certificates: ACME requests, automated renewals, centralized visibility.
Certeasy: ACME on top of ADCS
Certeasy is a full ACME server that communicates directly with your ADCS. You continue using your internal PKI, templates, and policies — but through standard ACME clients.
Sovereignty & full control of your certificates
Certeasy is designed for organizations that want to automate their internal certificates without relying on any external cloud service. Everything runs inside your infrastructure, under your policies and your PKI.