components

arizuko › components

A directory of every daemon in an arizuko deployment. Core daemons ship in every instance. Channel adapters plug platforms in; an instance runs as many as it needs. Each row links to that daemon’s page — some pages are still being written.

Core

namerole
gatedgateway daemon — HTTP API, MCP host, message loop, owns the SQLite schema
webdweb channel — SSE hub, the route-token surface, MCP endpoint
proxydauth-gated reverse proxy — verifies JWTs, signs identity headers for backends
dashdoperator dashboard — browse groups, grants, messages in a browser
onbodonboarding daemon — admission queue, invite tokens, OAuth handshake
timedscheduler — cron and interval tasks, writes scheduled messages to the DB
ttsdtext-to-speech proxy — OpenAI-compatible endpoint for voice replies
davdWebDAV 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
crackboxegress sandbox — allowlist which hosts a workload can reach

Channel adapters

namerole
channelsoverview — shared shape, common HTTP surface, how to add a new adapter
slakdSlack — Events API listener, bot user, threaded replies
teledTelegram — bot API, groups and DMs, voice and media
discdDiscord — gateway client, server channels, threads
mastdMastodon — streaming API, mentions, replies
bskydBluesky — AT Protocol firehose, posts and replies
reditdReddit — subreddit and inbox polling, comments and DMs
emaidemail — IMAP inbound, SMTP outbound, threading by message-id
linkdLinkedIn — messaging API, connection-scoped DMs
whapdWhatsApp — TypeScript adapter on whatsapp-web.js, QR pairing
twitdX / 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.