Angie: nginx 1.31.2 as the base, with two Mercurial files left in a Git tree
Angie - drop-in replacement for nginx
At a glance
- What is it?
- Angie is a C fork of nginx positioned as a drop-in replacement, so existing module layouts and configuration carry over. Its README is reStructuredText, its documentation lives on a separate site in five languages, and its differentiators are HTTP/3 on both sides, DoH and least-time balancing.
- Who is it for?
- Angie is worth a look for an operator who wants the nginx configuration language and module layout unchanged but needs something nginx does not yet offer, and the page is unusually specific about which of those are real differences rather than reimplementations. Three things to weigh before switching.
- Can I use it commercially?
- Yes. BSD-2-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- webserver-llc/angie2,618 ★ · +42
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| webserver-llc/angie | 2.6k | 2.6k |
42 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The readme is reStructuredText while the build is nginx's own layout
The file at the root is README.rst, not a Markdown readme, and it is written in reStructuredText throughout. The logo is an image directive with alt text and a target, and the section headings are underlined with equals signs, then dashes, then tildes, at three levels. That is consistent with the rest of the tree, which is nginx's own layout: a configure script at the root, an auto directory beside it, conf, contrib, src, html, man, misc and tests. So the documentation format and the build system both match upstream rather than the more common convention of a Markdown readme and a different toolchain. The one thing the repository does not hold is the documentation itself. Everything a user needs is on a separate site published in five languages, English, Russian, Chinese, Spanish and Portuguese, with each of four topics offered in all five, which comes to twenty links in the getting started section alone. A docs directory does exist at the root of the tree, and the readme does not point into it.
Two Mercurial metadata files sit in a Git repository
The root listing opens with .gitignore, followed by .hgignore and .hgtags. Those last two are Mercurial artefacts: one is an ignore file for that version control system and the other is its tag list. They are present in a repository whose branches, releases and commit history are all Git, so they describe a version control system this project does not use. Nothing on the page mentions them and nothing appears to read them. They are the kind of file that arrives with a fork and stays because deleting it would look like a change to somebody's tooling, and they are worth removing if you are reading the tree to work out what is actually live.
The fork point is 1.31.2, which is a mainline version rather than a stable one
The feature list is introduced by saying that everything is on top of all the capabilities of a specific upstream nginx version, 1.31.2, with a link to nginx's own change log. That matters because 1.31.2 is the development line rather than one of the even-numbered stable branches, so the base moves often and any comparison of behaviour has to name the version it was made against. The tag naming differs from upstream too: releases here are prefixed with the project name, as Angie-1.12.2, where nginx tags carry the nginx prefix. Three releases are listed, and two of them sit within three days of each other in July 2026, with the third following in September. The root carries two changelog files, one plain and one suffixed for Russian, which is the same bilingual pairing as the documentation site and the only place in the tree where two languages are represented by filenames rather than by subdirectories.
The HTTP/3 claim is that both sides can choose a version independently
HTTP/3 is described as production ready for client connections and for proxied server connections alike, and the capability claimed is not HTTP/3 itself but independence: HTTP/1.x, HTTP/2 and HTTP/3 can be selected separately on the two sides of a proxy. The page then says what nginx does instead, which is that its HTTP/3 is limited to the server side, is still described as experimental, and degrades after reloads, with a link to an article on that. So the difference being sold is a symmetric one, and the criticism of nginx is specifically about reload behaviour rather than about protocol support in general.
DoH, MQTT pre-read and RDP cookies are three separate modules
Beyond HTTP the connectivity list is a set of narrowly scoped additions. A built-in DNS over HTTPS server module implements RFC 8484, accepting queries over HTTP and HTTPS and proxying them on to DNS server groups over UDP or TCP, so name resolution moves into the same process as the web server rather than sitting beside it. PROXY Protocol V2 is supported with arbitrary TLV values passed through. Two more entries are about making balancing decisions from protocols that nginx cannot read: an extension of authorization and balancing for MQTT through a pre-read module, and a module that reads the RDP protocol's session cookies so a client can be returned to the same session. The mail proxy gains two authentication methods, XOAUTH2 and OAUTHBEARER.
Automatic certificates cover wildcard and IP names through built-in ACME
Automatic HTTPS provisions certificates without an external client, covering multiple domain names, wildcards and bare IP addresses. The challenges are HTTP, DNS and ALPN, and the module also supports ACME profiles and External Account Binding, which is what commercial certificate authorities require. Two TLS features are extended past nginx. Early data for TLS 1.3, the 0-RTT mode, is available in both the HTTP and the stream modules where nginx supports it only for HTTP, so a stream proxy can send early data too. Session binding works the same way in both, with a learn mode that detects sessions automatically and a drain mode for taking a server out of rotation gracefully, plus the slow_start directive for bringing a failed server back.
NTLS is a build-time choice tied to a forked TLS library
The one feature on the page that cannot be turned on in a configuration file is NTLS support, available on both the server and the client side of a proxy. It is enabled when the server is built against the Tongsuo TLS library, and the page links to that project for the library and to the source build documentation for the flag. So an operator who wants it needs a separately compiled binary, and one who does not never sees the directives. This is the only entry in the feature list that changes the build rather than the configuration, and it is also the only one that depends on a third-party fork of a foundational library.
Least-time balancing is argued directly against nginx's least connections
The load balancing entry is the longest argument on the page. Selection is based on the average response time of each upstream, using a probability based algorithm rather than a fixed weight: faster servers attract proportionally more traffic, a configurable smoothing factor suppresses spikes, and the claim is that no server is ever starved. The page says manual weights are unnecessary and adds that they would not make sense, since distribution is derived from measured response times instead of declared ones. The comparison drawn is that nginx's approach amounts to least connections with a time based adjustment rather than a genuinely response time aware algorithm. Elsewhere in the same section, upstream groups can be updated from events and labels published by Docker containers or Podman, with no server reload involved. The last feature group on the page moves to observability, describing a RESTful API that reports basic information about the server and its configuration, alongside metrics for proxied servers, client connections, shared memory zones and TLS certificates.
Editorial conclusion
Angie is worth a look for an operator who wants the nginx configuration language and module layout unchanged but needs something nginx does not yet offer, and the page is unusually specific about which of those are real differences rather than reimplementations. Three things to weigh before switching. Every advantage listed is framed as being on top of nginx 1.31.2, so the fork point is a moving target and an upgrade means tracking upstream nginx as well. The HTTP/3 and least-time claims are comparisons the page makes about nginx's own behaviour, not measurements presented side by side, so they are worth checking against your own traffic. And the NTLS support is a build-time decision tied to a forked TLS library, so it is a different binary rather than a configuration switch.
Frequently asked questions
What is Angie the web server?
A fork of nginx written in C and released under BSD-2-Clause, positioned as a drop-in replacement so existing module layouts and configuration carry over. It was conceived by former members of the original nginx team.
Which version of nginx does Angie build on?
The page says everything is on top of the capabilities of nginx 1.31.2, which is the upstream development line rather than a stable branch, and links to nginx's change log.
Does Angie support HTTP/3?
Yes, for client and proxied server connections, and the two sides can use different protocol versions independently. The page says nginx's own HTTP/3 is server-side only, remains experimental and degrades after reloads.
How does Angie distribute load across upstream servers?
By average response time, with a probability based selection, a configurable smoothing factor for spikes, and the claim that no server is starved. Manual weights are described as unnecessary since distribution follows measured performance.
How does Angie issue TLS certificates automatically?
Through a built-in ACME module covering multiple domains, wildcards and IP addresses, with HTTP, DNS and ALPN challenges, plus ACME profiles and External Account Binding for commercial authorities.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/webserver-llc-angie)Star history chart for your README
[](https://hysenlabs.com/projects/webserver-llc-angie)Was this useful?