iii Homepage for AI

This markdown is auto-generated from visible homepage content and optimized for quick context.

Code Examples

Code examples are intentionally omitted from this machine page. For implementation details and source examples, visit:

Primary Links

Overview

One Engine.trigger any language

The centralized orchestration runtime for distributed polyglot function execution. React simplified frontend with Component and Context. iii does the same for backend.

Polyglot execution — any language participates through one universal protocol.
Complete observability — logs and traces auto-injected into every invocation.
Self-hosting/BYOC — connect existing domains and services, full portability.
Shared capabilities — State, Streaming, Observability accessible to every function.

Architecture

One engine.Three primitives.

iii unifies your entire backend with Function, Trigger, and Worker. One mental model for every backend system. Anything that does work. A Function receives input and optionally returns output. It can live anywhere — locally, on cloud, on serverless, or as a third-party HTTP endpoint. All Functions are treated the same within iii.

The Engine does it all

Operations flow through the Engine to any worker, in any language

Polyglot Runtime

One protocol. Any language.

Python registers a function. Rust registers a function. Node.js consumes both.Simply register functions and trigger them.

Observability

Trace-level visibility. Built in.

Every function call, every span, every metric — captured automatically with OpenTelemetry. Export to any backend or use the built-in console.

Built-in Console

Native trace viewer with waterfall, flame graph, service breakdown, and trace map visualizations.

Export Anywhere

OTLP-native export to any OpenTelemetry-compatible backend — Datadog, Grafana, Honeycomb, and more.

Zero-Config Tracing

Auto-instrumentation for all function calls with W3C traceparent propagation across language boundaries.