Armada's web app, a Nostr relay, a Blossom server, push notifications, and voice and video calls on a built-in LiveKit, served from one domain by one static binary, with HTTPS from Let's Encrypt and an onion over a built-in Tor. Install it on a Linux server with: curl -fsSL https://armada.buzz/install.sh | sudo sh -s -- armada.example.com See INSTALL.md.
First release: Oct 4, 2026, 13 total releases.
Most recent release: Nov 20, 2026.
Appears in 0 app stacks.
0 sats / 0 zaps received in the past year.
Sats Received
Underlying data available via MCP: app_zaps, app_releases.
Zap Count
Underlying data available via MCP: app_zaps, app_releases.
Releases
- Nov 20, 2026 0.10.0- `web.dir` serves the web app from a directory on this machine instead of the nsite, such as a build of your own, and Nostr isn't asked for it. With `auto_update` on, the directory is watched, and a change goes live once it has held still for a couple of seconds.
- Nov 19, 2026 0.9.0- `armada ban --user <npub>` bans one person on their own: armada takes nothing more signed by them, deletes what they published and uploaded here, and puts them on this server's blocklist as a user, so the app served here hides what it has of theirs behind tombstones and won't open their profile. `armada unban <npub>` lifts it. - The app served here names this armada in the NIP-89 `client` tag on what it signs: `APP_NAME` from `[web.env]` if set, else the host, never the onion. `CLIENT_TAG` under `[web.env]` replaces it, and `""` turns it off. - The relay takes NIP-13 `nonce` tags on gift wraps, NIP-46 and push requests, so a mined envelope isn't refused.
- Oct 20, 2026 0.8.0- `armada ban` puts the community on this server's blocklist, so the app served here won't open or join it, and `armada unban` lifts it. Entries are signed with a moderation key armada makes on first start; the relay takes them from that key alone, and the app is pointed at it through `BLOCKLIST_AUTHORS`, beside Soapbox's. - `armada ban --members` bans everyone in the community too, by their own keys, and deletes what they published and uploaded here. Members come from the community's guestbook and whoever posted in its channels, less those the community banned itself. `armada unban` with the link lifts them too. - `armada ban --relay <url>` reads the community from another relay as well
More…
as the link's and its own. - Oct 18, 2026 0.7.0- `armada ban <invite link>` takes a Concord community off the server. The link's keys give the community's addresses: its control plane, guestbook, channels, and other invite links. armada bans those keys, deletes what they published, and deletes Discover posts sharing the community's links and the Blossom blobs its icon, banner and messages point at. `--dry-run` shows what it would do, `armada ban --list` what's banned, and `armada unban` lifts a ban. See "Taking a community down" in INSTALL.md.
- Oct 13, 2026 0.6.0- The onion address stays reachable. Arti, the Tor built into armada, now comes from Soapbox's fork with two fixes: choosing relays no longer costs ~0.4 s of CPU each, which starved Tor's other work until its circuits timed out, and a descriptor upload waits long enough for slow directory relays instead of giving up on them every time, which left the address unpublished for many clients. - The `.deb` and `.rpm` files are named `armada-stack-X.Y.Z-linux-ARCH`, after the package, rather than `armada-X.Y.Z-linux-ARCH`. - install.sh is a short shell script, with no Python. On Debian, Ubuntu, Fedora, RHEL and their relatives it adds the `armada-stack` repository at
More…
pkg.soapbox.pub and installs the package, so upgrades come with the system's. It no longer installs the binary anywhere else: without apt 2.3.10 or dnf, install armada by hand, as INSTALL.md says, and upgrade it with `armada upgrade`. It no longer takes `--version`: use `armada upgrade --version`. - Oct 9, 2026 0.5.10.5.0 was withdrawn; this is its replacement. - Releases have `.deb` and `.rpm` packages, named `armada-stack`, beside the binaries. They install armada at `/usr/bin/armada` with its user, unit and UDP buffer limits, and a config to set `public_url` in. See "From a package" in INSTALL.md. `armada upgrade` and `install.sh` leave a packaged armada to its package manager, and pick the plain binary over the packages. - Releases no longer have a `SHA256SUMS`: the signed release gives each file's sha256 already.
- Oct 9, 2026 0.5.0- Releases have `.deb` and `.rpm` packages beside the binaries, which install armada at `/usr/bin/armada` with its user, unit and UDP buffer limits, and a config to set `public_url` in. See "From a package" in INSTALL.md. `armada upgrade` and `install.sh` leave a packaged armada to its package manager, and pick the plain binary over the packages. - Releases no longer have a `SHA256SUMS`: the signed release gives each file's sha256 already.
- Oct 8, 2026 0.4.2- Behind Cloudflare's proxy (the orange cloud), each visitor is limited as itself, by the address Cloudflare names in `CF-Connecting-IP`, rather than every visitor sharing the limits of whichever Cloudflare address it came through. It's believed only from Cloudflare's own addresses, and connections from those aren't capped per address. The built-in LiveKit is told the visitor's address too. `trust_cloudflare = false` turns it off. - Cloudflare's Flexible SSL mode works: Cloudflare's requests to port 80 for visitors on HTTPS are served, where they were redirected to HTTPS, which sent the visitor round in a loop. - A certificate is renewed by whichever challenge worked last. Behind
More…
Cloudflare's proxy, which ends TLS itself, that's HTTP-01, so renewals no longer start with a failed TLS-ALPN-01 validation. - `armada onion`, run by a user who can't read `/etc/armada/armada.toml`, says so and to use sudo, rather than reading no config at all and saying there's no onion address yet. - A certificate that can't be had logs why, as the CA put it, such as "Timeout during connect (likely firewall problem)", rather than only that the CA left the order invalid. - `armada upgrade`, when it needs root, gives the command with the binary's path, `sudo /usr/local/bin/armada upgrade`: sudo on RHEL, Rocky, AlmaLinux and CentOS Stream doesn't search `/usr/local/bin`. - Logs are colored only on a terminal, so the journal has no escape codes in it. - Oct 6, 2026 0.4.1- The built-in LiveKit is told the machine's public address, from its network interfaces, rather than finding it over STUN, which it wouldn't start without: a server that couldn't reach Google's or Twilio's STUN servers had no calls, and restarted LiveKit over and over. Only a machine with no public address of its own, behind a NAT as on AWS or GCP, still uses STUN, and armada warns that it does; set the new `[av] node_ip` there to its public IP. - `armada --help` and the release's description say what armada serves now: push, calls on the built-in LiveKit, and Tor.
- Oct 5, 2026 0.4.0- Calls, built in. armada carries LiveKit 1.13.7 and runs it itself, as the node its AV broker places calls on, so a new server has voice and video with nothing to install. Its signaling goes through armada at `/rtc`; **open 7881/tcp and 7882/udp** for the media. Its key and secret are made on first start, in `livekit/` in the storage directory. `[av] livekit = false` turns it off, and a node in `[[av.nodes]]` on armada's own origin takes its place. It needs `public_url`. The binary is about 20 MB larger. - `window.ENV` gives `CONCORD_AV_SERVERS` as this armada alone, rather than this armada then armada.buzz. - install.sh raises the kernel's UDP buffer limits for LiveKit, in
More…
`/etc/sysctl.d/60-armada.conf`. The service unit no longer hides the rest of `/proc` (`ProcSubset=pid`), which LiveKit reads the machine's load from; install.sh installs the new unit, or copy `deploy/armada.service` in. - `window.ENV` names the web app's relays and Blossom servers the way Armada now reads them: `RELAYS` and `BLOSSOM_SERVERS`, armada's own first, in place of `APP_RELAYS`, `COMMUNITY_RELAYS`, `APP_BLOSSOM_SERVERS` and `PREFERRED_BLOSSOM_SERVER`. `RELAYS` is every relay the app uses by default, the backups of each user's community and invite lists included, so setting it in `[web.env]` to this relay alone keeps the app off every other relay. Armada's versions from before the change don't read it. **A `[web.env]` that sets the old names does nothing now; rename them.** - Oct 5, 2026 0.3.1- install.sh sets up a new server again. It enabled the systemd unit before copying it in, so on a server without one it stopped, silently, after writing the config. - Until the web app has downloaded, a browser gets an Armada page, with the app's animated crest and ASCII sea, that says how far the download has got and opens the app once it's live, rather than a line of text. Other requests still get the plain 503. It asks `/_armada/status.json`, which says the stage (`searching`, `not_found`, `downloading` with counts, `failed`, or `live`) and never why a deploy failed; that's in the log.
More…
- armada says when Tor has published the onion, and warns when Tor reports a problem with it. Publishing can take several minutes after a start, and until then the onion can't be reached; it used to say it was serving the onion as soon as it launched it. - Oct 5, 2026 0.3.0- Tor, built in, with no tor daemon to install. armada is served as an onion service by default, at an address made on first start; `armada onion` prints it. Its key is `tor/hs_ed25519_secret_key` in the storage directory, in C Tor's format, so back it up to keep the address. Clients that come over the onion are pointed at the onion's relay and Blossom server in `window.ENV`, and aren't offered AV. Pages served over HTTPS send `Onion-Location`. The relay takes requests to vanish naming either of its names. Each Tor circuit counts as one client for the per-address limits, and proxy headers on onion requests are dropped. `[tor] onion_service = false` stops serving the onion; `[tor] enabled = false`
More…
turns Tor off altogether (both on by default). - Relays at `.onion` addresses are reached over Tor, both configured ones and those in an nsite author's relay list, so the site can be followed on relays that are only onions. An author's may be `ws://`. - Building needs Rust 1.92. - The relay's NIP-11 document has an `icon` and a `banner`: Armada's logo and social card, built into the binary and served at `/_armada/icon.png` and `/_armada/banner.png`, whatever site is live. - Blossom uploads and mirrors may ask to expire, with `X-Expiration: <unix time>` (blossom#115), as Armada does for attachments to disappearing messages. It's rounded up to the end of its day. A blob goes once every uploader's claim on it has expired, never while anyone keeps it for good, so an avatar can't vanish because the same bytes were attached to a disappearing message. Its expiration is in the descriptor and in a `Sunset` header, it's not served past it, and an hourly sweep deletes it. Blobs uploaded before, and uploads without the header, are kept as ever. - A built-in Web Push service, `[push]`, on by default. It speaks nostr-push2's protocol (kind 25742), so the web app needs no changes: `window.ENV` points `NOSTR_PUSH2_PUBKEY` and `NOSTR_PUSH2_RELAYS` at it. Its key is made on first start, at `push/key` in the storage directory. It pushes events stored on this relay only: NIP-17 DMs to users whose DM relay this is, and Concord channels hosted here. Group chats and DMs on other relays don't notify. Unlike nostr-push2, it takes only filters for gift wraps, to one `#p` or by `authors`, as Armada sends them; filters only for kinds the relay doesn't store are dropped. `#p` has to be a hex pubkey, and a client's subscriptions may come to at most 60,000 bytes of JSON, so `get` can always answer. Set `NOSTR_PUSH2_PUBKEY` and `NOSTR_PUSH2_RELAYS` in `[web.env]` to keep using another push service. - The relay takes kind 25742, which only filters that name its author or `#p` recipient can read. - A relay query stops once its subscription is closed or replaced, or its connection goes, rather than running to the end for nobody. Each client address may have `relay.max_queries_per_ip` (4) queries running or waiting for a core at once, and a REQ's filters together examine at most 200,000 events, so one client can't keep everyone else's REQs waiting. - Each client address may send `relay.reqs_per_minute_per_ip` (1,200) REQs a minute across its connections. `relay.max_filters` is now 32 by default, down from 100: Armada sends at most 32 in one REQ. `relay.max_subscriptions` is now 64, up from 32, as Armada may open dozens at once at startup. - A REQ's filters may list at most `relay.max_filter_values` (10,000) ids, authors, kinds and tag values between them, and each client address's open subscriptions at most `relay.max_filter_values_per_ip` (200,000), since they're held in memory while open. Armada's largest REQ lists about 5,500. ### Security - Without `public_url`, the relay took its own name from each request's `Host`, so anyone could replay here a NIP-62 request to vanish that its author had meant for another relay, deleting their events. Now it takes only `ALL_RELAYS` requests then. armada warns at startup when `public_url` is unset. - A request to vanish was carried out in full each time it was sent, in the one write transaction, so resending one stalled every write. Now one no newer than a request already taken costs nothing, and a new one is carried out in bounded steps. - One event that couldn't be stored failed every other event in its batch. - A REQ's results are capped at 16 MiB. Clients that stop reading for a minute, or go silent for two, are dropped; so are subscriptions whose query falls 4,096 live events behind. - `relay.event_bytes_per_hour_per_ip` (256 MiB) bounds how fast one client can fill the disk. Every message a connection sends costs one of 3,000 a minute. Matching tags costs queries as examining events does. - An EVENT reusing a stored id with a bad signature was answered as a duplicate, confirming a gift wrap was stored. Signatures must now be lowercase hex. - Every listener — HTTPS, the port-80 redirect, and plain HTTP — now has a 30-second header timeout, which hyper skipped without a timer, and closes connections idle for two minutes. There are at most 32,768 connections at once, and 256 from one address unless behind a proxy. - Blossom uploads time out after 15 minutes, or 30 seconds without data. Every byte received counts against `blossom.upload_bytes_per_hour`, kept or not, and a declared length is held against it while the upload runs. At most 64 uploads and mirrors run at once, 4 per client. Uploads that would leave less than `blossom.min_free_space` (1 GiB) on the disk are refused. Tokens signed more than a day ago are refused, whatever their expiration, and deletes are limited to 120 a minute per client. - The push service takes at most 1,200 new clients an hour, and creates from one endpoint site 120 an hour; all clients' subscriptions may list a million filter values; and pushes to one host are capped at 3,000 a minute, so it can't be aimed at someone else's server. - An `X-Forwarded-For` entry that isn't an address is ignored for the socket peer, and a port on one is dropped. armada says at startup what trusting the header, the default behind a loopback listener, asks of the proxy. - Blob downloads and pushes ignore proxies from the environment, which would resolve names past the check for private addresses. - `/rtc` forwards only plain paths, and drops client-sent headers that would tell the node someone else is the client. - `/_armada/env.js` is `Cache-Control: private` and varies by `Host`. - Failed deploys no longer keep what superseded versions downloaded, and downloads can cross `web.max_site_size` by one file at most, not four. - `armada upgrade` and install.sh no longer install an older release than the one installed unless given `--version`. `armada upgrade` refuses to write the new binary in a directory others can write to. - install.sh makes `/etc/armada/armada.toml` readable only by root and the armada user, as it can hold an AV node's `api_secret`. Run it again to fix an existing install. - The systemd unit is hardened further: a syscall filter, no W^X memory, private devices, and the kernel, `/proc`, and namespaces walled off. `armada upgrade` installs the unit of the binary doing the upgrading, so run it once more after upgrading to this release, or rerun install.sh. - Oct 4, 2026 0.1.0First release: Armada's web app, a relay, a Blossom server, and a Concord AV broker in one binary, with HTTPS from Let's Encrypt. Static builds for Linux on x86_64 and aarch64.