NGINX Amplify Alternative: The Drop-In Replacement (2026)

Looking for an NGINX Amplify alternative after F5 shut down the service? You’re not alone. F5 Networks officially discontinued NGINX Amplify on January 31, 2026, leaving thousands of users without their monitoring solution.

If you relied on NGINX Amplify for server monitoring, GetPageSpeed Amplify is the only drop-in compatible NGINX Amplify alternative that works with your existing agent—no reinstallation required.

This guide covers everything you need to know about migrating from NGINX Amplify and why GetPageSpeed Amplify offers even more features than the original.

What Happened to NGINX Amplify?

NGINX Amplify was a free SaaS monitoring platform launched by NGINX, Inc. that allowed users to monitor NGINX instances, PHP-FPM pools, MySQL databases, and system metrics. After F5 Networks acquired NGINX in 2019, the service continued operating—until F5 announced its deprecation.

Key dates:

• 2019: F5 acquires NGINX, Inc.
• 2025: F5 announces NGINX Amplify deprecation
• January 31, 2026: NGINX Amplify service permanently discontinued

The shutdown left users scrambling for alternatives. Most monitoring solutions require reinstalling agents, reconfiguring dashboards, and learning entirely new systems. That’s why we built GetPageSpeed Amplify as a true NGINX Amplify alternative—one that respects your existing setup.

GetPageSpeed Amplify: The Drop-In Replacement

GetPageSpeed Amplify was built specifically to fill the void left by NGINX Amplify’s shutdown. Unlike other monitoring solutions, it’s fully API-compatible with the original NGINX Amplify agent—meaning migration takes under 60 seconds.

Key Advantages

How to Migrate from NGINX Amplify

Migration requires changing a single configuration line. Your existing nginx-amplify-agent continues working without modification.

Step 1: Sign Up for GetPageSpeed Amplify

Visit amplify.getpagespeed.com and create an account. You can sign up with GitHub or email.

Step 2: Get Your API Key

After signing up, navigate to Settings → API Keys and copy your API key.

Step 3: Update Agent Configuration

Edit the agent configuration file:

sudo nano /etc/amplify-agent/agent.conf

Find the [cloud] section and update the api_url:

[cloud]
api_key = YOUR_API_KEY_HERE
api_url = https://amplify.getpagespeed.com

Step 4: Restart the Agent

sudo systemctl restart amplify-agent

That’s it. Your metrics start flowing to GetPageSpeed Amplify immediately. No agent reinstallation, no configuration rewrites, no learning curve.

Features That Surpass NGINX Amplify

GetPageSpeed Amplify doesn’t just replace NGINX Amplify—it improves on it with features the original never had.

Full-Stack Monitoring

Monitor your entire web infrastructure from a single dashboard:

• NGINX: Request rates, HTTP status codes, connection metrics, response times
• Varnish Cache: Cache hit ratios, backend health, object storage
• PHP-FPM: Pool metrics, process counts, slow requests, memory usage
• MySQL: Query throughput, connection counts, buffer pool stats
• System: CPU, memory, disk I/O, network throughput

For optimizing your PHP-FPM performance based on the metrics you collect, see our guide on optimizing NGINX for high-performance PHP websites.

Website Performance Monitoring

Unlike NGINX Amplify which only monitored server-side metrics, GetPageSpeed Amplify monitors your websites from the outside:

• TTFB (Time to First Byte): Track response times from multiple locations
• Protocol detection: HTTP/1.1, HTTP/2, HTTP/3 (QUIC) support verification
• Compression analysis: Verify Brotli and Gzip are working correctly
• SSL certificate monitoring: Get alerts before certificates expire
• Uptime monitoring: Check intervals from hourly to every minute

Security Analysis with Gixy

GetPageSpeed Amplify integrates Gixy, Yandex’s NGINX configuration analyzer. Every configuration change is automatically scanned for:

• Server-Side Request Forgery (SSRF) vulnerabilities
• HTTP response splitting attacks
• Path traversal risks
• Weak SSL/TLS configurations
• Missing security headers
• add_header directive issues
• Alias traversal vulnerabilities

Security issues are flagged with severity levels (CRITICAL, WARNING) and include remediation guidance. For comprehensive SSL/TLS security, also review our NGINX TLS 1.3 hardening guide.

Custom Dashboards

Create personalized dashboards tailored to your workflow:

• Multiple widget types: graphs and value displays
• Chart options: line graphs and bar charts
• Metric selection: choose exactly what to monitor
• Per-host filtering: focus on specific servers
• Drag-and-drop organization

Advanced Alerting System

Set up intelligent alerts that notify you before problems escalate:

• Metric conditions: Greater than, less than, equal to
• Time windows: 2 minutes to 24 hours
• Notification channels: Email, Slack, Discord, generic webhooks
• Alert muting: Silence known issues during maintenance
• Cooldown periods: Prevent notification storms
• Per-alert subscribers: Route alerts to different teams

For protecting your NGINX from abuse that might trigger alerts, consider implementing rate limiting alongside your monitoring.

Configuration History

Track every NGINX configuration change:

• Automatic snapshots on modification
• Git-like diff view between versions
• Checksum-based duplicate detection
• Historical rollback reference

