Free APT repository · Open-source project · No registration
NGINX and Angie packages for Debian and Ubuntu
40+ source packages, with HTTP/3, mail services and web application firewall tools ready to install. This free APT repository for NGINX and Angie gives Debian and Ubuntu administrators builds with features and modules beyond the standard distribution packages.
An APT repository for NGINX, Angie and the rest of your stack
Choose a web server, add the modules your application needs, and manage updates through APT. The repository also covers the mail and security services around it, so you can follow one set of installation guides across the stack.
// performance
HTTP/3 and modern TLS
NGINX and Angie use openssl-nginx, a dedicated OpenSSL 4.0 build with QUIC support. NGINX also uses zlib-ng. The HTTP/3 setup guide covers the configuration and network checks needed after installation.
We package upstream releases for Debian and Ubuntu rather than waiting for the distribution’s next major release. Check the changelog for actual updates and the package list for availability. Review changes before upgrading a production service.
// security
Security tools with setup guides
Build a WAF with ModSecurity and the OWASP Core Rule Set, add Snuffleupagus hardening for PHP-FPM, or use hardened OpenSSH on Debian 13 and Ubuntu 26.04. Each tool has its own configuration and compatibility requirements.
// containers
Containers from the same packages
The NGINX and Angie images are rebuilt nightly with modules compiled in. Use the Kubernetes guide for deployment details, or install the packages directly when you manage the host yourself.
// trust
Signed metadata and clear provenance
APT verifies signed repository metadata and checks package hashes against that metadata. The signed-by setting scopes the repository key to its source entry. Read the installation and pinning guide before replacing distribution packages. A signature verifies origin and integrity, not suitability for your server.
Articles and practical server guides
The articles explain how the packages fit together, what to configure after installation and how to investigate failures. Start with the task you need to finish. Each guide links to the relevant tools and settings.
Compare the servers, set up a reverse proxy and work through TLS and HTTP/3 configuration. These guides explain the settings behind the install commands.
Set up a mail server with Postfix and Dovecot and filter spam. Understand where Rspamd and attachment scanning fit into the process and which part to look at when mail delivery fails.
Configure a WAF and review container privileges. The guides explain how these controls fit into a deployment and where their limits are, with configuration details you can apply to your own setup.
Browse the main web, mail and security packages below. The full package list is the reference for available packages; the distribution notes explain release and architecture coverage.
We develop and maintain these NGINX and Angie modules alongside the repository. They cover compression, caching, certificate management and request filtering. Each has a guide and source repository, so you can check its behaviour before adding it to a server.
// compression
zstd-nginx-module
Our fork of the Zstandard compression module, with several upstream bugs fixed and clean builds against current NGINX and Angie. What we fixed · What zstd is · GitHub
// abuse
error-abuse
Bans clients that flood you with 403, 404 or 5xx responses, fail2ban-style but inside NGINX. Sliding-window counters in shared memory, with optional cluster-wide bans through Redis or Valkey. Guide · GitHub
// cache
cache-turbo
A page cache inside NGINX itself, so you don’t need Varnish or a second daemon. Stale-while-revalidate, L0, L1 and L2 tiers and single-flight refresh. Guide · GitHub
// tls
autocert
Gets and renews TLS certificates over ACME from inside NGINX, so Certbot and its cron job can go. Guide · GitHub
// shield
http-shield
Blocks probes for ancient exploits cheaply, without running a full WAF. Guide · GitHub
// minify
strip-filter
Minifies CSS and JavaScript as NGINX serves it, for apps that ship unminified assets. Guide · GitHub
A complete WAF stack for NGINX and Angie: the ModSecurity v3 engine, the OWASP CRS, and our own CRS plugins for apps we self-host. The plugins also run on Apache with mod_security2. If you’d rather not use ModSecurity, Coraza runs the same CRS rules.
Over 100 rules tuned for WordPress: typed-parameter SQLi blocking, rate limiting, GeoIP and an XML-RPC lockdown, all enforced before PHP starts. Guide · GitHub
Mail security, container images and open-source tools
The repository is part of a wider set of tools we use to run web and mail infrastructure. Explore the projects below, or use the project directory to find source repositories and images.
Mailstrix unpacks mail attachments and scans them with YARA rules. It supports integrations with Rspamd, SpamAssassin, Dovecot Sieve and ICAP. The Mailstrix guide explains the scanning path; the Olefy guide covers Office macro scanning.
Choose the service you want to run first, then install the modules and security controls it requires. Installing packages is the start of configuring your system, not a finished production deployment.
A web server or reverse proxy
Start with nginx or angie. Angie includes native ACME certificate management; NGINX has a broad module ecosystem. Read the Angie migration guide before switching an existing installation. Add compression, caching or a WAF when you know which traffic and applications they will handle.
A mail server
Postfix is a mail transfer agent, Dovecot provides mailbox access and Sieve filtering and rspamd-git provides spam filtering. The mail server setup guide puts them all together. Plan DNS, certificates and authentication as part of the deployment.
A smaller self-hosted service
Install the packages your application needs rather than the whole catalogue. The nginx-minimal guide describes a smaller web server build, and the Vaultwarden guide shows how to run a self-hosted application behind a reverse proxy.
Built for the infrastructure we run
The repository began with packages we needed for our own web and mail servers. Maintaining the builds made it possible to publish the packages, then document the configuration around them. When an upstream module needed fixes, we maintained a fork; when a feature was missing, we developed a module. The zstd module history is one example.
Builds cover Debian 11, 12 and 13, and Ubuntu 22.04, 24.04 and 26.04. Availability depends on the package, release and architecture; check the package list before planning a migration.
Green = current/recommended. Builds cover amd64 (x86-64) and arm64 (aarch64); Debian 11 gets a smaller set, with NGINX, Angie, Postfix and Dovecot on amd64 only. Curious about the next Debian release? Here’s what to expect from Debian 14 (Forky).
Quick start
Add the repository, update APT’s package index, then install the service you need. Run package-management commands with root privileges. On an existing server, take a configuration backup and review APT’s proposed changes before confirming an upgrade.
Need manual setup or APT pinning? Use the full setup guide. Moving from nginx-full or nginx-light? Read the package migration guide before changing variants.
Before upgrading a production server
Check the changelog and the guide for the service you are upgrading. Review package replacements, module compatibility and local configuration changes. Keep a tested rollback path and validate the service configuration before restarting it. APT pinning controls which repository wins; it doesn’t test an application’s behaviour for you.