iii

Why we included this project

Most service wiring ends up as a tangle of point-to-point integrations. iii takes a different route: you declare Workers, Functions, and Triggers, and the runtime routes calls between them over WebSocket, so there's no per-pair glue code. For teams building agent-driven backends, that pays off directly. An agent can spin up a worker at runtime, discover its functions, call them, and trace the whole call through the same console a developer uses. Queues, cron, state, pub/sub, and observability come as built-in workers you can add with one command, and the console shows live workers, functions, triggers, and traces. If you'd rather have one composable backbone than a pile of hand-written connectors, iii is worth evaluating.