Roadmap

Mirrored page

This page mirrors ROADMAP.md in the platform repository, which is the source of truth and is tracked as GitHub milestones and issues. If the two differ, the platform repository wins.

0.1 – Core (released 2026-10-04)

• Control node: API (Fastify, OpenAPI 3.1), PostgreSQL, run queue, console (React), OIDC/LDAP sign-in, RBAC with six roles, API tokens.
• Agents as code: agents.md parser and validator, immutable published versions, pipelines of 1..n agents.
• Events: signed webhooks, Kafka, cron, mail-in via webhook; Teams and Slack through generic webhooks.
• Guardrails: per-agent audit gate, global control agent, approvals, data classification.
• Audit: append-only SHA-256 hash chain with Ed25519-signed checkpoints and verification.
• Costs: per step and run, price table, budgets with hard stop.
• Providers: OpenAI-compatible, Ollama, AWS Bedrock (VPC endpoint, proxy, IRSA), Anthropic, simulated.
• MCP: client with per-agent allowlists, timeouts and result limits; the policy gate as an MCP proxy.
• Runners: in-process and local (oax CLI), with the interfaces for all later runners.
• Observability: Prometheus metrics, OpenTelemetry traces, JSON logs, health endpoints.
• Cost attribution: per tenant, agent, use case and run, with CSV/JSON export.
• Delivery: Docker Compose, Helm chart for Kubernetes and EKS, this website and docs.

0.2 – Next release (on main)

• Tenants and access: tenants as the isolation boundary, roles per tenant and optionally per agent (details).
• Bring your own: provider keys by reference and a model catalog from a pinned models.dev snapshot (details); MCP servers per tenant.
• Typed handovers and conditional steps: schema-validated outputs and when expressions.
• Tool profiles: named read/write profiles per MCP server.
• Worker nodes: container runner (Docker, Podman) and kubernetes-job runner (also EKS) that spawn one short-lived worker per step, with per-step credentials.
• Toolbox images from a catalogue: minimal, non-root, read-only, pinned by digest, signed (cosign), with SBOM (syft) and vulnerability scans (trivy); egress allowlisted per toolbox.
• Agent Check and Agent Plan: advisory, least-privilege decomposition with linting.
• OpenCode harness: next to Claude Code behind the policy gate.

0.3 – Anywhere

• aws-lambda, github-actions and gitlab-ci runners with signed callbacks.
• Optional external harnesses: Claude Code, OpenCode, Hermes, OpenClaw, all routed through the policy gate.
• Dedicated Teams and Slack adapters, IMAP polling for mail.

Features shipped in 0.1 with full docs

• Change-gated schedules with HTTP and file probes (details).
• Development guidelines with deterministic hardening review (details).
• Dark software factory mode, opt-in (details).

0.3 – Enterprise integration

• AWS Lambda, GitHub Actions and GitLab CI runners with signed callbacks.
• Hermes and OpenClaw harnesses.
• Dedicated Slack and Teams event adapters, IMAP polling for mail.
• SCIM provisioning, per-tenant identity providers.
• Secret managers (Vault, AWS Secrets Manager).
• MCP catalog with review states and per-server egress rules.

0.4 – Agent lifecycle

• Agent Build: from plans to scaffolded agents with tests.
• Evaluations v2: golden datasets and promotion gates.
• Version approval bound to model and eval set.
• Automatic hardening review of development agents’ pull requests.
• MCP catalog governance and container-run MCP servers.

1.0 – Enterprise readiness

• Stable v1 API and agents.md schema.
• Per-tenant audit chains and Merkle proofs.
• Multi-step approval workflows.
• Data residency and region pinning.
• Scale-out run queue (Valkey/Kafka).
• Red-teaming campaigns.
• Air-gapped offline bundle.
• Private model hosting (vLLM/Ollama with GPU).
• Public demo at demo.openagentix.si.

The order within this list is not fixed; the platform repository tracks the current plan.

Towards 1.0

• Stable v1 APIs and agents.md schema (openagentix.io/v1).
• Signed releases and images, documented upgrade paths.
• Chart repository and OCI publishing, public demo at demo.openagentix.si.

Have an idea? Open an issue in the platform repository; larger changes start as an ADR.