Skip to main content

Support terms

Last updated 2026-10-22. Material changes are flagged here and recorded in the changes log below.

The software is open source and free to run. What We-Amp sells alongside it is support. This page summarizes the support terms: what a subscription covers, what it does not, what is signed and attested today, and how purchases are handled.

2026-09-17, release 2.1.0: with the move to Apache-2.0, the per-tier license model on this page is retired. See the changes log.

The short version

  • The software — mod_pagespeed and its predecessor lines — is open source under the Apache License 2.0. Free to install and run, in development and in production, on any number of servers. No key, no token, no registration.
  • A support subscription buys a direct channel to the people who build the product, first-response targets, and advance notice of security releases. It never changes what the software does.
  • Terms live on this page; what each support tier includes, its price, and its first-response target are published at modpagespeed.com/support/ and modpagespeed.com/pricing/.

This is a summary, not a contract — the commercial terms for a support subscription are the product terms at modpagespeed.com/terms/.

1. What this page covers

This page is We-Amp's support-terms home. It summarizes how the software is licensed, what a support subscription covers, what is signed and attested today, and how purchases are handled. It states terms in summary form; where a purchase order or a subscription agreement says something different, that order or agreement governs for the subscription it covers.

The software's license itself is stated on the product site's software license page: Apache License 2.0, for the module, the optimizer worker, and the predecessor lines. That page points here for the support terms.

2. The software: Apache-2.0

mod_pagespeed — the web-server module and the optimizer worker — is open source under the Apache License 2.0. Every feature is available to everyone, in development and in production. You may install and run it on any number of servers without paying, registering, or asking permission.

The standard signed packages are free: the .deb and .rpm packages from the signed package repository, the Docker images, and the NuGet packages. There is no license key and no token — the licensing apparatus of earlier 2.0 releases (keys, activation, the unlicensed signal) is gone.

The source is published; you are free to build, modify, and redistribute it under the same terms. The Apache License 2.0 is a perpetual grant that does not depend on We-Amp B.V.'s corporate status.

3. Support subscriptions

A support subscription covers the things a free open-source license does not include:

  • a direct channel to the people who build the product;
  • first-response targets for configuration, upgrade, and incident questions;
  • advance notice of security releases;
  • scope shaped to your deployment or your organization.

A subscription changes who answers when you need help — never what the software does. It adds no features, unlocks nothing, and is not required to run the software: running without one is a first-class choice, and the software behaves identically either way.

Hosting providers running the software at fleet scale are served through the hosting partner program rather than a per-deployment subscription.

What each support tier includes, its price, and its first-response target are published at modpagespeed.com/support/ and modpagespeed.com/pricing/. This page deliberately carries no numbers.

4. Signed packages and the private repository

A private package repository for Priority and Enterprise subscribers is being set up; it is not delivered yet.

What is signed and attested today is the same for every user, with or without a subscription:

  • GPG-signed apt and yum repositories;
  • .asc signatures on release packages;
  • the Authenticode-signed Windows installer;
  • SHA256SUMS on release assets;
  • the SPDX SBOM and VEX in the source tree;
  • cosign-signed container images with SBOM and provenance attestations.

Packages in the private repository will carry the same Apache License 2.0 as the standard packages.

5. Purchases and billing

Standard and Priority support are bought at checkout from FastSpring, the merchant of record. FastSpring presents the checkout terms at purchase, processes the payment, and handles VAT/sales tax at checkout; its terms govern the payment and refunds. Enterprise agreements are invoiced by We-Amp B.V. directly (master agreement, purchase order, and invoice).

For the rest, the documents governing a subscription rank in this order — when they conflict, the earlier document governs:

  1. The checkout terms presented by FastSpring at the time of purchase.
  2. The product terms at modpagespeed.com/terms/ — the We-Amp support terms summarized on this page apply alongside them.
  3. The terms of service of the We-Amp website you use.

Where your order or a subscription agreement states something different from these documents, the order or agreement prevails for that subscription.

6. ModPageSpeed 2.0, mod_pagespeed 1.15, and IISpeed installs

If you run ModPageSpeed 2.0, mod_pagespeed 1.15, or IISpeed, you can move to mod_pagespeed 2 at no cost. Existing paid terms run to the end of the term you bought — nothing is cut off early, and nobody is left stranded by the transition.

