arizuko › components
components
An arizuko deployment is a handful of small programs, each doing one job. A daemon is one such program that runs in the background. The core daemons ship in every instance; channel adapters connect outside platforms like Slack or Telegram, and an instance runs as many as it needs. Each row links to that program’s page.
Core
| name | role |
|---|---|
| routd | routing plane — message loop, resolves event→group, hosts the agent MCP socket, owns routd.db and the grant/ACL authority. See concepts/routing |
| runed | execution plane — spawns and tears down the per-turn agent container; the only daemon wired to the Docker socket; owns runed.db |
| authd | auth plane — mints and verifies tokens, OAuth provider routes, owns auth.db. See concepts/auth |
| webd | web channel — SSE hub, the route-token URLs, MCP endpoint |
| proxyd | auth-gated reverse proxy — verifies JWTs, signs identity headers for backends |
| vited | static origin — Vite server behind proxyd for the /pub/ docs tree and group web pages |
| dashd | operator dashboard — browse groups, grants, messages in a browser |
| onbod | onboarding daemon — admission queue, invite tokens, OAuth handshake |
| timed | scheduler — cron and interval tasks, writes scheduled messages to the DB |
| ttsd | text-to-speech proxy — OpenAI-compatible endpoint for voice replies |
| davd | WebDAV workspace browser — mount a group’s folder in a file manager |
| route tokens | /chat/<token>/ visitor chat + /hook/<token> webhook ingest, both served by webd |
| crackbox | the box the agent runs in — containment boundary; egress only through a host allowlist |
Channel adapters
| name | role |
|---|---|
| channels | overview — shared shape, common HTTP surface, how to add a new adapter |
| slakd | Slack — Events API listener, bot user, threaded replies |
| teled | Telegram — bot API, groups and DMs, voice and media |
| discd | Discord — gateway client, server channels, threads |
| mastd | Mastodon — streaming API, mentions, replies |
| bskyd | Bluesky — AT Protocol firehose, posts and replies |
| reditd | Reddit — subreddit and inbox polling, comments and DMs |
| emaid | email — IMAP inbound, SMTP outbound, threading by message-id |
| linkd | LinkedIn — messaging API, connection-scoped DMs |
| whapd | WhatsApp — TypeScript adapter on Baileys, QR or pairing-code login |
| twitd | X / Twitter — TypeScript adapter, mentions and DMs |
See README.md for the daemon + library table that drives this page, and ARCHITECTURE.md for how the pieces fit.