Home / Products / Acmefyer

AcmefyerAgent-based Certificate Manager

SSL certificates that renew themselves.

Acmefyer is an SSL certificate manager for your own network: it obtains SSL/TLS certificates from Let’s Encrypt, ZeroSSL or Google Trust Services, issues its own from a local CA for internal names, renews them in time and rolls them out wherever they are needed. Certificates from an existing internal CA, or the CA itself, come in by import. Installation happens from the inside: an agent on the target system picks up the certificate itself, without PowerShell remoting and without inbound ports.

€299one-time, incl. VAT · 3 years of updates included

One certificate, many services: Acmefyer renews it and the agents install it everywhere.

01LifetimesWhy automation is becoming mandatory

SSL certificate lifetimes are shrinking to 47 days.

The browser vendors Apple, Google, Microsoft and Mozilla and the certificate authorities decided in the CA/Browser Forum to shorten the lifetime of public TLS certificates step by step: from 398 days to 47 days by 2029. Domain validation can then be reused for only 10 days.

At 47 days, every certificate is replaced roughly once a month, on every web server, every mail system and every firewall. That can no longer be done by hand. Acmefyer renews automatically and installs the new certificate via the agent, with no one having to step in.

Source: CA/Browser Forum, Ballot SC-081v3, approved on 11 April 2025.

02FeaturesWhat Acmefyer takes care of

Every ACME challenge, wildcards too

HTTP-01 with a built-in challenge server, DNS-01 for around 190 DNS providers, including wildcard certificates (*.example.com), and TLS-ALPN-01.

Automatic certificate renewal

Scheduling with backoff, a lock per certificate and idempotency. Nothing runs twice, nothing expires.

Rollout via agent

The agent on the target system picks up the certificate itself and installs it locally, without inbound ports.

Secure by default

AES-256-GCM for secrets, Argon2id passwords, AD/LDAP sign-in with roles, optional TOTP and an audit log.

Notifications

Email, Teams, Telegram, PRTG or webhook. With templates, rate limiting and deduplication.

Two interfaces, one core

Web interface in the browser, in German and English, light and dark. Plus a terminal interface right on the server.

Certificates of your own and a local CA

Import certificates from an internal CA, self-signed or purchased ones (PEM, DER, PFX) and deploy them through the same agents and targets. For internal names such as server.company.local Acmefyer creates and manages one or more internal CAs of your own if you wish: a root CA with a name constraint, intermediate CAs per purpose (TLS server and client, S/MIME, code signing) and certificates that Acmefyer renews with a new key and rolls out again by itself. Acmefyer can also take over an existing root or intermediate CA, for example from XCA, OpenSSL or AD CS, together with its key, and your systems then trust it already. Certificates it issued before come in several at once: they appear in the tree below their CA, and from then on Acmefyer renews the server certificates. Certificates of your own CA can be revoked: each CA signs a revocation list (CRL), which the server serves over HTTP and signs anew in good time. If you wish, Acmefyer revokes a replaced certificate once the new one has reached every target. The target “Trust store (CA)” makes your own CA trusted on Windows and Linux agents.

Acmefyer is under continuous development: updates keep adding new features and supported services.

03ViewsThe application with demo data
Acmefyer at a glance (1:34): shorter lifetimes, renewal and rollout via agents without open ports on the servers, then domains, deployments and targets, agents with detected applications, found certificates, notifications and audit log. Watch on YouTube
Dashboard with tiles for all, active, soon-to-expire and failed domains and the agents, below it the health of all certificates and the latest domains.

At a glance: how many certificates are valid, which expire soon, where an error is pending and which agents are online.

04RolloutFrom the inside instead of remote access

Deploy certificates via agent: no holes in the firewall, no PowerShell remoting.

Many tools and scripts push certificates from the outside: via PowerShell remoting, file shares or remote logins. That requires open ports on every target system and administrator credentials stored in one central place.

The Acmefyer agent runs directly on the target system. It opens an encrypted connection to the Acmefyer server itself, picks up the certificate and installs it locally.

