License Terms

These terms govern the use of We-Amp's binary software distributions: ModPageSpeed 2.0 (Docker images with a Helm chart, and a NuGet preview for ASP.NET Core) and the companion mod_pagespeed 1.15 line (.deb/.rpm/.msi packages).

Releases shipped after these terms took effect reference this page by its URL, https://we-amp.com/licensing/, in their license documents. The terms that govern a release are the terms published here on that release's date. Changes to this page bind releases shipped after the change and subscriptions renewed after it — they do not rewrite the terms of a release you already received.

By installing or using a We-Amp product you accept the terms of the tier that applies to your use.

A site is one registrable domain plus its subdomains. example.com, www.example.com, and shop.example.com together are one site; example.org is a second site. A server is one running instance of the software serving the site — a physical machine, a virtual machine, or a container.

Licensing is per site, except Enterprise (per organization) and Hoster (per host). Every paid subscription includes security patches and version upgrades; support varies by tier. This page states what each tier permits and deliberately carries no prices — those are published at modpagespeed.com/pricing/.

2.1 Unlicensed

No signup, no key. You may install and run the software on any number of servers for evaluation, development, and testing. Production use is not covered by this tier: it requires a license under one of the tiers below. The software does not enforce that requirement — an unlicensed install stays fully functional and is signalled as described in section 4.

2.2 Community

Production use of a site is permitted where the site is non-commercial or operated by a registered not-for-profit organization, under a Community key issued for that site at no charge. Community is a registered license class — the same grant mechanics as the paid tiers, with eligibility in place of payment. Keys are issued on self-attestation — an email address, the site domain, and your confirmation that the use qualifies — and are valid for one year, renewing the same way they were issued: by re-attesting. We do not verify attestations; a materially false attestation places the use outside this grant. This permission applies from the next release onward after its first publication here (see the changelog, section 9); releases shipped before it are not retroactively covered. Community keys are issued only while these terms are in force; request one at modpagespeed.com/community-license/.

2.3 Starter

A Starter license permits commercial production use of one site on up to two servers concurrently serving that site. Support is community-level, without the priority handling Business includes.

2.4 Business

A Business license permits commercial production use of one site on any number of servers, containers, or instances. Autoscaling groups, high-availability replicas, and elastic container fleets serving the licensed site are all covered — the site is the licensed unit, not the machine. Includes priority email support.

2.5 Enterprise

An Enterprise license is organization-wide: production use of all sites the organization operates, on any number of servers, with any engine. Enterprise licensing is sold under a negotiated agreement and includes a service-level agreement, invoicing under a master services agreement, supply-chain attestations (software bill of materials, signed artifacts), and a direct support line. Where the negotiated agreement and this page conflict, the agreement governs.

2.6 Hoster

A Hoster license is per host: one licensed hosting server covers every customer domain served from that host. Hoster licensing is arranged as a partner agreement, with keys scoped to the host and volume terms negotiated per deal. See the contact page.

2.7 One license, any engine

A site license (Community, Starter, or Business) covers whichever We-Amp engines serve that site: the mod_pagespeed 1.15 line on Apache, nginx, IIS, or Envoy, and ModPageSpeed 2.0. You may switch or mix engines under one license. The ASP.NET Core middleware joins this model at general availability (section 8).

2.8 Honor system

Tier limits are license terms, not technical controls. The software does not count your servers or verify your attestation — the tiers are designed for honest self-selection, with the signal described in section 4 as the only backstop. No release will add gating to the optimization functionality the Unlicensed and Community tiers include.

License keys are Ed25519-signed tokens, validated against api.modpagespeed.com and cached locally; an internet connection is needed only for activation and periodic renewal. Activation is handled through the admin console at /pagespeed_global_admin or via a license key in your configuration. A key under any tier removes the unlicensed signal.

A lapsed subscription behaves exactly like unlicensed use: the software keeps optimizing and is signalled as described in section 4. Renewing restores the licensed state. Renewals are governed by the terms in force at the time of renewal (section 9).

Purchases and use are governed by these documents. When they conflict, the earlier document in this list governs:

1. The checkout terms presented by FastSpring at the time of purchase.
2. The product terms at modpagespeed.com/terms/.
3. The terms of service of the We-Amp website you use.

This page supplies the grant of use those documents reference. For Enterprise and Hoster customers, the negotiated agreement governs first (sections 2.5 and 2.6).

We intend to publish the ModPageSpeed 2.0 source under the Business Source License 1.1 (BSL 1.1). BSL is a source-available license introduced by MariaDB and used by companies such as HashiCorp. Each published release will carry a four-year change-date after which that release converts automatically to Apache 2.0. The change-date is the worst-case ceiling — it applies regardless of We-Amp B.V.'s corporate status.

The optimization libraries inherited from the original mod_pagespeed remain Apache 2.0 today and are not affected by the BSL plan.

No date is committed. We'll announce on the ModPageSpeed blog when source publication is scheduled. Enterprise customers who need source access on a defined timeline should email enterprise@modpagespeed.com — we can prioritize this against active deals.

The ASP.NET Core middleware preview package (WeAmp.PageSpeed.AspNetCore) is available for evaluation during the preview period. Production use requires a commercial license. As with every ModPageSpeed distribution, unlicensed use is never blocked; the middleware simply adds the X-PageSpeed-Warn response header. The package's license text is the Business Source License 1.1. Preview versions released after these terms took effect carry an Additional Use Grant incorporating the permissions published on this page as of each version's release date; earlier versions carry none. At general availability the middleware joins the per-site model in section 2 — that change will be announced ahead of time so you can plan.

This changelog is append-only: entries are added, never edited or removed. The page's full revision history is additionally preserved in We-Amp's version control. Subscription renewals are governed by the terms in force at the time of renewal. Until an email notification mechanism for key holders is in place, material changes are flagged prominently at the top of this page and recorded here — this changelog is the authoritative record of what changed and when.

Pricing is published at modpagespeed.com/pricing/. This page deliberately carries no prices — terms here, numbers there. Starter and Business purchases are immediate-charge subscriptions via FastSpring, billed when you buy; Enterprise and Hoster licensing is invoiced under negotiated agreements (sections 2.5 and 2.6). You can install and run the product unlicensed to evaluate it before you buy, as described in section 2.1.