# local-cert

> Self-hosted service that issues and renews trusted Let's Encrypt certificates for NAS boxes, hypervisors and internal services, through DNS-01 validation. REST API, built-in ACME server, MCP server for AI agents.

local-cert is a self-hosted service that obtains and renews publicly trusted Let’s Encrypt certificates for machines on a private network — NAS, hypervisors, internal web apps — using the DNS-01 challenge. It holds the DNS credentials in one place and hands out certificates through a REST API, a built-in ACME server and an MCP server for AI agents.

## Key facts

- Current version: 0.5.0. Published by Resourcepool. Source: https://github.com/resourcepool/local-cert
- Deployment: self-hosted, one container (Node.js), SQLite or PostgreSQL.
- Validation: ACME DNS-01 only; hosts never need to be reachable from the Internet.
- DNS providers: AWS Route53, OVHcloud, Gandi LiveDNS, GoDaddy, Google Cloud DNS.
- Interfaces: REST API (OpenAPI 3.1), ACME server with External Account Binding (RFC 8555) at /acme/directory, MCP server at /api/mcp.
- Access control: API keys with per-domain scopes (cert:read, cert:issue, cert:renew, cert:revoke, cert:export, dns:read, dns:write, admin:*).
- Security: argon2id passwords, private keys encrypted with AES-256-GCM, audit log, HMAC-SHA256 signed webhooks.
- Console languages: English, French, Spanish, Italian, Portuguese, German.

## Features

- DNS-01 on five providers: AWS Route53, OVHcloud, Gandi LiveDNS, GoDaddy and Google Cloud DNS. Several accounts per host are the normal case.
- A built-in ACME server: Point Traefik, Caddy, certbot, acme.sh, lego or cert-manager at /acme/directory with an EAB credential. They keep their usual workflow.
- REST API with OpenAPI 3.1: Issue, renew, revoke and download certificates. The spec is generated from the validators, and an in-console explorer sends real requests.
- MCP server for AI agents: Agents get the same tools as the API — with the same scopes and the same audit trail. A key can do nothing more over MCP than over curl.
- Per-domain, scoped access: Each key carries scopes like cert:issue or cert:export on specific domains. The NAS key cannot issue for the build server.
- Renewal on autopilot: Certificates renew ahead of expiry, with a deterministic ±24 h jitter so your whole fleet never hits Let’s Encrypt in the same minute.
- Least-privilege IAM, generated: The console writes the IAM policy for exactly your zones, then probes the five Route53 calls it needs before a domain is saved.
- Secure by construction: argon2id passwords, private keys encrypted with AES-256-GCM, every mutation in an audit log, webhooks signed with HMAC-SHA256.
- Watch it happen: Every issuance streams its events live: order, TXT published, propagation, validation, cleanup. Failures retry with exponential backoff.

## Docs: Getting started