API Access

Programmatic access to all your monitoring data:

• RESTful JSON API
• Metrics series queries
• Bulk data retrieval
• API key authentication with rate limiting

Pricing Plans

GetPageSpeed Amplify offers a free tier for personal use and paid plans for growing teams:

Annual billing saves approximately 17% ($90/year for Starter instead of $108).

Self-Hosted Option

For organizations requiring complete data sovereignty, GetPageSpeed Amplify can be self-hosted:

• Single binary deployment: No containers, no external dependencies
• SQLite database: Minimal infrastructure overhead
• Zero external services: Everything runs in one process
• Your data, your servers: Complete privacy and control

Contact GetPageSpeed for self-hosted licensing.

Why Choose GetPageSpeed Amplify Over Other Solutions?

Compared to Datadog, New Relic, or Dynatrace

Enterprise monitoring platforms cost hundreds of dollars per month and require significant setup:

Compared to Prometheus + Grafana

Open-source stacks require operational expertise:

Compared to Netdata

Netdata is excellent for real-time visualization but lacks:

• Historical data retention beyond 24 hours
• Website monitoring
• NGINX configuration security analysis
• Multi-server aggregation
• Team collaboration features

Installation on Fresh Servers

If you’re setting up monitoring on new servers (not migrating from NGINX Amplify), use the install script:

curl -sS -L -O https://amplify.getpagespeed.com/install.sh && 
API_KEY='YOUR_API_KEY' sh ./install.sh

The script automatically:

• Detects your operating system (RHEL/CentOS/Rocky/AlmaLinux, Debian, Ubuntu)
• Installs the amplify-agent package
• Configures the agent with your API key
• Starts the agent service

After installation, your server will appear in the GetPageSpeed Amplify dashboard within seconds.

Enabling PHP-FPM Monitoring

To monitor PHP-FPM pools, enable the status page. For detailed PHP-FPM tuning, see our guide on NGINX FastCGI keepalive connections.

Configure PHP-FPM

Edit your pool configuration (e.g., /etc/php-fpm.d/www.conf):

pm.status_path = /php_fpm_status

Configure NGINX

Add a location block to serve the status page locally:

location = /php_fpm_status {
    include fastcgi_params;
    fastcgi_pass unix:/run/php-fpm/www.sock;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    allow 127.0.0.1;
    deny all;
}

Restart both services:

sudo systemctl restart php-fpm nginx amplify-agent

Enabling MySQL Monitoring

The agent monitors MySQL via the performance schema:

Create Monitoring User

CREATE USER 'amplify'@'localhost' IDENTIFIED BY 'secure_password';
GRANT PROCESS, REPLICATION CLIENT ON *.* TO 'amplify'@'localhost';
GRANT SELECT ON performance_schema.* TO 'amplify'@'localhost';
FLUSH PRIVILEGES;

Configure the Agent

Edit /etc/amplify-agent/agent.conf:

[mysql]
user = amplify
password = secure_password
unix_socket = /var/lib/mysql/mysql.sock

Restart the agent:

sudo systemctl restart amplify-agent

Troubleshooting

Agent Not Reporting

Check the agent log:

sudo journalctl -u amplify-agent -f

Common issues:

• API key incorrect: Verify in /etc/amplify-agent/agent.conf
• Firewall blocking: Ensure outbound HTTPS (443) is allowed
• NGINX stub_status not configured: Agent needs access to NGINX metrics

Missing NGINX Metrics

Ensure NGINX stub_status is enabled:

server {
    listen 127.0.0.1:80;
    server_name localhost;

    location /nginx_status {
        stub_status;
        allow 127.0.0.1;
        deny all;
    }
}

Reload NGINX:

sudo nginx -t && sudo systemctl reload nginx

High Memory Usage

The agent is lightweight, but if you notice issues:

# Check agent memory usage
ps aux | grep amplify-agent

# Restart to clear any accumulated state
sudo systemctl restart amplify-agent

Security Considerations

Network Security

The agent makes outbound HTTPS connections only:

• No inbound ports required
• All data encrypted in transit
• API key authentication

Data Privacy

GetPageSpeed Amplify collects:

• Server metrics (CPU, memory, disk, network)
• NGINX access/error log statistics (not raw logs)
• NGINX configuration (for security analysis)
• PHP-FPM and MySQL performance metrics

GetPageSpeed Amplify does not collect:

• Raw access logs or user data
• Application-level data
• Database contents
• File system contents

For complete data sovereignty, use the self-hosted option.

Conclusion

The shutdown of NGINX Amplify created a monitoring gap for thousands of NGINX users. GetPageSpeed Amplify fills that gap as the best NGINX Amplify alternative available:

• Zero-friction migration: Same agent, one config change
• Enhanced features: Website monitoring, Gixy security analysis, custom dashboards
• Flexible pricing: Free tier for personal use, affordable paid plans for teams
• Self-hosted option: Complete data control when required

Don’t let F5’s decision leave your servers unmonitored. Migrate to GetPageSpeed Amplify today and get even better visibility into your NGINX infrastructure.

Get started free at amplify.getpagespeed.com