sailfork / t3code-github / .repos/ alchemy-effect/ website/ src/ content/ docs/ acme/ index.mdx

ACME (Automatic Certificate Management Environment) is the protocol used by certificate authorities such as Let's Encrypt and ZeroSSL to issue TLS certificates. Alchemy manages the account and certificate separately from the service that terminates TLS. You can issue a certificate once and pass its PEM chain and private key to Fly or another consumer.

Choose when to issue

During deploymentFrom an application
APIACME.CertificateACME.IssueCertificate
AccountACME.AccountBind an existing ACME.Account
DNS-01 validationSerializable solver descriptorRuntime DNS client wrapped as a solver
Certificate storageStack stateYour application's responsibility
RenewalEvaluated on each deploymentYour application's scheduler
RevocationOptional on resource deletionExplicit revoke call

Start with a deploy-time certificate unless your application needs to issue certificates without redeploying. Both paths support wildcard names and use DNS-01 validation; HTTP-01 and TLS-ALPN-01 are not implemented.

Guides

  • Getting started — deploy a Let's Encrypt staging certificate using an existing Cloudflare zone.
  • Certificate authorities — choose staging or production, configure ZeroSSL external account binding, and understand account keys.
  • DNS validation — configure Cloudflare, validate wildcard names, tune propagation, and implement a custom solver.
  • Renewal & revocation — schedule deployments, understand replacement and deletion, and protect persisted keys.
  • Runtime issuance — deploy an authenticated Worker that issues and revokes certificates, then integrate your own storage and renewal scheduler.
  • Using certificates — upload a certificate to Fly or pass its outputs to another TLS consumer.
  • Troubleshooting — diagnose DNS failures, CA rejection, rate limits, and runtime connectivity.

Security and lifecycle

Account and deploy-time certificate private keys are stored in stack state. Redacted masks ordinary logs; it does not encrypt your state backend. Protect the state store, backups, deployment credentials, and any runtime that receives the account key.

Renewal needs execution: a certificate resource checks its expiry when you deploy, not in a background process. Runtime-issued certificates are not tracked as stack resources. In either mode, monitor expiry and arrange renewal before relying on a certificate in production.

API reference

The generated references document each property and method: