iii-hq/iii

Effortlessly compose, extend, and observe every service in real-time for the first time ever.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 3rd, 2026
Created on January 2nd, 2025
Open Issues & Pull Requests: 73 (+0)
GitHub issues: Enabled
Number of forks: 1,255
Total Stargazers: 18,681 (+0)
Total Subscribers: 92 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.1 hours
Mean response time: 8.2 days
90th percentile: 25.9 days
Tracked items: 330

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "release-failure" is answered fastest, typically in under an hour, while "feature request" waits about 3 days. Only 9% of issues opened in the past year have been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 30
New in 7 days: 4
Closed in 7 days: 4
Avg open age: 71 days
Stale 30+ days: 18
Stale 90+ days: 9

Recent activity

Opened in 7 days: 3
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (89)
  • enhancement (33)
  • high-priority (23)
  • stale (22)
  • medium (20)
  • release-failure (20)
  • feature request (16)
  • documentation (13)

Detailed Description

iii is a service composition engine that enables developers to build distributed systems by composing workers, functions, and triggers into a shared runtime.

The tool addresses the complexity of integrating multiple backend services by eliminating point-to-point integrations. Instead of each service managing its own connections to queues, cron jobs, HTTP endpoints, state management, and observability, iii provides a unified runtime where workers automatically discover and call each other. When a worker is added to the system, other workers are immediately notified and can invoke its functions without additional configuration. This approach extends to agent capabilities: when an agent encounters a task requiring functionality the system lacks, it can dynamically add a new worker, discover its available functions, call them, and trace execution through the same interface developers use manually.

The tool suits teams building microservice architectures or agent-based systems who want to reduce integration overhead and gain real-time visibility across their stack. It provides SDKs for JavaScript, Python, and Rust, allowing services to be written in multiple languages while remaining part of the same composed system. The mental model is intentionally minimal: workers expose functions that can be triggered by various event sources, and that simplicity is the entire abstraction.

Almost all open issues are raised by outside users rather than the core team, indicating a substantial base of adopters reporting real-world use. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by bug, enhancement, and high-priority labels.