Feature Matrix
This page provides a comprehensive view of what Airdress supports today and what is on the roadmap, broken down by platform, installation method, protocol, and operator feature.
Platform support
Section titled “Platform support”| Platform | Operator CLI | Tunnels | DNS Server | Reverse Proxy | Plugins | Mini-apps | Chat |
|---|---|---|---|---|---|---|---|
| Linux x86_64 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Linux ARM64 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| macOS x86_64 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| macOS ARM64 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Windows x86_64 | ✅ | ✅ | 🔜 | 🔜 | 🔜 | 🔜 | 🔜 |
Installation methods
Section titled “Installation methods”| Method | Linux x86_64 | Linux ARM64 | macOS x86_64 | macOS ARM64 | Windows x86_64 |
|---|---|---|---|---|---|
Shell installer (curl | sh) | ✅ | ✅ | ✅ | ✅ | ❌ |
| Manual download | ✅ | ✅ | ✅ | ✅ | ✅ |
| deb package | ✅ | ✅ | — | — | — |
| rpm package | ✅ | ✅ | — | — | — |
| Homebrew | 🔜 | 🔜 | 🔜 | 🔜 | — |
| Scoop | — | — | — | — | 🔜 |
| Docker | 🔜 | 🔜 | 🔜 | 🔜 | 🔜 |
The shell installer is the recommended method for macOS and Linux. It detects your OS and architecture automatically, downloads the latest stable binary, and verifies the SHA-256 checksum.
On Linux, the installer also offers .deb and .rpm packages when a supported package manager is detected.
Quickstart Install the operator and expose your first service in under five minutes.
Protocol support
Section titled “Protocol support”All protocols listed below are supported on every platform where the corresponding feature is available.
| Protocol | Port | Status | Notes |
|---|---|---|---|
| WireGuard | 51820 | Available | Tunnel transport |
| HTTP | 80 | Available | Relay inspects Host header for routing |
| HTTPS / TLS | 443 | Available | Passthrough — operator terminates TLS |
| DNS (UDP) | 53 | Available | Authoritative queries |
| DNS (TCP) | 53 | Available | Large responses, zone transfers |
| WebSocket | 80/443 | Available | Ingress events |
| SSE | 80/443 | Available | Chat, ingress events |
Protocol Support Detailed protocol reference including message formats and behavior.
Operator features
Section titled “Operator features”| Feature | Status | Description |
|---|---|---|
| Embedded Database | Available | Bundled with the operator binary. No external database required. |
| External Database | Available | Connect to your own PostgreSQL instance via database.url. |
| Reverse Proxy | Available | HTTP/HTTPS proxy routing to local services. |
| Health Probes | Available | Configurable health checks for upstream services. |
| OIDC Auth | Available | OpenID Connect authentication for protected endpoints. |
| Ingress (webhooks) | Available | Receive webhooks, SSE, and WebSocket connections from the internet. |
| App Runtime | Available | Host and run plugins and mini-apps. |
| Mini-apps | Available | Lightweight web applications served by the operator. |
| Chat | Beta | SSE-based messaging with MLS (RFC 9420) end-to-end encryption. |
| Circuit Breaker | Beta | Automatic upstream failure detection and recovery. |
| Rate Limiting | Beta | Request rate limiting per service. |
| Federation | Beta | Connect operators to each other for cross-instance communication. |
| DNSSEC | Available | DNS responses are signed at the authoritative DNS PoPs. |
| Plugins | Available | Extend operator functionality with installable plugins. |
Limits
Section titled “Limits”During the pre-billing phase, limits are soft and configurable. The defaults are designed to support typical development and small-production workloads without restriction.
| Limit | Default | Notes |
|---|---|---|
| Airdress names per account | 5 | Soft limit, contact support to increase |
| Concurrent tunnels | 3 | Per operator instance |
| Request size | 10 MB | HTTP body limit at the relay |
| Tunnel bandwidth | Unmetered | Fair-use during pre-billing |
Network Architecture How anycast routing, relay PoPs, and WireGuard tunnels work together.