Download websites that use Angie

About Angie

Angie exists because of a corporate event rather than a technical gap. The server is a fork of an established web server, started in 2022 by engineers who had worked on the original and who wanted development to continue on a different footing after the ownership and priorities of the parent project changed. The code stays deliberately compatible, so an operator can swap binaries and keep the same configuration files, modules and habits.

Compatibility is what makes migration cheap, and cheap migration is what makes the adoption curve worth watching. Auriga maintains the fork and publishes it under a BSD licence, the same permissive family as the parent, so there is no licence barrier to argue about internally. The additions are the sort of thing operations teams notice: richer runtime monitoring, finer control over upstream servers, and capabilities the parent project keeps inside its commercial edition. The implementation language is C, inherited with the rest of the codebase, which matters mainly because it places the fork in the same performance and vulnerability class as its parent.

As of September 2026 the server answers for 87,111 sites, and 56,529 of those sit in Germany, with .com the common suffix. Concentration on that scale is almost never a story about individual site owners. Web servers get chosen by hosting companies, and one provider standardising its fleet on a new build moves an entire block of domains at once without a single customer making a decision. Reading a hosting technology as a measure of developer preference is the standard mistake, and the country distribution here is a good illustration of why.

Version data supports the same reading. We record 33 releases in circulation, with 1.12.1 the build current installs report, which is a tight spread for an install base of this size, and tight spreads are what fleet deployments look like. Independent operators upgrade on their own schedules and smear the distribution across many releases. A provider pushes one build everywhere and produces a spike.

Detection depends on the server naming itself in a response header, and a header is trivial to change. Some operators set it to the parent project's name for compatibility or discretion, some blank it out, and any site behind a caching network answers with the network's header instead of the origin's. The count is a floor, and it under-represents exactly the careful operators most worth knowing about.

For a researcher the value of the full list is that it makes a migration visible while it is still happening. A young fork spreading through hosting fleets is a measurable event, and measuring it needs every domain, grouped by network and country, compared against the parent project's own population over time. Checking a single domain tells you which binary answers on one host. Infrastructure vendors, security teams tracking a new codebase and analysts watching a market split along political lines all need the population instead.