Out of the box, nothing is locked.

Production use requires a commercial license — but the software never locks you out. For non-commercial sites, the Community tier makes that deployment licensed: $0, self-attested, one site, renewable every 365 days. Mint your key below.

Mint a key

The key is bound to this address, and a confirmation link is sent to it before the key is issued. Use the same address when you renew.

Site domain

One site per key. A full URL or subdomain is fine; the server keeps the registrable domain (www.example.com becomes example.com).

I attest that this site is non-commercial or operated by a registered not-for-profit organization, that this key covers this one site, and that I accept the license terms at we-amp.com/licensing/. This self-attestation is binding.

Also send me occasional product updates — releases and licensing changes. Optional. See the Privacy policy.

Requests are rate limited per IP address. Repeated failures are blocked for a while; wait a few minutes before retrying.

Your Community key

Store the key with your deployment configuration, then activate it:

Set PAGESPEED_LICENSE_KEY=<key> in the environment of both the nginx module and the worker (recommended), or
paste it into the admin console: License status card, manual key entry.

Docker, systemd, and Kubernetes specifics: License activation.

What Community covers

$0 per site, self-attested. Non-commercial production: personal sites, non-profits, education, and evaluation deployments. The key covers one site on either engine, mod_pagespeed 1.15 or ModPageSpeed 2.0; servers and instances behind the site do not count. Commercial deployments need a paid tier — see pricing. The full terms live at we-amp.com/licensing/.

Renewal

Keys last 365 days. To renew, submit the same email and domain again and confirm the emailed link: the API mints a fresh key, and you install that one. You can renew at any time, before or after expiry. If a key lapses, nothing breaks: the software keeps optimizing and signals the unlicensed state with an X-PageSpeed-Warn response header until a current key is installed.

Which releases the grant covers

The Community grant is part of the license text that ships inside each release, so it covers releases published after the grant was added. Older binaries you may already be running carry the earlier license and are not retroactively covered; upgrade to a current release before running under a Community key.