aethercert
NewCertificates now last 200 days at most, 47 from 2029What changes

Focus on your own work. We'll keep your certificates running.

aethercert finds, renews and installs the TLS certificates on your Windows and Linux servers automatically. You set it up once. After that, nobody on your team has to remember an expiry date again.

  • Free for up to 2 servers
  • No card required
  • No inbound firewall rules
A coffee roaster inspecting freshly roasted beans under a magnifying lamp.
Your work

You build, ship and make things. Certificates shouldn't be part of the job.

Every company runs on servers now, from the site office to the warehouse to the shop counter. aethercert takes the certificate work off the list, so the people who run your business can keep doing exactly that.

A woman working at a desktop computer in a warmly lit office.
Offices & agenciesYour team works on client projects, not on expiry dates.
A construction worker in a hard hat on the timber frame of a new building.
ConstructionPlan the next project, not the next expiry date.
Two warehouse workers next to a reach truck between high shelving.
WarehousingGoods keep moving while certificates renew in the background.
A regional jet parked at an airport gate, with a pushback tug in front of it.
Travel & transportRunning around the clock. So is renewal.

Installs directly into the systems you already run

  • IIS & Exchange
  • NGINX
  • Docker
  • Kubernetes
  • F5 BIG-IP
  • NetScaler
  • FortiGate
  • PAN-OS
  • Proxmox VE
  • Let's Encrypt
All integrations
Your part, our part

Above the line is what you do. Below it, we take over.

Everything a certificate needs, step by step. Your part is two things at the start. We take care of the rest.

01Set up
02Choose
03Renew
04Install
05Track
You
Run the install command once
Choose which certificates we manage
Nothing to do
Nothing to do
Take a look whenever you like
What you see
The server appears in the dashboard
Every certificate with its expiry date
Status: being renewed
Status: installed
A complete history
From here on, it's our job
What we do
The agent connects, outbound only
The agent finds the certificates on the server
30 days before expiry: new key, new certificate
Installed where it's used, service reloaded
Every step logged, errors with the exact message
Renewal starts 30 days before expiry by default. The old certificate stays in place until the new one is installed.Where your part endsWork aethercert does for youThe step that's easiest to forget
Trust

What happens on your server stays on your server.

The agent does its work where your certificates live. The private key is created there, used there and never sent anywhere, not even to us.

No open ports
Agents only call out over HTTPS. No inbound firewall rule, VPN or public IP address on any server.
No code from the dashboard
Custom scripts must already be on the server. The dashboard can only point at them.
Keeps working without us
Installed certificates keep working if aethercert is unreachable, and 30 days of lead time leave room to catch up.
Hosted in Germany
The application runs on Hetzner in Nuremberg, the database in Frankfurt. Multi-factor sign-in is mandatory.
Security and data handling
Exploded view of one server running aethercertFour layers lifted apart: your server at the bottom, the aethercert agent on it, the private key and the certificate side by side above it, and your service on top. The private key is highlighted because it never leaves the server.
  1. Your serviceIIS · NGINX · EXCHANGE
  2. CertificateRENEWED 30 DAYS AHEAD
  3. Private keyCREATED HERE, NEVER SENT
  4. aethercert agentOUTBOUND HTTPS ONLY
  5. Your serverWINDOWS OR LINUX
Why now

Soon every certificate needs someone eight times a year.

The CA/Browser Forum is cutting the lifetime of public TLS certificates in stages. Each step roughly doubles how often someone has to renew, install and check every single one.

  1. Until March 2026
    398 days
    about once a year
  2. March 2026In effect
    200 days
    about 2× a year
  3. March 2027
    100 days
    about 4× a year
  4. March 2029
    47 days
    about 8× a year

Requesting the certificate is the easy part. Getting it onto the right system, into the right store, and making the service pick it up is where the hours go.

For your technical lead

One lifecycle, from discovery to proof.

The same sequence for a public certificate on a web server and an internal one from your own CA.

01Discover

See what is already installed

Each agent inventories the certificate stores and directories on its own host and reports expiry dates. Nothing probes your network.

02Renew

Renewed before it expires

Renewal starts 30 days ahead by default. The current certificate stays active until the new one is in place, and failed attempts retry automatically.

03Deploy

Installed where TLS terminates

IIS bindings, Exchange, Remote Desktop, NGINX, Apache, HAProxy, Kubernetes secrets and appliance APIs, with key permissions applied and the service reloaded.

04Verify

Every step on the record

Issuance, renewal and deployment go into an immutable event log, with who triggered it and the original error if something failed.

All features
Certificate authorities

Public CA, private PKI or your own ACME server

Let's Encrypt works without any CA setup. Google Trust Services, ZeroSSL, SSL.com and Actalis connect with an EAB key pair, as do self-hosted ACME servers like step-ca or EJBCA. Active Directory Certificate Services connects through a connector on the CA host, so the CSR never leaves your network.

Automate a private PKI
  • Let's Encryptno CA setup needed
  • EAB authoritiesGoogle Trust Services, ZeroSSL, SSL.com, Actalis
  • Self-hosted ACMEstep-ca, EJBCA, your own server
  • AD CSthrough the CA connector
Pricing

Start free. Pay one flat price when it's worth it.

No per-certificate fees. Community covers a small estate for good; Standard covers a whole company.

Community

Homelabs and small businesses

€0forever

  • 2 certificates, 2 servers, 1 domain
  • Let's Encrypt, already set up
  • Every deployment target
  • Automatic renewal and mail alerts

Standard

A company running its own servers

€590per year

  • 150 certificates, 75 servers, 5 domains
  • Any authority, public or internal
  • Groups and policies for new servers
  • 30 days of history

Pro, MSP and MSP Plus are on the pricing page.

What people ask before they start

Do I need to know anything about certificates?

Not for the routine. You install the agent, pick what it should manage and where each certificate goes. Renewal, installation and the reload of the service happen on their own after that.

Do private keys ever leave my servers?

No. The agent generates the key on the server that uses the certificate, at first issuance and at every renewal. aethercert stores certificate metadata such as serial number, fingerprint and validity, never the key.

Do I need to open inbound ports?

No. The agent only makes outbound HTTPS connections. No inbound firewall rule, VPN or public IP address is required.

What happens if aethercert is unavailable?

Installed certificates keep working. Renewal starts 30 days before expiry by default, so a temporary outage on our side does not put a certificate at risk.

What does it cost?

Community is free for 2 certificates on 2 servers, with no payment details. Standard is €590 per year for 150 certificates on 75 servers. There are no per-certificate fees.

Make the next renewal the last one you do by hand.

Start free with up to two servers in your own infrastructure. Spend the time you get back on your own work.

Community plan, no card required. Open registration - your account is ready in a few minutes.