GetPageSpeed EDGE
The closed, licensed, high-performance edge server. Tuned by us, exclusive to Ultra.
HTTP/3, active upstream health checks, a dynamic upstream API, and benchmark-proven microcaching profiles — in one licensed binary, on every Enterprise Linux release, for $50/month. Not $3,500 per instance per year.
One binary that does the edge job properly
EDGE is the server we always wanted at the front of a stack: TLS 1.3-first termination, HTTP/3/QUIC on every supported OS, request-collapsing microcache for dynamic content, and live upstream reconfiguration — shipped as a single licensed package with opinionated, documented tuning profiles instead of a folder of blog-post snippets.
EDGE is not a bundle of add-ons around a distribution web server. It is built, tested and released as one integrated commercial product. Under the hood, it deliberately implements the proven NGINX module ABI, allowing established open-source modules to be built for EDGE instead of rewritten from scratch.
Microcaching that ships enabled-by-design
The packaged microcache profile gives dynamic content a 1-second cache window with request collapsing and background revalidation: effectively fresh, orders of magnitude faster under load.
HTTP/3 on every EL release
QUIC-enabled TLS engine across EL8, EL9 and EL10. Stock distro web servers offer HTTP/3 on EL10 only — fleets on 8/9 are left behind.
Active upstream health checks
Six health check types probe your backends proactively and eject the sick ones before users notice — the headline feature of commercial edge servers.
Dynamic upstream API
Add, drain and remove backend servers at runtime through an NGINX Plus-compatible HTTP API. No reloads, no dropped connections during deploys.
Tuned TLS out of the box
The packaged TLS profile: TLS 1.3-first ciphers, session cache, OCSP stapling, and dynamic TLS record sizing for faster first bytes.
Tells attackers nothing
Responds as Server: EDGE. No engine name, no version fingerprint, no default error-page signatures for scanners to match CVE lists against.
Benchmarked, not marketed
Same VM, same dynamic backend (~10 ms per request), one server at a time, out-of-the-box configuration on both sides, median of three 30-second runs. That last part is the point: stock distro web servers configure no cache by default; EDGE ships its microcaching profile in the package.
Reverse-proxying a dynamic application — requests per second
wrk, 64 connections, 30 s × 3, Rocky Linux 10, 2 vCPU. Higher is better.
Full methodology
- Rocky Linux 10 VM (aarch64, 2 vCPU, 2.6 GB RAM); load generator, backend and server-under-test on the same host — results are for relative comparison on identical hardware.
- Backend: keep-alive HTTP/1.1 app server simulating ~10 ms of application work per request, identical for both servers.
- Stock: the distribution's own web server package (1.26 line) with a plain reverse-proxy configuration — its out-of-the-box shape. EDGE: the packaged
microcacheprofile wired exactly as its documentation shows. - Cache engagement (
X-EDGE-Cache: HIT) verified before measurement; unsafe methods and session cookies bypass the microcache by default. - TLS full-handshake throughput was measured but is not published: run-to-run variance on the shared-host VM exceeded ±30%, and we don't publish numbers we can't defend. The TLS profile's value is qualitative: TLS 1.3-first, session cache, OCSP stapling, dynamic record sizing.
The commercial-server features, without the commercial-server invoice
| GetPageSpeed EDGE (Ultra) | NGINX Plus | Stock distro web server | |
|---|---|---|---|
| Price | $50/mo — included in Ultra, internal servers unmetered | ~$3,500 / instance / year | $0 |
| Active upstream health checks | Yes — 6 types | Yes | No (passive only) |
| Dynamic upstream API (no-reload changes) | Yes — NGINX Plus-compatible | Yes | No |
| HTTP/3 / QUIC | Yes — EL8, EL9, EL10 | Yes | EL10 only |
| Packaged, documented tuning profiles | Yes — microcache, TLS, rate-limit | Configure yourself | Configure yourself |
| Rate limiting time units | r/s to r/year | r/s, r/m | r/s, r/m |
| Module ecosystem | NGINX ABI-compatible — modules built specifically for EDGE | Native NGINX modules | Limited to distribution-packaged modules |
| Server identity exposed to scanners | EDGE — nothing to fingerprint |
nginx | Engine + often version |
| Also included in the plan | Full premium package repository, repo mirroring, priority support | Support contract | — |
Install
On an Ultra-subscribed server:
sudo dnf install -y https://extras.getpagespeed.com/release-latest.rpm sudo dnf config-manager --enable getpagespeed-extras-edge sudo dnf install -y edge
Then place your Ultra license token at /etc/edge/license.jwt and systemctl enable --now edge — full steps in the EDGE license & setup guide. Configuration lives in /etc/edge/, tuning profiles in /etc/edge/edge-profiles/.
Get EDGE with Ultra
- EDGE — the licensed edge server, this page's headliner
- Everything in Pro: NGINX-MOD + all exclusive modules
- Repo mirroring, unlimited internal hosts
- Priority support
Frequently asked questions
What exactly is GetPageSpeed EDGE?
EDGE is our proprietary, closed, high-performance edge server: a licensed binary distributed as the edge package from our repository, exclusive to the Ultra plan. It terminates TLS, speaks HTTP/3, reverse-proxies and microcaches your applications, and ships with benchmark-proven tuning profiles maintained by GetPageSpeed.
How is EDGE licensed?
EDGE validates an Ultra license token at /etc/edge/license.jwt on every server it runs on. You generate the token in the client area after subscribing — step-by-step instructions in the EDGE license & setup guide. Without a valid Ultra license the binary does not serve traffic.
Will my existing web-server configs work?
Yes. EDGE uses the familiar declarative server/location configuration syntax that operations teams already know, so existing reverse-proxy know-how carries over directly. Configuration lives in /etc/edge/.
Can EDGE use NGINX modules?
Yes. EDGE is designed and shipped as an independent commercial server, but deliberately implements a module ABI compatible with NGINX. Most NGINX module source can therefore be built for the matching EDGE release with little or no adaptation. This gives EDGE access to the mature NGINX module ecosystem without locking customers into a proprietary extension format.
Native modules must match the exact EDGE release and build ABI. Use EDGE-specific module packages rather than arbitrary prebuilt NGINX .so files.
Which operating systems are supported?
Enterprise Linux 8, 9 and 10 (RHEL, Rocky, AlmaLinux, Oracle Linux) on x86_64 and aarch64. DEB-based delivery for Ubuntu and Debian is on the roadmap.
How does EDGE compare to NGINX Plus?
EDGE covers the headline commercial features — active upstream health checks, a dynamic upstream configuration API, HTTP/3 — as part of the $50/month Ultra plan, which also includes the full premium package repository and priority support. NGINX Plus lists at roughly $3,500 per instance per year.
How many servers can I run EDGE on?
The Ultra plan covers your own organization's servers at any internal scale — one subscription, your infrastructure. Redistribution to third-party customer-owned servers requires an Enterprise agreement.
Are the benchmark numbers reproducible?
Yes. The methodology is published on this page: same VM, same dynamic backend, one server at a time, three 30-second runs with the median reported, and out-of-the-box configuration on both sides. The microcache result is dramatic precisely because stock distro web servers configure no cache by default while EDGE ships a documented microcaching profile.
What are the EDGE tuning profiles?
Ready-made, documented configuration profiles packaged in /etc/edge/edge-profiles/: microcaching with instant freshness (1-second window, request collapsing, background revalidation), a TLS 1.3-first profile with OCSP stapling and dynamic TLS record sizing, and rate-limiting presets with extended time units.
Does EDGE replace NGINX-MOD on the Pro plan?
No. Pro keeps NGINX-MOD and the 10+ exclusive Pro modules. EDGE is the tier above: the Ultra plan's own flagship server product, with everything Pro has underneath it.
Can I try EDGE before subscribing?
The package installs only from the Ultra-authorized repository channel and serves only with a valid Ultra license. Subscribe monthly ($50, cancel any time) — the first month effectively is the trial.