CertForge acts as an ACME client on your behalf. Configure an ACME provider once, then any device or Domain Trust Profile can request publicly-trusted certificates through CertForge’s approval and policy layer.Documentation Index
Fetch the complete documentation index at: https://docs.certforge.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Add an ACME CA
- Go to Admin → Certificate Authorities → New
- Select type ACME
- Fill in:
| Field | Let’s Encrypt | ZeroSSL |
|---|---|---|
| Name | Let's Encrypt | ZeroSSL |
| Directory URL | https://acme-v02.api.letsencrypt.org/directory | https://acme.zerossl.com/v2/DV90 |
| Contact email | Your ops email | Your ops email |
- Save — CertForge registers an ACME account with the provider automatically.
Use Let’s Encrypt’s staging environment (
https://acme-staging-v02.api.letsencrypt.org/directory) while testing to avoid rate limits. Switch to production before going live.Configure DNS validation
ACME requires proving you control the domain. CertForge uses DNS-01 challenge solving, which works for wildcard certs and doesn’t require an open HTTP port.Cloudflare
Inconfig.yaml:
Zone:DNS:Edit permission scoped to your zone(s). Set the token via environment variable:
Route 53 (AWS)
Manual (any DNS provider)
Create a Domain Trust Profile for ACME
- Go to Admin → Domain Trust Profiles → New
- Set:
- Domains:
*.corp.com(or your public domain) - CA: select the ACME CA you created
- Require approval: recommended for production domains
- Domains:
- Save
Test an issuance
Using certbot pointed at your CertForge dashboard:Let’s Encrypt rate limits
| Limit | Value |
|---|---|
| Certificates per registered domain per week | 50 |
| Duplicate certificates per week | 5 |
| New orders per account per 3 hours | 300 |