TRACKER ONLINE

ainode tracker

Swarm rendezvous and advisory planner.

This host is not an HTTP API. The tracker speaks iroh/QUIC over UDP 48010 and authenticates by node id. This page exists only so the hostname explains itself — there is nothing here for a browser to call. The download below is what actually joins the swarm.

Download the desktop app

Installs the node service and joins this swarm. The tracker below is already baked in — nothing to paste.

Download for macOSApple Silicon · 13 MB WindowsBuild pending LinuxBuild pending
Unsigned beta — macOS will block the first launch. You will see “Apple could not verify ‘ainode’ is free of malware” with only a Done button. That is expected: the build is not notarised yet. It is not a damaged download.
  1. Drag ainode into Applications, then open it once and press Done.
  2. Open System Settings → Privacy & Security.
  3. Scroll to Security. There is now a line about ainode — click Open Anyway.
Prefer the terminal, or no Open Anyway button appeared? This does the same thing in one line:
xattr -dr com.apple.quarantine /Applications/ainode.app
On macOS 15 and later, right‑click → Open no longer works — Apple removed that bypass. Use one of the two above.

Tracker id — the whole configuration a contributor needs

0a4c50ca9338d9bada2b3b81763d35f082e729d0603155fdaccfb91fd80fe3ce@api.ainode.world:48010

Join

ainode-ctl catalog --tracker <id>
ainode-ctl start --model <model-id> --tracker <id> --complete

Or paste the id into the desktop app's Tracker field. No --public on the joining side — a tracker named by id is reached through relays, so joining needs no port forwarding.

Endpoint

Transportiroh / QUIC over UDP
Port48010/udp
Plannerenabled (--plan-hints) — advisory; joiners still self-select
Reachability--public — relays and hole punching, NAT traversal both sides
Registryin memory; ads refresh every 20s against a 60s TTL

Health check

ainode-ctl catalog --tracker <id>

An empty catalog is a healthy answer — the tracker replied and nothing has registered yet. No address lookup configured means the id could not be resolved; a timeout means it resolved but could not be reached.