In detail:

  • ModPageSpeed 2.0 stays supported until February 7, 2027 — the migration guide covers the move to mod_pagespeed 2.
  • mod_pagespeed 1.15 installs upgrade in place to mod_pagespeed 2 at no cost — see upgrading to mod_pagespeed 2.
  • IISpeed is deprecated; existing customers transfer at no cost — see iispeed.com.
  • Existing paid terms — support and license terms already bought — continue to the end of their term, as purchased.

7. Changes

This log 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.

2026-10-22

Naming only: the short version and sections 2 and 6 call the product mod_pagespeed, and "mod_pagespeed 2" where the move from an earlier line is the point, instead of "mod_pagespeed 2.1". The dated notice under the page heading now reads "2026-09-17, release 2.1.0" instead of "2.1 GA relicensing". No term on this page changed.

2026-10-20

Section 3 and the short version: "agreed response times" becomes "first-response targets", the wording of the product terms at modpagespeed.com/terms/, which govern a subscription and say we aim to respond within your tier's first-response targets. The targets themselves are unchanged and remain published at modpagespeed.com/support/. No other term on this page changed.

2026-10-19

Sections 3, 4 and 5 and the short version, corrected to what ships today. Prices and first-response targets are now published on modpagespeed.com, so "stated in your quote" is removed and the page links to modpagespeed.com/pricing/ and modpagespeed.com/support/ instead. "SLA-backed delivery of security updates" becomes "advance notice of security releases": no delivery window is defined today. Section 4 was retitled from "Hardened builds" to "Signed packages and the private repository"; wording only. It now states the private package repository as being set up, not delivered, lists what is signed and attested today for every user, and its Apache License 2.0 sentence is in the future tense: it speaks of the packages the private repository will carry. Section 5 names direct invoicing by We-Amp B.V. for Enterprise agreements. The introduction and section 1 no longer present hardened, attested builds as a separate thing sold. No other term on this page changed.

2026-10-09

Section 4 correction. The section previously stated that hardened builds ship with a signed software bill of materials (SBOM) and build provenance on every build. It now states what the hardened builds provide today: signed artifacts with published SHA-256 checksums. No other term on this page changed.

2026-10-08

Editorial: two internal reference tags were removed from the 2026-09-17 and 2026-06-11 entries below. Wording only; no term on this page changed.

2026-09-18

Section 6 was retitled from "Predecessor lines" to "ModPageSpeed 2.0, mod_pagespeed 1.15, and IISpeed installs", and its opening paragraph now names those three products rather than grouping them as a predecessor line; both are wording changes. One term changed: the mod_pagespeed 1.15 bullet previously stated that 1.15 receives security fixes only, with per-platform windows; it now states that 1.15 installs upgrade in place to mod_pagespeed 2.1 at no cost. The bullet's link is unchanged. No other term on this page changed: the ModPageSpeed 2.0 support date of February 7, 2027, the IISpeed transfer terms, the Apache License 2.0 grant, and the treatment of existing paid terms all stand as previously published.

2026-09-17

2.1 GA relicensing. The software — mod_pagespeed 2.1 and its predecessor lines — is now open source under the Apache License 2.0, free to install and run in development and in production. The per-tier license model this page carried (Unlicensed, Community, Starter, Business, Enterprise, Hoster grants; license keys and activation; the never-locks-out commitment) is retired with it: with everything open source and free, there is nothing to license, signal, or lock out. This page is re-scoped from license terms to support terms (same URL): it now summarizes what We-Amp sells alongside the free software — support subscriptions and hardened attested builds — and how purchases are handled. Prices remain at modpagespeed.com/pricing/. Existing paid terms are honored to expiry; predecessor-line customers move to 2.1 at no cost.

2026-06-11

This page became the canonical license-terms home for all We-Amp products. Per-tier grant of use published: Unlicensed, Community, Starter, Business, Enterprise, Hoster. Never-locks-out commitment stated as a standing term; order of precedence documented. The license summary on modpagespeed.com continues as the product-side mirror of this page. Earlier versions of this page covered distribution and the BSL plan only.

Questions?

For support engagements, predecessor-line transitions, or hosting partnerships, see our contact page or email info@we-amp.com.

Related