# Roadmap Available behavior, active hardening, and planned surfaces separated clearly, with Apache 2.0 governance staying in the open tree. Source: https://aioverload.io/roadmap/ {{< section id="available" eyebrow="AVAILABLE NOW" title="The governed execution core." >}} - Event-sourced workflows on NATS JetStream with replay through `aioctl replay`. - Named workflow and agent manifests, acceptance criteria, and registry state. - Reflex step gate, recorded holds, and human approval input. - Gateway-routed MCP decisions and default-deny tool grants. - Forge ingestion into governed task rows without automatic dispatch. - Generic declared-source ingress with deduplication and trigger matching. - CLI, operator console, worker, sidecar, and server surfaces. “Available” points to behavior in the stamped source tree. It does not imply production hardening, a stable release, or support for every runtime. {{< /section >}} {{< section id="progress" eyebrow="IN PROGRESS" title="Close the gaps the threat model names." class="section--tint" >}}
01

Make container isolation the real default.

Move the shipped fleet beyond the cli tier, then finish resource limits, capability dropping, and container hardening.

02

Bring native harness tools into policy.

Close the Bash / Edit / Write bypass instead of pretending gateway-only coverage is complete.

03

Harden transport and identity by default.

Move NATS accounts, bus TLS, and API TLS from an opt-in profile toward a safer operating posture.

04

Complete the forge feedback loop.

Event-driven fleet convergence, acceptance enforcement on every ingested path, and lifecycle write-back.

{{< /section >}} {{< section id="planned" eyebrow="PLANNED" title="More surfaces, same governance contract." >}} - Kubernetes execution driver alongside cli and docker profiles. - Additional Codex, Kimi, and Gemma harnesses after the wired Claude Code path. - Resident manager and assistant runtimes. - Session distillation into a knowledge plane. - Business-app operational agents through declared applications and `.aio/` overlays. - Dev-of-flows: governed agents building integration flows through issue, run, PR, CI, and merge. - A documented boundary with integration engines: they own deterministic plumbing; AiOverload owns judgment, human doors, and the log of record. These are directions, not release commitments. Each becomes “available” only when implementation and evidence exist. {{< /section >}} {{< section id="licensing" eyebrow="APACHE 2.0" title="The governance core remains open." class="section--dark" >}} The engine and its governance surfaces are Apache 2.0: use, modify, self-host, redistribute, and offer services under the license’s conditions. There is no network-copyleft exception and no seat counter in the open engine. Any future commercial artifact must be described when it exists. Until then, this site makes no pricing or packaging claims. Read the [license summary](/license/) and the authoritative license text with the source. {{< /section >}} {{< next "/status/" "Compare plan with evidence" "The roadmap is intention; the generated status page is the receipt." >}}