Orkeon
The project

Orkeon is a young, open-source project, designed for production.

With Orkeon, you declare what a team of agents is allowed to do, the runtime enforces it, and the team you tuned is the one that is integrated into the application, without a rewrite.

Kama, Orkeon’s chameleon
The problem

The problem is not the intelligence of the models, but what is missing around them

Two obstacles keep AI agents from moving past the demo stage: the lack of a boundary, the lack of continuity.

Trust is built in the runtime, not in the prompt. What you tune must be what you deploy.

In the Orkeon framework, a team (a crew in the code) is a set of agents that cooperate; the runtime is the engine that executes it and enforces the rules.

As of November 2026

Where the project stands

Version
1.0.0, released
Platform
.NET 10
License
MIT
Notations
YAML, TypeScript (.ork.ts), C#
Orchestration
6 modes: sequential, hierarchical, parallel, consensual, graph, autonomous
Models
16 providers (14 vendors, 2 aggregators), local models included: the list (new tab)
Memory
6 backends: InMemory, Redis, SQLite, ChromaDB, Pinecone, LanceDB
Knowledge
Built-in RAG pipeline
Interoperability
MCP and A2A (experimental), Microsoft Agent Framework
Observability
OpenTelemetry
Orkeon Studio
Desktop application for Windows; two terminal applications for Linux, macOS and Windows
Repositories
orkeon (new tab), orkeon-studio (new tab), orkeon-workshop (new tab), orkeon-code (new tab)
Governance
Published architecture decisions (ADR), public API frozen per package
StatusComponents
stableThe runtime, the orkeon CLI, the three notations, the virtual file system, the six orchestration modes, OpenTelemetry, 16 providers, 124 tools (the inventory (new tab)). The drive tools have yet to be proven on real accounts.
experimentalMCP and A2A. The C# APIs marked [Experimental] (new tab) refuse to compile without an explicit opt-in and may change between two versions.
Limits
  • The Windows installer (.msi) and the Orkeon Studio installer are not signed.
  • The macOS archive is not notarized.
  • The container image carries no provenance attestation.

Security: guaranteed, not guaranteed · Known limitations (new tab)

Doors

Five doors, four repositories

  • Orkeon Studio: a desktop application for Windows, to create a team without code or a terminal, and two terminal applications for Linux, macOS and Windows.
  • The orkeon CLI: to run a team (orkeon run) or generate one from a sentence (orkeon forge).
  • Orkeon Code: a coding assistant in the terminal, built on the runtime.
  • Orkeon Workshop: a workshop to design, test and measure teams.
  • The Orkeon NuGet package: to integrate the runtime into your own applications (same repository as the CLI).
Scope

What Orkeon is not

  • Not a demo. It is designed for production, not for the throwaway prototype.
  • Not a chain of prompts. It provides state, memory, tools, deployment and observability.
  • Not a dead end. What is tuned with Orkeon is integrated into an application without being rewritten.
  • Not a guardrail bolted on afterwards. The limits are in the runtime from the start, not in a filter applied to the output.
Longevity

What lets you leave Orkeon

Your teams are files, and the models are interchangeable. Orkeon is maintained by a single maintainer, with no commercial support, and is looking for its first users. It is designed for production, not yet proven in production. A security boundary is not taken on trust: this one can be read, tested and challenged.

This site sells nothing and sets no cookies.