certimate

An open-source and free self-hosted SSL certificates ACME tool, automates the full-cycle of issuance, deployment, renewal, and monitoring visually. 完全开源免费的自托管 SSL 证书 ACME 工具，申请、部署、续期、监控全流程自动化可视化，支持各大主流云厂商。

⭐ 8,577 stars on GitHub · 🍴 827 forks · 📜 License: mit · 💻 Language: Go

What is certimate?

Certificate automation gets messy fast once you manage more than a couple of domains, DNS providers, and deployment targets. Certimate gives you a self-hosted, visual ACME certificate manager that handles issuance, renewal, deployment, and monitoring without forcing you into a SaaS control plane.

Main components

• Visual workflow orchestration for certificate issuance, deployment, renewal, and monitoring.
• ACME client support for Let’s Encrypt, Google Trust Services, ZeroSSL, SSL.com, Actalis, and other CAs.
• DNS-01 and HTTP-01 challenge support for single-domain, multi-domain, wildcard, and IP address certificates.
• Broad DNS provider integration, covering 60+ registrars and DNS services including Cloudflare, AWS, GoDaddy, Alibaba Cloud, and Tencent Cloud.
• Deployment automation for 120+ targets including Kubernetes, CDNs, WAFs, load balancers, and other hosting platforms.
• Certificate export in common formats such as PEM, PFX, and JKS, with RSA and ECC key options.
• Notification integrations for email, Slack, Discord, Telegram, DingTalk, Feishu, WeCom, and more.
• Lightweight self-hosted deployment via Docker or a standalone binary, with no external database or runtime required.

Clear use cases

• Automate wildcard certificate issuance with DNS-01 across Cloudflare, Route 53, or other DNS providers.
• Keep Kubernetes ingress, CDN endpoints, and load balancers updated without manual certificate uploads.
• Centralize certificate renewal and expiry monitoring for a small business or internal platform team.
• Replace scattered Certbot scripts with a visual workflow that non-specialist admins can understand.
• Manage certificates across mixed infrastructure where some services need PEM files and others require PFX or JKS.
• Run certificate management privately on your own server instead of handing DNS/API credentials to a commercial SaaS.

The biggest strength is end-to-end certificate workflow automation across many providers — Certimate does not stop at requesting a certificate. It can push the renewed certificate into real deployment targets and notify your team when something needs attention. Compared with commercial certificate lifecycle tools, the unique value is that you get broad provider coverage and visual operations while keeping credentials, certificate data, and automation logic inside your own environment.

Best for sysadmins, DevOps engineers, homelab operators, and small platform teams that need reliable SSL automation across multiple DNS providers, clouds, and deployment targets without buying into a hosted certificate management platform.

Topics: the project is tagged with popular topics:

• 🏷️ acme
• 🏷️ acme-client
• 🏷️ automation
• 🏷️ certbot
• 🏷️ certificate
• 🏷️ certificate-management
• 🏷️ certificate-manager
• 🏷️ certificates
• 🏷️ devops
• 🏷️ https

📸 Screenshots

Quick install

See the README for detailed install instructions. Most projects support Docker — if the repo has a Dockerfile, use:

git clone https://github.com/certimate-go/certimate.git
cd certimate
docker build -t certimate .
docker run -d -p 8080:8080 certimate

Minimum system requirements

⚡ Deploy fast on VSIS

Use the VSIS VPS Lite 2GB RAM / 2 vCPU / 25GB SSD (~104k/tháng) plan from VSIS.NET — high-speed VN-based VPS, 24/7 support, ideal for running certimate smoothly.

🎯 Benefits:

• One-command docker compose up -d deploy in 2 minutes
• Dedicated IPv4, root access, unmetered domestic bandwidth
• Daily snapshot backup
• Free install assistance from the VSIS team

👉 See matching VPS plans at vsis.net

Resources

• 🔗 GitHub: certimate-go/certimate
• 🌐 Homepage: https://docs.certimate.me
• 📚 Official docs: see README in the repo
• 💬 Community: GitHub Issues + Discussions

Article compiled from GitHub data on 05/05/2026. Star/fork counts may have changed — see live numbers via the GitHub link.