NGINX is dead? Angie migration — what the F5 split actually means for your reverse proxy

Christian Lempa’s March 27 video — “NGINX is Dead? // Angie Web Server Migration Guide” — walks through migrating from NGINX to Angie, a fork built by former NGINX engineers after F5’s 2022 Russia exit left a gap in the support/maintenance pipeline.

Lempa’s title hedges with a question mark, and he’s right to. NGINX isn’t literally dead — F5 still ships it, the codebase still works. But the center of gravity has shifted: the original NGINX engineering team is now elsewhere, Angie is moving faster on features that NGINX has historically dragged on (native ACME, Prometheus metrics, Docker upstream discovery), and the question of “which fork represents the future of NGINX-style reverse proxies” is now actually open.

What Angie ships that NGINX doesn’t

From Lempa’s walkthrough and the Angie docs:

• Native ACME / Let’s Encrypt support. No more certbot, no more renewal cron jobs, no more sidecar containers. Built into the proxy.
• Native Prometheus metrics. No more nginx_exporter. Metrics endpoint built in.
• Docker upstream discovery. Auto-discovers backend services by Docker labels — closer to Traefik’s ergonomics, with NGINX’s familiar config syntax.
• NGINX config compatibility. Existing NGINX configs work largely unchanged. Migration is the lowest-risk path of any “switch reverse proxies” decision in 2026.
• DNS challenge support for wildcard certs — a feature NGINX has long required external tooling to handle.

This is the kind of feature set that has been on the NGINX wishlist for 5+ years. Angie shipping it is what the headline question is really about: “NGINX is dead” reads as “NGINX hasn’t shipped the features its own users have been asking for, and the engineers who would have built those features are now building them elsewhere.”

The geopolitical wrinkle

The most uncomfortable thread on r/selfhosted (17 upvotes, but high-signal discussion):

“You can’t trust anything that is legally under Russia jurisdiction. Company can be completely honest and trustworthy, but they need to obey Russia jurisdiction which basically mean anything that government wants from them they have to comply.”

This is the elephant in the room. Angie’s parent company (WEBSERVER LLC, the entity that picked up NGINX-Russia after F5’s exit) is Russian-registered. For users in regulated industries, government, or anyone with a compliance posture that excludes Russia-based supply chain, Angie is a non-starter regardless of technical merit.

For homelab and small-business users, this is mostly a non-issue. For enterprise, it’s disqualifying. The choice surface is therefore narrower than the technical comparison suggests.

Creator POV vs Reddit dissent

Lempa’s framing is pro-Angie but qualified: he covers the technical wins (ACME, metrics, Docker discovery), acknowledges the geopolitical concern in passing, and treats Angie as a viable path for self-hosters who care about feature velocity over corporate provenance.

The Reddit dissent breaks into three camps:

• “Performance is about the same; the appeal is convenience features.” Top technical comment in the r/selfhosted thread. Angie isn’t faster than NGINX — it’s more convenient. For users where convenience is the bottleneck, this is enough. For users where performance is the bottleneck, NGINX and Angie are roughly interchangeable.
• “Use Caddy instead.” Caddy gives you most of Angie’s convenience (auto-TLS, simpler config) with a non-Russian provenance and stronger community momentum. Lempa’s own Caddy video implicitly acknowledges this is the bigger competitor.
• “Just stay on NGINX; it works.” The contrarian camp argues NGINX’s pace is fine for stable workloads — if you don’t need ACME or Prometheus or Docker discovery as table-stakes, the upgrade has no payoff.

The honest read: for self-hosters and homelab users in 2026, the practical reverse-proxy choice is now Caddy first, NGINX second, Angie third — with Angie’s specific niche being “I want NGINX config syntax with modern features and I’m OK with the supply chain.”

What this means for working engineers

Three concrete considerations:

1. If you’re starting a new homelab in 2026, default to Caddy. Simpler config, automatic TLS, single binary, strong community. NGINX’s mindshare advantage in 2026 is mostly inertia for new deployments.

2. If you’re running NGINX in production, don’t migrate reactively. NGINX is still maintained by F5; the lights aren’t off. Migrating to Angie for “feature velocity” is a real decision but not an urgent one. Plan it like any infra migration — not a fire drill.

3. If you’re evaluating Angie specifically, audit your compliance posture first. Russian-jurisdiction supply chain is not a hypothetical concern — it has real consequences in regulated industries and may be a hard “no” depending on where you operate.

The honest critique

What this story really illustrates:

• NGINX has become a maintenance project, not a feature platform. Whether or not Angie wins, the fork happened because NGINX wasn’t shipping. That’s the durable signal.
• Reverse proxy is now a commodity decision. In 2026, the practical differences between NGINX, Angie, Caddy, and Traefik for typical small/medium workloads are small. Pick one, learn it well, automate the deploy.
• The Linux Foundation / OSS-foundation gap is real. NGINX is technically open source, but the engineering decisions are made inside F5. Caddy’s foundation model and Angie’s Russian-corporate model are both responses to “where does the governance live?” — a question the broader OSS infra ecosystem keeps having to re-answer.

For most working engineers in 2026: Angie is interesting, Caddy is the safer recommendation, and NGINX is still fine if you’re already there. The “is NGINX dead” question gets a “no — but it’s been moved to maintenance mode” answer, which is more interesting than either extreme.