iii: what it is, what problem it solves & why it's gaining traction

What it solves

iii is a shared runtime that replaces point-to-point integrations between backend services. It simplifies the process of adding new capabilities (like queues, cron jobs, and observability) to a software stack by collapsing them into a single live system surface, reducing the need for separate vendor integrations and configuration.

How it works

iii uses three core primitives to manage services:

• Workers: Processes (written in Node.js, Python, Rust, or Go) that register with the engine and provide specific functions.
• Functions: Stable, identifiable units of work (e.g., orders::validate) that exist within workers.
• Triggers: Declarative rules that define when a function should run, such as an HTTP endpoint, a cron schedule, or a queue subscription.

This architecture allows developers and AI agents to discover and call functions across the system in real time. Agents can even add new workers to extend the system's capabilities at runtime.

Who it’s for

• Platform teams who publish workers to provide infrastructure capabilities.
• Application teams who that register functions and declare triggers.
• AI agent developers who want their agents to be able to discover, use, and extend the system's capabilities via a shared catalog.

Highlights

• Zero-integration surface: Add capabilities via iii worker add instead of manual vendor setup.
• Multi-language support: SDKs available for Node.js, Python, Rust, and Go.
• Agent-ready: Includes agent-readable reference material ("skills") and allows agents to add workers at runtime.
• Integrated observability: Built-in console for inspecting traces, logs, and real-time state.