# polymind-inc/acmebot

Automated ACME SSL/TLS certificate management built around Azure Key Vault

Repository: https://github.com/polymind-inc/acmebot
Canonical: https://ross.abutalabs.com/products/acmebot
Homepage: https://acmebot.dev/
Language: C#
License: Apache-2.0
License Family: permissive
Topics: azure, azure-key-vault, azure-app-service, azure-cdn, azure-frontdoor, letsencrypt, acme-v2, azure-application-gateway, certificate, azure-functions
Last push: 2026-08-31T05:28:47+00:00

## Health v2 (maintenance only)
Score: 100/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 100, release rhythm 99, longevity 100
- inputs: {"age_days": 2898, "days_push": 2, "days_rel": 7, "gap_med": 11, "n_releases_24m": 22}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1156, forks 311 (observed 2026-09-01T02:14:05.986598+00:00)

## What it is
Acmebot is an Azure-native application that automates ACME SSL/TLS certificate issuance and renewal using DNS-01 validation, storing private keys and certificates in Azure Key Vault. It runs as an Azure Function App with a dashboard, HTTP API, and CLI, supporting Let's Encrypt and other ACME CAs across multiple Azure services.

## Use cases
- automate letsencrypt certificate renewal on azure
- issue wildcard ssl certificates for azure app service
- store tls certificates in azure key vault
- manage ssl certificates for azure front door and application gateway
- replace manual certificate renewal scripts
- monitor certificate expiry across multiple azure domains
- set up acme certificate automation with dns-01 validation

## When to choose
- you run workloads on Azure services like App Service, Front Door, or Application Gateway and need automated TLS certificates
- you want private keys generated and stored in Azure Key Vault rather than on disk
- you need wildcard or multi-domain (SAN) certificates via DNS-01 validation
- you want ARI-aware renewal scheduling and webhook notifications for certificate operations

## When to avoid
- your infrastructure is not on Azure or you do not use Azure Key Vault
- you need HTTP-01 or TLS-ALPN-01 validation instead of DNS-01
- your DNS provider is not among the supported integrations
- you need a simple standalone certbot-style tool outside the cloud

## Facets
- artifact type: application
- maturity: active
- function: security, deployment, webhook, monitoring, api-framework, cli
- domain: security, cloud-computing, self-hosted
- platform: cloud, serverless, cli
- tags: acme, lets-encrypt, ssl-tls, certificate-management, azure-key-vault, dns-01, azure-functions, wildcard-certificates, certificate-renewal, devops, automation, web-server

## Member repositories
- polymind-inc/acmebot (main) score 100

## Provenance
- Observed fields: from GitHub, fetched 2026-09-01T02:14:05.986598+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:33:29.352677+00:00, confidence not recorded.
  - readme: https://github.com/polymind-inc/acmebot (fetched 2026-09-01T02:14:05.986598+00:00, sha 2bc8201e4cce)
  - homepage: https://acmebot.dev/ (fetched 2026-08-29T12:38:04.102934+00:00, sha 0c500077c188)
  - site_page: https://acmebot.dev/guide/getting-started (fetched 2026-08-29T12:38:04.105405+00:00, sha d5186cad10e5)
  - site_page: https://acmebot.dev/guide (fetched 2026-08-29T12:38:04.107169+00:00, sha 5a0b8454265c)
- Data as of 2026-08-30T08:39:29.467469+00:00.