Architecture
One runtime, five doors.
The runtime is the engine that executes a team of agents (a crew in the code) and enforces the rules. There is only one, however you use Orkeon.

The runtime and its invocation point
Doors
Five ways to reach the runtime.
- Orkeon Studio
- the
orkeonCLI - Orkeon Code
- Orkeon Workshop
- NuGet package
Runtime
The engine: it loads the team and runs it.
- YAML ·
.ork.ts· C# - 6 modes
- budgets and circuit breakers
- memory, checkpoints (opt-in)
- RAG pipeline
Invocation point
Every tool call an agent makes goes through it before acting.
- virtual mounts
- Guardian (heuristic)
- confined shell (except in a container)
- sandbox
- call audit
Tools
What an agent can do, once the call is accepted.
- files
- mail · drives
- web · HTTP
- databases · Office · PDF
- code
Providers
The models that respond to the agents.
- local models
- vendors
- aggregators
- OpenAI-compatible endpoints
Cross-cutting OpenTelemetry · domain events · MCP and A2A (experimental) · Microsoft Agent Framework
A boundary declared, then enforced
A path outside the mounts is refused at the invocation point, before it reaches the disk.
An agent is software, not a script
A team is deployed, keeps its state and is observed like any other service.
An open project: standards, not lock-in
Orkeon is open source, under the MIT license, and the choice of model stays yours.
The runtime’s building blocks
The limits of the boundary are detailed on the Security page.
A. Boundary
- BoundaryWhat an agent may touch is declaredMounts place a real folder behind each virtual path. Code runs in a sandbox; the shell is confined, except in a container. The web tools reach the whole public web until the domain list is declared. Guardian, a heuristic filter against injection, remains outside the guarantee.
- BudgetAutonomy has a budgetAn autonomous run operates under the budget the team declares, with five dimensions: tool calls, delegation depth, duration, tokens, spawned agents. Without a declared budget, neither tokens nor duration are capped. Circuit breakers interrupt loops. The other modes are bounded by the token and cost cap set by the host, the application that starts the runtime; there is none by default. (new tab)
B. Continuity
- OrchestrationSix modes, chosen in the team’s fileSequential, hierarchical (a manager and workers), parallel, consensual (each agent runs the task, then a vote), graph, autonomous. Tasks run in the order of their declared dependencies, then of the file; in parallel mode, tasks with no dependency between them start together. (new tab)
- StateMemory, RAG and checkpointsThe runtime provides six memory backends and a RAG pipeline (the document search that feeds the model). Durable memory and checkpoints are opt-in. Local embeddings cover English only. (new tab)
- ObservabilityTraces, metrics and logs through OpenTelemetryAn OTLP export (the OpenTelemetry protocol), domain events (a cancelled task, a failed agent…) and an audit of each tool call, without the arguments. (new tab)
- ExtensibilityIsolated plugins and .ork.ts filesPlugins load in separate contexts. A team’s procedural code is written in
.ork.ts. A tool that this code calls itself does not go through the invocation point. (new tab) - DeliveryThe same runtime, from workstation to server
dotnet toolcommand, container,orkeon-hostservice, NuGet library. apt package (signed source), unsigned.msiinstaller, macOS archive not notarized.
Continuous integration checks every change
- The README is a testits two blocks of commands are run (new tab)
- Every number is recomputed124 tools, 16 providers, 6 modes, 6 memory backends, 104 example teams (new tab)
- Zero warningsall .NET analyzers,
-warnaserror(new tab) - Public GitHub workflowscoverage, CodeQL, secrets, dependencies (new tab)
Documentation
- Security, resilience and plugins (new tab)/architecture/security
- Replay the model’s responses (new tab)/guides/testing
- A2A conformance matrix (experimental) (new tab)/reference/a2a-conformance
- Microsoft Agent Framework interoperability (new tab)/reference/agent-framework-interop
- Architecture decisions (ADR-002 to ADR-018) (new tab)/adr
- API reference (new tab)/api