docs/index.mdx
Today, building a typical backend means connecting many separate systems: API frameworks, a task queue, a cron scheduler, an event bus, a pub/sub layer, a state store, a WebSocket server, and an observability pipeline.
Each system brings its own setup, its own deployment, and its own failure modes. Balancing infrastructure and business logic becomes increasingly difficult with every new system.
The result of balancing these many necessary systems are delayed delivery, difficulty debugging, transient issues, increased expenses, siloed domain and systems knowledge, and difficulty with onboarding new developers and AI agents.
The main benefit of iii is that it transforms a backend from behaving like a series of separate concerns, domains, and services into a single application-level interface across services.
iii (pronounced "three eye") does this by creating a single integration point for all backend systems which results in a stack that is easier to change and which keeps all historical knowledge in one place (ie. a single config).
The result is faster onboarding of new developers and AI agents, and simpler debugging across systems, removal of cost centers with reduced switching costs, and faster delivery of backend features.
iii unifies any backend stack with a single engine and three primitives: Function, Trigger, and Worker.
This results in the ability to:
The best way to understand iii is to try it:
Install and then update the iii-cli to get everything installed.
curl -fsSL https://install.iii.dev/iii-cli/main/install.sh | sh
iii-cli update
Check that iii has installed correctly with the following command. It should return a version number.
iii --version