# Feature matrix

What runs where today. A feature marked preview is switched on per airdress
while it settles.

## Binaries and platforms

| Binary | Linux x86_64 | Linux arm64 | macOS Intel | macOS Apple silicon | Windows x86_64 |
|--------|:---:|:---:|:---:|:---:|:---:|
| `airdress` (the [CLI](/cli/)) | ✅ | ✅ | ✅ | ✅ | ✅ |
| `airdress-agent` ([agent device](/agents/)) | ✅ | ✅ | ✅ | ✅ | — |
| `airdress shell host` ([shell host](/shells/)) | ✅ | ✅ | — | — | — |
| Claude Code plugin ([preview](/editor/claude-code/)) | ✅ | ✅ | ✅ | ✅ | — |

## Installing the CLI

| Method | Linux | macOS | Windows |
|--------|:---:|:---:|:---:|
| One-line installer (`curl -fsSL https://get.airdress.co/cli \| sh`) | ✅ | ✅ | — |
| `.deb` package (amd64, arm64) | ✅ | — | — |
| Single binary from `downloads.airdress.co` | ✅ | ✅ | ✅ |
| `airdress update` (self-update) | ✅ | ✅ | ✅ |

Details and checksums: [Install the CLI](/cli/install/).

## Network: ports and protocols

| Where | Address | Port | Protocol | Notes |
|-------|---------|------|----------|-------|
| Relay PoPs | `23.163.148.11` | 443 | TLS (any protocol on top) | Passthrough by SNI; TLS ends on your airdress |
| Relay PoPs | `23.163.148.11` | 80 | HTTP | Passthrough by `Host` header |
| DNS PoPs | `185.43.32.1` | 53 | DNS over UDP and TCP | Authoritative for `a.airdr.es` |
| Your airdress | its own IPv6 address | 443, 80 | TLS, HTTP | IPv6 clients connect directly |

How the pieces fit: [Network architecture](/reference/architecture/).

## Features of an airdress

An airdress can run on our fleet, created for you at
[airdress.co](https://airdress.co), or on an [operator you run
yourself](/reference/cli/). An airdress we host is being brought to the
same feature set as your own operator, in phases; the table shows where
each feature stands on both.

| Feature | On an airdress we host | On your own operator | Where to start |
|---------|:---:|:---:|----------------|
| Permanent `a.airdr.es` address with TLS | Available | Available | [Quickstart](/getting-started/quickstart/) |
| Functions (TypeScript, JavaScript) | Available (new airdresses)[^new] | Available | [Functions](/functions/) |
| Resources and manifests | Available (new airdresses)[^resources] | Available | [Resources](/cli/resources/) |
| Plugins from the signed registry | Coming | Available | [Plugins](/cli/plugins/) |
| Paired devices (phones, chat clients) | Available | Available | [Devices](/cli/devices-and-machines/#devices) |
| Approved machines | Available (new airdresses)[^new] | Available | [Machines](/cli/devices-and-machines/#machines) |
| Home Assistant link | Available (new airdresses)[^new] | Available | [Homes](/cli/devices-and-machines/#homes) |
| MCP server (`airdress mcp serve`) | Coming | Available | [Claude Code and MCP](/editor/claude-code/) |
| Shells | Preview (new airdresses)[^new] | Preview | [Shells](/shells/) |
| Agent devices, agent bus, agent chat | Coming | Preview | [Agents](/agents/) |
| Claude Code plugin | Coming | Preview | [Claude Code](/editor/claude-code/) |

An airdress we host also has the Airdress Chat app, its own DNS zone,
custom domains and root recovery, and, from 9 October 2026, push
notifications, push-to-talk, federation with other operators, schedules,
location sharing and things. Still coming to an airdress we host: MCP and
the tools bridge, agents, and plugins, which need a larger machine.

[^new]: For airdresses created from 9 October 2026. Airdresses created
    earlier get these when Airdress re-creates them; you do not need to do
    anything.

[^resources]: For airdresses created from 9 October 2026, as for the rows
    above. Resources that a plugin provides arrive with plugins.