Stars
Forks
Watchers
Developer links
CertMate
Certificate lifetimes are collapsing toward 47 days, which turns TLS from a yearly chore into a weekly one, and CertMate is the control plane that makes that schedule boring. It issues and renews certificates from Let's Encrypt, ZeroSSL, Google Trust Services, Actalis, DigiCert, SSL.com, Sectigo, or your own private CA, validating by DNS-01 through 29 DNS providers, HTTP-01, or a CSR whose private key never leaves the device. Renewals run automatically, earlier when a certificate's life is short or the CA moves the date through ARI, and deploy hooks push each renewed certificate where it is actually served, then probe the live endpoint to prove the new certificate answers. Discovery watches hosts and certificate transparency logs for certificates you did not issue, folding them into one inventory of what is served where and when it expires. Certificates rest on local disk or in Azure Key Vault, AWS Secrets Manager, HashiCorp Vault, Infisical, or S3 storage, with encrypted backups copied off-site. Its built-in CA issues client certificates for mTLS with OCSP and CRL, and can serve ACME itself, so certbot, lego, acme.sh, and cert-manager get internal certificates under EAB rules you define. Every action lands in a tamper-evident, hash-chained audit trail you can export and verify independently. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Benefits
- Ready for 47-day certificates
- Automatic renewal runs 30 days before expiry by default, earlier for short-lived certificates, and follows the CA's own renewal signals through ARI, including Let's Encrypt's 45-day and 160-hour profiles.
- Every certificate, one inventory
- Discovery observes certificates on your hosts and in certificate transparency logs, including ones you never issued, and folds them into a single inventory of what is served where and when it expires.
- Deployed and verified live
- Post-renewal hooks run your shell commands to reload or push each certificate, then deployment probes over HTTPS, plain TLS, or SMTP STARTTLS compare the real peer certificate to prove it is live.
- Audit trail that proves itself
- Humans, API tokens, scheduled renewals, and AI agents are each attributed in a SHA-256 hash-chained log, exportable as an Ed25519-signed file that third parties verify without trusting the server.
Features
- Multi-CA ACME issuance
- Issue wildcard and multi-name certificates from eight public ACME CAs or a private CA, using DNS-01 across 29 providers, HTTP-01, alias-zone validation, or CSR-only issuance.
- Built-in ACME server
- Act as the CA for internal names and IPv4 addresses: certbot, lego, acme.sh, and cert-manager order 45-day certificates over http-01, dns-01, or tls-alpn-01 under per-client EAB rules.
- Client certificates and mTLS
- The built-in private CA issues, renews, and revokes client certificates for mutual TLS and VPNs, publishing OCSP and CRL status, with revocation hooks that notify your infrastructure.
- API, CLI, and MCP
- Full REST API with Swagger and OpenAPI docs, a first-party Python SDK and certmate-cli terminal client, plus a built-in MCP server so AI assistants manage certificates and run diagnostics.