iii-hq /iii
Effortlessly compose, extend, observe, discover, and react to every service in real-time for the first time ever.
★ 18,933⑂ 1,273👁 83⑃ 2,150● 375▤ 401
-2
Daily
+37
Weekly
+94
Monthly
18,933
stars
1,273
forks
83
watchers
2,150
prs
375
issues
401
releases
README
iii
!iii: point-to-point integrations vs zero-integration via shared runtime
What is iii? ·
Install iii ·
Add Workers ·
SDKs ·
Agent Skills ·
Resources
What is iii?
iii is the easiest way to compose, observe, discover, extend, and react (CODER) to every service in
your stack in real time.
Every backend starts as a project before the first line of business logic. Queues, cron, HTTP,
state, observability, agents, and sandboxes each usually bring their own integration story that
complicates CODER. iii solves all of these concerns with one live system surface.
bash
iii compose --namespace dev --up
iii call -n dev compose::add worker=queue
iii call -n dev compose::add worker=agent
iii call -n dev compose::add worker=
Each worker joins the live catalog. Every other worker is notified and can call it immediately.
Browse available workers at workers.iii.dev.
That is the agent story too: when a task needs a capability the system does not have, an agent can
add a worker, discover its functions, call them, and trace what happened. Same interface a developer
uses.
Three Primitives
iii is powered by 3 primitives:
Workers are processes that connect to the iii engine and register functions. A TypeScript API
service is a worker. A Python data pipeline is a worker. A Rust microservice is a worker. Any
functionality can be transformed into a worker with a few lines of code. Compose can also add
workers at runtime, so agents and applications can extend the system while it is running.
Functions are units of work with a stable identifier (e.g., content::classify,
orders::validate). A function receives input, does work, and optionally returns output. Functions
exist in workers, and any worker runs any function with iii.call(), wherever it is.
Observers make the system reactive. iii.observe('orders::create', 'alerts::big-order') means:
when orders::create runs, alerts::big-order runs. Every function can be observed, including the
ones workers provide for events: an HTTP request is a call of http::on-request, a cron tick is a
call of cron::on-tick, and a queue message is a call of queue::on-message. iii handles routing,
serialization, and delivery.
By mapping everything a service can do to these three primitives iii creates a development process
that is both effortlessly composable, and completely observable.
What Changes
Before iii:
- New observability tool: uncountable integrations
- New agent harness: separate retry config, separate traces, separate timeouts
- New queue: vendor evaluation, procurement, and weeks of integration
After iii:
- Declare workers in worker-compose.yaml
- Run them with iii compose --up
- Done. It is in the system, traceable, and callable.
Platform teams publish workers. Application teams register functions and observe the functions they
react to. Agents use the same catalog and the same function calls.
Extending iii is adding a Compose worker. Composing iii iTop issues
#1553iii native Windows installation8 comments · 2026-04-28#2201provider-llamacpp: context window falls back to 4096 on non-llama.cpp OpenAI-compatible servers (SGLang/vLLM) every turn fails with context/overflow5 comments · 2026-09-18#1095Feature: Jump to Trace from Log Details5 comments · 2025-12-19#811Deduplication/Debounce features5 comments · 2025-10-12#1814Support enqueue with custom priority4 comments · 2026-06-09#1723iii worker add mcp fails with missing skills dependency, but config.yaml starts it successfully4 comments · 2026-05-31#2084HTTP trigger disappears after duplicate worker registration is rejected3 comments · 2026-08-25#1744Feature Request: Export Conversation as JSON3 comments · 2026-06-03
Discussions
#2312HA and zero-downtime deployments: roadmap for engine redundancy and worker replicas?3 comments · 2026-10-08#1738Feature Request: Worker isolation / access control between workers1 comments · 2026-06-02#1730iii worker add --force does not invalidate dependency cache when project dependencies change (ex. pyproject.toml, Cargo.lock)3 comments · 2026-05-31#1728`iii worker add` attempts to pull local Docker image from registry2 comments · 2026-05-30#1135Dependency Injection1 comments · 2026-01-15#1134API for create cron scheduling job0 comments · 2026-01-14#1041Low Test Coverage - Blocking Production Adoption0 comments · 2025-12-10#1030Paths0 comments · 2025-12-08
Latest release
iii 0.26.0 iii/v0.26.0 2026-11-09What's Changed docs(changelog): complete 0.25.0 release notes by @guibeira in https://github.com/iii-hq/iii/pull/2383 test(rust): give the oversized result_wire case a 30s budget by @guibeira in https://github.com/iii-hq/iii/pull/2386 fix(python): require websockets=14.0 by @guibeira in https://github.com/iii-hq/iii/pull/2385 fix(deps): update Tokio to address RUSTSEC-2026-0386 by @guibeira in https://github.com/iii-hq/iii/pull/2391 fix(sdk): patch happy-dom and zod security advisories by @guibeira in https://github.com/iii-hq/iii/pull/2400 docs: move Upgrading group to bottom of sidebar