Skip to content
$ACME has not launched yet. There is no contract address. Any token claiming to be $ACME right now is not this project. The address will be published here first.
Why this name

A word that already carries weight in two directions

ACME was not picked because it is funny. It was picked because it is one of very few words that is simultaneously a piece of critical internet infrastructure and a hundred-year-old joke about ranking first. Both halves matter, and this page is the evidence for both.

01The technical meaning

RFC 8555 secures most of the public web

When a machine reads ACME in a technical context, this is what it means, not the coyote.

CA market share, Let’s Encrypt
64.7%
of websites whose certificate authority is known
W3Techs · 2026-07-31
Certificates issued per day
~10M
Let’s Encrypt, steady-state issuance
Let’s Encrypt · 2025-12-09
cert-manager in new K8s clusters
86%
of new production Kubernetes clusters deploy it
CNCF · 2026
cert-manager downloads
500M+/mo
at time of CNCF graduation
CNCF · 2026
Total public TLS certs
110M+
all certificate authorities combined
RFC 8555 published
Mar 2019
Barnes, Hoffman-Andrews, McCarney, Kasten — IETF Proposed Standard
IETF · 2019-03

Who speaks the protocol

WhoWhatSince
Let’s EncryptSpeaks ACME and nothing else. No manual issuance path exists.2015
Google Trust ServicesPublic ACME endpoint for all customers.2021
AWS Certificate ManagerManaged ACME endpoint, 45-day public TLS certs.2026-07
CloudflareACME for custom hostnames and origin certificates.2019
ZeroSSL / SectigoCommercial ACME endpoints.2020
Kubernetes (cert-manager)De facto cluster certificate controller, ACME-native.2017
Caddy / TraefikACME built into the web server itself; TLS on by default.2015
Microsoft AzureACME support via App Service and Key Vault integrations.2022

The forcing function

CA/Browser Forum ballot SC-081v3, passed 11 April 2025, collapses the maximum lifetime of a public TLS certificate on a fixed schedule. Each step makes manual renewal less survivable.

0d300d600d900dNOWpre-202015 Mar 2029
Get this right. The 47-day figure is quoted everywhere as though it were current. It is not; it lands in 2029. The limit in force today is 200 days.

In July 2026 AWS Certificate Manager shipped a managed ACME endpoint issuing 45-day public certificates. When the largest cloud adopts a protocol rather than competing with it, the category is settled.

02The placeholder meaning

A hundred-year-old ranking hack

The origin is the part most people miss, and it is the part that makes the token make sense. Acme was not a joke first. It was an optimisation first.

American businesses in the 1920s named themselves Acme so they would appear at the top of alphabetised telephone directories. From the Greek akmē, the highest point. Chuck Jones, who put it in Looney Tunes, said the quiet part out loud: “AC was about as high as you could go; it means the best.”

So the most famous fake company in history began as a hack on an index. It was adopted so widely that it stopped meaning anything specific, became shorthand for any company, and ended up the default placeholder in technical documentation worldwide. It is a ranking strategy that succeeded so completely it turned into a punchline.

Running that same play on the index that is replacing search is not a coincidence of naming. It is the same move, a century later, on the next directory.

  1. 1920sA ranking hackUS businesses name themselves Acme so they sort first in alphabetised telephone directories. From Greek akmē — the highest point. At one stage Manhattan lists hundreds of them.
  2. 1930sCartoon shorthandWarner Bros. adopts Acme as the supplier of everything in Looney Tunes. Chuck Jones: “AC was about as high as you could go; it means the best.”
  3. 1980sThe documentation defaultAcme becomes the standard placeholder company in software manuals, RFCs and code examples.
  4. 2026A tickerThe same ranking hack, run on the index that is replacing search.
03The competitive position

Acme is not the biggest placeholder. It is the only unowned one.

Worth stating plainly, because the opposite claim would be easy to make and trivially false.

PlaceholderOwnerStatus
example.comIETF (RFC 2606 / 6761)Reserved. Unregisterable by anyone.
ContosoMicrosoftOn Microsoft’s official list of 46 fictional companies.
AcmenobodyNot on that list. Not owned. Not reserved.
AnyCompanyAmazon Web ServicesAWS documentation standard.
CymbalGoogle CloudGoogle Cloud documentation standard.
FabrikamMicrosoftMicrosoft manufacturing placeholder.

example.com is reserved by RFC 2606 and RFC 6761 and cannot be registered by anyone. Contoso, Fabrikam, AnyCompany and Cymbal are house placeholders belonging to Microsoft, Amazon and Google. Acme is not on Microsoft’s official list of 46 fictional companies at all. It is the one name on this list with no owner, no reservation, and no corporate steward.

04In the wild

Acme, as it actually appears in their documentation

Verbatim strings from published material, quoted and linked to source.

Stripe · SSO consolidation guideverified
Acme Inc. has four Stripe accounts.
View source →
Okta · Salesforce SAML configuration guideverified
Acme Corp has developed applications for partners and customers and needs to allow access using a single username and password.
View source →
Okta · okta-signin-widget, localisation stringsverified
"primaryauth.title": "Sign in to Acme"
"primaryauth.username.placeholder": "Your Acme Username"
View source →
Salesforce · custom domain exampleverified
https://acme.my.salesforce.com
View source →
Vercel · team and project placeholderunverified
acme.com and "Acme" as the default team name in dashboard and docs examples.
View source →
Auth0 · quickstart tenant namingunverified
"Acme" used as the example tenant across getting-started guides.
View source →

Why there are no screenshots or logos here

Screenshots of these pages are not reproduced. Capturing them was blocked by the network policy in the build environment, and an image of another company’s documentation that we did not actually capture would be a fabricated record. The exact strings are quoted instead, each linked to the page it came from. Two rows are marked unverified: widely reported, but not confirmed against source in this pass. None of these companies is affiliated with $ACME.

None of these companies is involved

Stripe, Okta, Salesforce, Vercel, Auth0 and the IETF have no relationship with $ACME and have not endorsed, sponsored or approved it. Their names appear here solely to refer factually to documentation they themselves published. Full non-affiliation notice →