Orkeon
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.

Kama at the workbench, in front of a team’s blueprint
Overview

The runtime and its invocation point

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.

In detail

The runtime’s building blocks

The limits of the boundary are detailed on the Security page.

Public checks

Continuous integration checks every change

Further reading

Documentation