- [Quick start](https://local-cert.link/en/docs): From provider to first certificate.
- [Add a domain](https://local-cert.link/en/docs/domains): Pick the zone, grant permissions, test.

## Docs: DNS providers

- [Overview](https://local-cert.link/en/docs/providers): Supported hosts, principle, environment variables.
- [AWS Route53](https://local-cert.link/en/docs/providers/aws): IAM user, role, policies, multiple accounts.
- [OVHcloud](https://local-cert.link/en/docs/providers/ovh): API token limited to DNS.
- [Gandi](https://local-cert.link/en/docs/providers/gandi): LiveDNS Personal Access Token.
- [GoDaddy](https://local-cert.link/en/docs/providers/godaddy): Production API key.
- [Google Cloud](https://local-cert.link/en/docs/providers/gcp): Cloud DNS service account.

## Docs: ACME server

- [Principle and EAB credentials](https://local-cert.link/en/docs/acme): What it is, how a certificate is issued, what EAB is for.
- [certbot, acme.sh, lego](https://local-cert.link/en/docs/acme/clients): The command-line clients, the basis of most integrations.

## Docs: Reverse proxies

- [Traefik](https://local-cert.link/en/docs/acme/traefik): Native ACME resolver with EAB.
- [Caddy](https://local-cert.link/en/docs/acme/caddy): Global or per-site options.
- [Nginx](https://local-cert.link/en/docs/acme/nginx): With certbot or acme.sh.
- [Apache httpd](https://local-cert.link/en/docs/acme/apache): mod_md.
- [HAProxy](https://local-cert.link/en/docs/acme/haproxy): acme.sh and its deploy hook.
- [Nginx Proxy Manager](https://local-cert.link/en/docs/acme/nginx-proxy-manager): No custom CA: import the certificate.

## Docs: Platforms

- [Kubernetes](https://local-cert.link/en/docs/acme/kubernetes): cert-manager, ACME ClusterIssuer.
- [Dokploy](https://local-cert.link/en/docs/acme/dokploy): Additional Traefik resolver.
- [Coolify](https://local-cert.link/en/docs/acme/coolify): Traefik proxy configuration.
- [Synology DSM](https://local-cert.link/en/docs/acme/synology): acme.sh and the synology_dsm hook.
- [Proxmox VE](https://local-cert.link/en/docs/acme/proxmox): pvenode acme, custom account.
- [Other systems](https://local-cert.link/en/docs/acme/others): OPNsense, pfSense, TrueNAS, and anything that doesn't speak ACME.

## Docs: Reference

- [Installation & configuration](https://local-cert.link/en/docs/reference/install): Setup, environments, database, worker, Docker.
- [REST API](https://local-cert.link/en/docs/reference/api): Authentication, scopes, endpoints, issuance, metadata, OpenAPI.
- [MCP server](https://local-cert.link/en/docs/reference/mcp): Tools and skills for AI agents.
- [Security & DNS records](https://local-cert.link/en/docs/reference/security): Secrets, audit, provenance markers, IAM pitfalls.
- [Operations & limits](https://local-cert.link/en/docs/reference/operations): DNS-01 internals, deletion and recovery, strategies, known limits.

## FAQ

### What is local-cert?

local-cert is a self-hosted service that obtains and renews publicly trusted Let’s Encrypt certificates for machines on a private network — NAS, hypervisors, internal web apps — using the DNS-01 challenge. It holds the DNS credentials in one place and hands out certificates through a REST API, a built-in ACME server and an MCP server for AI agents.

### How is it different from running certbot or acme.sh with DNS-01 on each host?

Those clients need DNS credentials on every machine, and each one can usually rewrite the whole zone. With local-cert the credentials live in a single service, each host gets a key scoped to its own domain, renewals are scheduled centrally, and every issuance is in one audit log. Existing ACME clients keep working: they point at local-cert instead of Let’s Encrypt.

### Does my host need to be reachable from the Internet?

No. Validation goes through DNS, not through your host. Only local-cert needs outbound access to your DNS provider’s API and to Let’s Encrypt.

### Which DNS providers are supported?

AWS Route53, OVHcloud, Gandi LiveDNS, GoDaddy and Google Cloud DNS. Your domain’s zone must be hosted at one of them; several accounts per provider are supported.

### Are these real, publicly trusted certificates?

Yes. They are issued by Let’s Encrypt, so every browser and operating system trusts them out of the box. There is no root certificate to install.

### Do I have to publish my private IPs in public DNS?

Only if you want local-cert to create the A record for you. With a wildcard certificate, nothing about your internal topology appears in the zone.

### Can Traefik, Caddy or cert-manager use it without changes?

Yes. They point at local-cert’s ACME directory with an EAB credential, as they would with any CA. Their HTTP-01 challenge is fulfilled through DNS-01 behind the scenes.

### What about Let’s Encrypt rate limits?

Production allows 50 certificates per registered domain per week. Development instances use the staging environment by default, renewals are spread out with jitter, and a wildcard needs a single order.

### Where are private keys stored?

In your database, encrypted with AES-256-GCM. They only leave in clear text through the bundle endpoint, for keys holding the cert:export scope — and every export is logged.

### What happens if my DNS account becomes unreachable?

Nothing gets stuck. Deletion revokes and cleans up on a best-effort basis, removes the row anyway, and tells you which records you need to delete by hand.

## Optional

- [local-cert — Let's Encrypt certificates for your local network](https://local-cert.link/en): home page (en)
- [local-cert — des certificats Let's Encrypt pour votre réseau local](https://local-cert.link/fr): home page (fr)
- [Sitemap](https://local-cert.link/sitemap.xml): every page in every language
