orchicon

AI orchestration & operations

Coordinate autonomous AI work
like a control plane should.

Orchicon orchestrates. Runtimes execute. One binary, one command, and your local stack — Postgres, NATS, OpenTelemetry, the SPA — is up. 

$ curl -fsSL https://orchicon.dev/install | bash
PS> irm https://orchicon.dev/install.ps1 | iex

Installs the orchicon binary to ~/.local/bin. Re-running updates to the latest release. See options below.

Quick start

  1. 1

    Install

    Run the one-liner above. Requires curl and tar (or PowerShell on Windows).

  2. 2

    Start the dev stack

    $ orchicon dev start

    Boots Postgres, NATS, SigNoz, the OTel collector, runs migrations, and serves the control plane + embedded UI on localhost:8080. Requires Docker.

  3. 3

    Log in & build

    Open the URL, sign in with the built-in dev IdP, create a project, define a Worker, and dispatch a Task. The whole end-to-end flow is verifiable locally.

What Orchicon is

An orchestration platform for autonomous AI work. It coordinates the moving parts — projects, workers, scheduling, policies, telemetry, recovery, governance — and talks to pluggable runtimes (OpenCode first) over gRPC.

Projects & work

Tenants, projects, work items as a DAG (Epic → Feature → Task → Subtask), with cycle-detected dependencies.

Workers & dispatch

Versioned Worker definitions (system prompt, permissions, gated tools, budgets). Reconciler-driven dispatch to healthy adapters.

Workflows

Step-DAG workflows: task, decision, approval, parallel, recover. Visual React Flow editor. Real-time step transitions.

Recovery engine

Default 6-step recovery workflow (capture → summarize → preserve → review → plan → resume) with checkpoint replay and bounded auto-relax.

Rego policy

OPA v1 at the dispatch decision point. Narrowest-scope-first evaluation, full Rego trace per decision for explainability.

Telemetry & cost

OTel → SigNoz. Per-tenant cost roll-up (Tenant → Project → Task → Execution) with streamed usage events.

Orchicon orchestrates. Runtimes execute.

The control plane is a single Go binary. The runtime is a sidecar. Adapters never touch Postgres or NATS directly — they stream telemetry over gRPC. Swap OpenCode for something else by implementing orchicon.adapter.v1.

Installer options

macOS / Linux

$ curl -fsSL https://orchicon.dev/install | bash -s -- --version v0.2.0
$ curl -fsSL https://orchicon.dev/install | bash -s -- --install-dir /usr/local/bin
$ curl -fsSL https://orchicon.dev/install | bash -s -- --uninstall

Windows

PS> & ([scriptblock]::Create((irm https://orchicon.dev/install.ps1))) -Version v0.2.0
PS> & ([scriptblock]::Create((irm https://orchicon.dev/install.ps1))) -InstallDir "C:\bin"
PS> & ([scriptblock]::Create((irm https://orchicon.dev/install.ps1))) -Uninstall
FlagDescription
--version <tag>Install a specific version (e.g. v0.2.0). Default: latest.
--install-dir <dir>Where to drop the binary. Default: ~/.local/bin.
--uninstallRemove Orchicon from the install directory.
--dry-runPrint what would happen without making changes.

Build from source

Pre-built binaries ship from GitHub Releases. Until the first release is cut, build from source:

$ git clone https://github.com/beardedparrott/Orchicon.git
$ cd Orchicon
$ make build         # → bin/orchicon
$ make dev-start     # full dev environment

Prereqs: Go 1.26+, Node 22+, Docker. The Makefile installs buf and atlas via make tools.

Read the design

Ten design documents, one for each subsystem.

Open the docs →