mod_pagespeed, maintained again.

Frequently asked questions

1.1-specific questions below. For the 2.0 architecture and integrations, see the 2.0 FAQ →

What counts as a server?

One license per machine running the module — whether that's nginx + worker (ModPageSpeed 2.0), an Apache, nginx, IIS, or Envoy host (mod_pagespeed 1.1), or an ASP.NET Core process. The 14-day free trial covers evaluation in any environment; contact sales@we-amp.com about non-production licensing or multi-server volume pricing.

What happens when the 14-day trial ends?

The module stops optimizing. Your origin serves directly from that point on.

What happens after I cancel?

The module stops optimizing when your license expires (end of the current period). Your origin serves directly from that point on. Re-activate any time — your cache contents and configuration aren't touched.

Is there a free tier?

No free tier. We offer a 14-day free trial — full features. After install, start the trial from the admin console at /pagespeed_global_admin on your server.

How does the license key work?

You receive an Ed25519-signed token via email. Set it as an environment variable. Signature validation runs offline at startup — no internet dependency in the request path. The product refreshes subscription state with our API every 12 hours; see Terms of Service for details.

mod_pagespeed is free. Why should I pay?

The original mod_pagespeed and ngx_pagespeed are no longer actively developed. We-Amp maintains both mod_pagespeed 1.1 (the drop-in continuation of the open-source project — CVE patches, modern nginx, IIS support) and ModPageSpeed 2.0 (the ground-up rewrite with zero-copy serving, variant-aware caching, and an out-of-process worker). Both come with direct email support.

What's your refund policy?

14-day money-back, no questions asked. Cancel before day 15 and we don't charge you. After day 15, cancel anytime through the FastSpring customer portal — billing stops at the end of the current period. Refund requests for charged-but-unused time are handled by FastSpring as Merchant of Record under their standard refund policy. EU/EEA consumers have a 14-day right of withdrawal under EU Directive 2011/83/EU; see Terms of Service for details.

Is mod_pagespeed still maintained?

Yes. Google released its final upstream version in 2020 and archived the project. Active development continued at We-Amp B.V. — a Dutch company founded by one of the former mod_pagespeed maintainers. mod_pagespeed 1.1 is the maintained continuation: drop-in compatible with the open-source release, with ongoing CVE patches, modern build infrastructure, and direct support.

Are the known CVEs against Google's last release patched?

Yes. mod_pagespeed 1.1 ships with patches for the known CVEs that accumulated against the archived upstream. Security maintenance is included with every license; if your security team needs a current CVE statement for procurement, contact us.

Will my existing pagespeed.conf keep working?

Yes. mod_pagespeed 1.1 is a drop-in continuation of the open-source project. All existing pagespeed directives work unchanged — swap the binary, keep your config.

How is 1.1 different from Google's last open-source release?

Same filters, same directives, same in-process architecture. What's added: ongoing CVE patches, modern nginx support (1.26+ as a dynamic module), a native IIS module, the Cyclone shared-memory cache (replacing the old file cache, no config change), and direct email support. Google's last release shipped in 2020; 1.1 is the actively maintained branch.

Which web servers does 1.1 support?

nginx (1.26+ as a dynamic module), Apache (drop-in replacement), IIS (native Windows Server module), and Envoy (HTTP filter).

What happens when my license expires?

mod_pagespeed stops optimizing and passes traffic through unmodified. Your web server continues to function normally — no downtime, no data loss.

Should I run 1.1 or ModPageSpeed 2.0?

Run 1.1 if you're already on open-source mod_pagespeed, need Apache / IIS / Envoy as in-process modules, or want the smallest delta from your current config. Run ModPageSpeed 2.0 if you're starting fresh or want the new architecture (zero-copy serving, variant-aware caching, out-of-process worker). Both are actively maintained.

Is the license heartbeat the same as 2.0?

Yes. Both products share the same offline-validated Ed25519 license token and the same 12-hour heartbeat that refreshes subscription state with our API. No internet dependency in the request path; one license format works across both products.