This is how certificates get into IIS and other HTTP.sys applications, Exchange, MailStore Server, PRTG, ScriptRunner, the Windows certificate store, NGINX, Apache, Traefik, HAProxy, Tomcat, Gitea, any service that reads PEM files, or custom scripts. In addition, Acmefyer exports PEM and PFX files to the file system or a Windows share, transfers them via SSH, calls webhooks and installs certificates on firewall appliances via REST API, e.g. FortiGate.

For each target you choose who performs the rollout: the server itself or an agent. The server only offers the safe actions, namely export, SSH and webhook. Firewall appliances such as a FortiGate are always served by an agent, for example one in the DMZ right next to the firewall.

Connection
Outbound only, from the agent to the server, via HTTPS with mutual certificate verification (mTLS). No inbound port is needed on the target systems.
Firewall
One rule: agent to the server on port 443 when the web UI has HTTPS with a publicly trusted certificate, otherwise to the agent port (default 8444). No WinRM, no file share, no RDP.
Credentials
The server stores no administrator passwords for the target systems. The agent works with the rights of its local service.
Installed locally
IIS bindings, HTTP.sys bindings, Exchange, MailStore Server, PRTG Network Monitor, ScriptRunner, Gitea, Windows certificate store, Windows and Linux trust stores (your own CA), NGINX, Apache, Traefik (also in a container), HAProxy, Tomcat keystores (PKCS#12/JKS), services such as Postfix or PostgreSQL, custom scripts and the web interface of Spherifyer (connects itself, no agent)
Internal networks
Target systems need no internet access. Only the Acmefyer server talks to the certificate authority.
Detection
The agent finds the applications serving TLS on its system, such as NGINX and Apache sites, Traefik also in Docker containers, HAProxy, IIS, Exchange, MailStore Server, PRTG, ScriptRunner, Keycloak, the enaio gateway, Gitea in a container, mail and database servers or Proxmox, with certificate file and expiry. On Windows also Tomcat, Apache and NGINX bundled by vendors, and every other port that speaks TLS, with the program behind it. Where one fits a certificate, the deployment is one click away. If certbot, acme.sh or a container renews the certificate already, the scan says so. Reverse proxies with many sites are set up in one step, missing domains included: sites sharing a certificate file get one certificate for all their names, and after a renewal the proxy reloads only once. An overview lists every certificate found and which of them Acmefyer does not manage yet. The server can also scan your own network for them read-only, with no agent at all.
Setup
The server generates a setup package per platform (Windows and Linux, x64, ARM64 and 32-bit) with the configuration built in. Or it installs the agent once itself: on Linux via SSH, on Windows via PowerShell remoting, detecting the target's processor. Likewise an agent can be uninstalled from the server without leftovers: service, program, configuration and identity. For PDQ Deploy and other software distribution the package installs itself with the parameter setup and removes itself with uninstall, without prompts and with an exit code.
Example 1 · Internal serversRollout running
INTERNET INTERNAL NETWORK Firewall Let’s Encrypt Certificate authority Acmefyer server obtains and renews ACME outbound Agents connect outbound only (mTLS) WEB01 · IIS Agent installs locally EX01 · Exchange Agent installs locally WEB02 · NGINX Agent installs locally inbound: no open ports

The server obtains the certificate over the internet. The agents on the target systems open a connection to the server themselves and install it locally. Nothing is opened from the outside.

05WorkflowEasy to set up, automated from the start

Certificate rollout: easy to use, usually fully automated from the first step.

Acmefyer takes the legwork off your hands: the agent finds out by itself which applications on a server deliver certificates and where their files are, and Acmefyer suggests the matching deployment. In most environments this automates the certificate rollout 100 % from the first step: issue, install, verify and renew in time, with nobody having to lend a hand afterwards.

  1. 01

    Install the agent

    Run the setup package or install it from the server. The agent detects the applications serving TLS on its system.

  2. 02

    Accept the suggestions

    One click per application, whole proxy servers with all their sites in one step. Missing domains are added along the way.

  3. 03

    Issue and roll out

    Acmefyer obtains the certificate, the agents install it and check that it is served.

  4. 04

    Renew

    In the renewal window everything repeats automatically, with notification.

How far this goes the first time naturally depends on your infrastructure and the applications in place. What Acmefyer knows, such as IIS, Exchange, NGINX, Apache, Traefik, HAProxy or Tomcat, it sets up with one click after the scan. A FortiGate needs API access once, software of your own a script or the generic service deployment. And if certbot or another tool renews a certificate already, it is switched off first. The scan points this out.

06Use casesTypical tasks, step by step

Renew the Exchange certificate automatically

Import, enable for IIS, IMAP and POP, verify and roll back if needed. In a DAG one server at a time.

Read the guide

Renew and bind the IIS certificate

Let’s Encrypt for IIS: import into the Windows certificate store and bind to the site, without remote access.

Read the guide

Wildcard certificate with Let’s Encrypt

*.example.com via DNS-01 for around 190 DNS providers: issued once, installed on every server.

Read the guide

Renew free SSL certificates automatically

Let’s Encrypt, ZeroSSL and Google Trust Services issue for free via ACME. Acmefyer takes care of the rest.

Read the guide

Let’s Encrypt for internal servers

Via DNS-01 without an open port 80. The internal servers need neither inbound ports nor internet access.

Read the guide

47-day certificates: dates and consequences

200 days since 2026, 100 days from 2027, 47 days from 2029. What was decided and how the replacement runs by itself.

Read the guide

Renew the FortiGate certificate automatically

Import via REST API and switch SSL VPN, admin interface, authentication portal and VIPs.

Read the guide

NGINX and Apache on Linux

One agent per Linux server writes the PEM files and reloads the web server, for all sites of a reverse proxy in one step.

Read the guide

Tomcat certificate with its keystore

Write the Java keystore as PKCS#12 or JKS, with the connector’s password and alias, and restart Tomcat.

Read the guide

Renew the PRTG certificate

Write prtg.crt, prtg.key and root.pem the way PRTG requires them, restart the core server, roll back on errors.

Read the guide

Renew the MailStore certificate

Enter it in MailStore Server, restart the service and verify. If MailStore does not start, the agent undoes everything.

Read the guide

Find expiring certificates in your network

Agent scan and network scan show every certificate with issuer, expiry date and every place it was found.

Read the guide

Private CA with revocation list

Issue, renew and deploy certificates for server.company.local and revoke them through a revocation list (CRL).

Read the guide
07Technical detailsOperation and requirements
Platforms
Windows (setup or executable) and Linux, as an executable and as a .deb and .rpm package
Programs
acmefyer-server for the service, web and terminal interface · acmefyer-agent for the target systems
Data storage
Embedded database, secrets encrypted with AES-256-GCM
Sign-in
Local admin (password set in the first-time setup in the browser on Windows, initial password on Linux), AD/LDAP with roles by group or OU, optional TOTP
Default address
127.0.0.1:443, freely configurable
Network
Server: outbound to the certificate authority (and, for DNS-01, to the DNS provider), and to www.wedigo.net for license activation, also through a proxy (taken over from the Windows settings or set in the web interface and the console). With revocation lists of the local CA also inbound over HTTP (port 80 by default) for the clients in your own network. Agents: outbound to the server only.
Updates
Automatic self-update from signed releases, optionally within a maintenance window. If a new version does not start cleanly, the service returns to the previous version on its own. Can be switched off or set to notify only.
08ComparisonAcmefyer and other certificate management tools

Certificate management between an ACME client and an enterprise platform.

There are roughly four ways to manage SSL certificates: an ACME client on every server, custom scripts with remote access, a certificate lifecycle management platform, or monitoring that warns before expiry.

Acmefyer combines the central certificate management of a platform with the simple operation of an ACME client: one server for all certificates, agents on the target systems, bought once.

ACME client per server
For example Certbot, win-acme, Certify The Web or Posh-ACME. They renew certificates on the server they are installed on. Acmefyer manages all certificates in one place and rolls them out via agent to many systems, with shared notifications and an audit log.
Custom scripts
PowerShell via WinRM or file shares, Certbot hooks via SSH. That requires open ports on the target systems and administrator passwords on the script server. With Acmefyer the agents connect outbound only, see Rollout.
Certificate lifecycle management platforms
For example Venafi (CyberArk), Keyfactor, AppViewX or Sectigo Certificate Manager, with features for private PKI, many certificate authorities and company-wide policies. Acmefyer focuses on certificates via ACME, also takes over imported certificates and brings a simple local CA for internal names, runs as a single program on Windows and Linux and is bought once.
Expiry monitoring
For example certificate checks in PRTG, Zabbix or Nagios. They warn before expiry, but a person still has to replace the certificate. Acmefyer renews and replaces the certificate itself and reports the result, also to PRTG if you like.
09LicenseOne-time purchase€299

Acmefyer

  • Unlimited certificates, domains and agents
  • 3 years of updates, fixes and support included, new major versions too
  • Then €99 per year if you like. Without an extension every version released until then stays usable without end
  • Continuous development: updates keep adding new features and supported services
  • License key by email right away, activated online
  • 14-day money-back guarantee
  • Free for non-profit and volunteer associations and institutions: full license with 3 years of updates, on request with proof through the contact form, extended free of charge
  • Try it free without a key: 1 domain with 1 subdomain (or wildcard) and 1 agent, all features except the internal CA
€299 one-time, incl. VAT, per installation All prices and terms
€0 free version, no license key: 1 domain with 1 subdomain (or wildcard) and 1 agent, all features except the internal CA Download the setup for Windows Download for Linux (amd64) Or just the program file for Windows, without the setup. Version 1.0.13 · 2026-11-21 · Installation

SHA-256 checksums

Windows setup: d0bebe4802652c369d15f2747bca77f84ed700601445d6dba9f35cccd01223bc

Windows program file: a68f109dab38582b6ca12364776d7688a8a79cc8cf69cb5ed3536455396567d6

Linux: 35e69b32c73bf78e19e2b02bb35407597bb452b4a586c053fadd1d19da219b91

The setup installs the Acmefyer server as a service, brings the agents for all platforms and leads through the first-time setup in the browser. A license key lifts the limits later, without reinstalling.
10FAQFrequently asked questions about Acmefyer

What is Acmefyer?

An SSL certificate manager for your own network. The Acmefyer server obtains SSL/TLS certificates via ACME from Let’s Encrypt or another certificate authority, renews them in time and distributes them. Agents on the target systems install them there, for example in IIS, Exchange, NGINX or a FortiGate.

How much effort is the setup?

Little. Install the server, roll out agents with the setup package or from the server, done: the agent detects the applications serving TLS on its system, and Acmefyer suggests the matching deployments, for whole proxy servers with all their sites in one step. In most cases this automates the certificate rollout 100 % right away. How far exactly depends on infrastructure and applications: appliances such as a FortiGate need API access once, software of your own a script.

Are the SSL certificates free?

Yes. Let’s Encrypt, ZeroSSL and Google Trust Services issue certificates via ACME for free, but ZeroSSL and Google Trust require an account. Acmefyer itself is free for one domain with one subdomain (or a wildcard certificate) and one agent, with all features except the internal CA. For more, the license costs €299 once, with 3 years of updates. More: renew free SSL certificates automatically.

What happens after the 3 years of updates?

Acmefyer keeps running without end, with every version released until then. New versions, fixes and support come with an extension for €99 per year. The extension continues from the end of the previous period, also if you extend later. As certificate authorities and browsers keep changing their rules (shorter lifetimes, new ACME features), we recommend not letting the update period run out.

Is Acmefyer free for associations and non-profit organizations?

Yes. Non-profit associations, foundations and institutions as well as associations run mainly by volunteers get the full license free of charge, with unlimited domains and agents, the internal CA and 3 years of updates. Write to us through the contact form and attach proof, such as your tax exemption notice or an extract from the register of associations. After 3 years we extend free of charge on renewed proof. The conditions are in the license terms.

Will more features and services be added?

Yes. Acmefyer is under continuous development, and updates keep adding new features and supported services, such as more applications the agent detects and new rollout targets. Until then any other application can be connected with a script or a target type of your own.

What is ACME?

ACME (Automatic Certificate Management Environment, RFC 8555) is the protocol certificate authorities such as Let’s Encrypt use to issue domain certificates automatically. The ACME client proves through a challenge that it controls the domain: with a file on port 80 (HTTP-01), a DNS record (DNS-01) or over port 443 (TLS-ALPN-01). Acmefyer supports all three.

How does Acmefyer renew certificates automatically?

The server checks every hour which certificates expire soon and renews them about 30 days ahead, at a randomized moment for each certificate. If that fails, it tries again later with growing intervals. It then installs the new certificate on every target and reports the result by email, Teams, Telegram, PRTG or webhook.

Can Acmefyer issue wildcard certificates?

Yes, via DNS-01. Acmefyer creates the validation record at your DNS provider itself, and around 190 providers are supported. The wildcard certificate also contains the domain itself (example.com). See wildcard certificate with Let’s Encrypt.

How does the certificate get into Exchange and IIS?

An agent on the Exchange or IIS server picks up the certificate, imports it into the Windows certificate store, binds it to the IIS site or enables it in Exchange for IIS, IMAP and POP, and checks that the port serves the new certificate. Details: Exchange certificate and IIS certificate.

Why will certificates soon have to be replaced every month?

The CA/Browser Forum is shortening the lifetime of public TLS certificates in stages: at most 200 days since 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029. Every certificate is then replaced roughly once a month, on every server. That is hardly feasible by hand.

Can Acmefyer also deploy certificates from an internal CA or purchased ones?

Yes. You import certificates from an internal CA such as Active Directory Certificate Services, self-signed or purchased ones as PEM, DER or PFX and give them targets like any other certificate. Acmefyer warns before they expire. Once your CA has renewed the certificate, a new file replaces it on all targets. The CA certificate itself goes into the Windows and Linux trust stores with the target “Trust store (CA)”. If Acmefyer should issue and renew by itself, take your CA over into the local CA together with its private key. The root CA can stay offline if you import only the intermediate CA with its key. Certificates your CA issued before then come in several at once. Acmefyer assigns them to their CA and from then on renews the server certificates itself.

Are there certificates for internal names such as server.company.local?

Yes, from Acmefyer’s local CA. Public certificate authorities issue nothing for such names. Acmefyer creates a root CA, restricted to your internal domains if you like, plus intermediate CAs per purpose, issues the certificates and renews them itself. You roll out the root CA by Group Policy, MDM or with the target “Trust store (CA)” on the agents. The local CA needs a license. See certificates for internal servers.

Can I revoke certificates of the local CA?

Yes. Every CA in Acmefyer signs a revocation list (CRL), and the server serves it over HTTP, on port 80 by default. New certificates name the address of the list so that clients find it. When you revoke a certificate, you pick the reason and can have it issued anew right away. If you wish, Acmefyer revokes a replaced certificate by itself once the new one has reached every target. Acmefyer signs the lists anew in good time and reports when one cannot be signed or runs out soon. The local CA, revocation and revocation lists included, needs a license.

Do the target systems need open ports or internet access?

No. The agents connect outbound only to the Acmefyer server, via HTTPS with mutual certificate verification. Only the server talks to the certificate authority. Acmefyer needs no PowerShell remoting, file shares or administrator passwords for the target systems.

Does Acmefyer run in the cloud?

No. Acmefyer runs on your own server under Windows or Linux. Externally it only talks to the certificate authority, to your DNS provider for DNS-01, and to www.wedigo.net for license and updates.