explaingit

iii-hq/iii

Analysis updated 2026-06-24

15,623RustAudience · developerComplexity · 4/5LicenseSetup · moderate

TLDR

Rust framework that wires every registered service to every other service so adding the 20th worker is as easy as adding the first. Built around Workers, Triggers, and Functions.

Mindmap

mindmap
  root((iii))
    Inputs
      Worker registrations
      Triggers like HTTP timers queues
      Function calls
    Outputs
      Function results
      Live traces
      Routed messages
    Use Cases
      Connect polyglot microservices
      Replace ad hoc service glue
      Inspect runtime flows
    Tech Stack
      Rust
      Node
      Python
      React
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Connect TypeScript Python and Rust services through one consistent function call interface

USE CASE 2

Replace homegrown queue and HTTP glue with named functions like orders validate

USE CASE 3

Trigger workflows from HTTP requests timers or queue messages without writing routing code

USE CASE 4

Inspect live function traces in the developer console

What is it built with?

RustNodePythonReact

How does it compare?

iii-hq/iiipyo3/pyo3louis-e/arnis
Stars15,62315,67115,698
LanguageRustRustRust
Setup difficultymoderatemoderateeasy
Complexity4/53/52/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Engine is Elastic License 2.0 so review the no-managed-service clause before deploying it commercially.

Engine is Elastic License 2.0 so you can use it freely but cannot resell it as a managed cloud service. SDKs and console are Apache 2.0.

In plain English

iii is a framework written in Rust that tries to solve a common problem in software development: as you add more services (individual programs that do specific jobs) to a system, the effort of connecting them all together grows rapidly. With iii, every service you add is automatically able to communicate with every other service the moment you register it, so adding your 20th service is no harder than adding your first. The framework revolves around three building blocks. A Worker is any process, a TypeScript API, a Python data pipeline, a Rust microservice, that registers with the iii engine. A Trigger is anything that makes work happen: an HTTP request, a scheduled timer, a queue message, or a state change. A Function is the actual piece of work, identified by a stable name like "orders::validate," that receives input and produces output. By organizing everything through these three concepts, iii gives your entire infrastructure a single consistent mental model. SDKs are available for Node.js, Python, and Rust, so teams can write workers in the language they prefer. There is also a developer console (built with React and Rust) for inspecting workers, functions, triggers, queues, and live traces. The engine itself is licensed under the Elastic License 2.0, which allows free use but restricts offering it as a managed cloud service, while the SDKs and console use the more permissive Apache License 2.0.

Copy-paste prompts

Prompt 1
Show me how to register a Node worker with iii and call a Rust function called billing charge from it
Prompt 2
Write a Python iii worker that exposes a function triggered by a cron schedule every 5 minutes
Prompt 3
Compare iii to Temporal and Restate for a small team migrating from raw HTTP microservices
Prompt 4
Set up the iii developer console locally and walk through inspecting a queue backed trigger

Frequently asked questions

What is iii?

Rust framework that wires every registered service to every other service so adding the 20th worker is as easy as adding the first. Built around Workers, Triggers, and Functions.

What language is iii written in?

Mainly Rust. The stack also includes Rust, Node, Python.

What license does iii use?

Engine is Elastic License 2.0 so you can use it freely but cannot resell it as a managed cloud service. SDKs and console are Apache 2.0.

How hard is iii to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is iii for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub iii-hq on gitmyhub

Verify against the repo before relying on details.