iii-hq/iii

What it solves

iii simplifies the complex process of integrating multiple backend services, queues, cron jobs, and observability tools. Instead of managing separate integration stories for every tool in a stack, iii provides a shared runtime that collapses these into a single, observable system surface.

How it works

iii operates on three core primitives:

• Workers: Processes (written in TypeScript, Python, Rust, or Go) that register with the engine and provide specific capabilities.
• Functions: Stable, identified units of work within workers (e.g., content::classify).
• Triggers: Declarative events that cause functions to run, such as HTTP endpoints, cron schedules, queue subscriptions, or state changes.

Developers can declare workers in a worker-compose.yaml file or add them at runtime. This allows the system to be extended dynamically, enabling AI agents to add new workers and discover their functions to solve tasks.

Who it’s for

It is designed for platform and application teams who want to effortlessly compose and observe their backend services, as well as developers building AI agents that need the ability to dynamically extend their own system capabilities.

Highlights

• Multi-language SDKs: Supports Node.js, Python, Rust, and Go.
• Dynamic Extension: Agents and applications can add new workers to the live catalog at runtime.
• Unified Observability: Includes a developer console for inspecting traces, logs, and real-time state.
• Agent-Ready: Provides agent-readable reference material (skills) to help AI agents understand and use the engine primitives.