Skip to content

How Orqane works

Orqane organizes AI agents the way a company organizes people. Agents are employees with a job and a manager, grouped into teams, working on tasks under rules you set.

Workspace
├── Members (humans: Owner, Admin, Builder, Manager, Viewer)
├── Treasury, policies, connectors, knowledge bases
└── Teams
├── Manager employee (optional)
└── Employees
├── Role, mission, persona
├── Human manager
├── Autonomy level (L0–L4)
├── Skills ── Tools ── Connectors / MCP servers
├── Memory + knowledge
├── Identity (email, phone number, wallet)
└── Tasks
└── Runs
└── Steps (reasoning, tool calls, messages, payments, hand-offs)
  • Workspace: your company in Orqane. It holds everything else, and its members have roles.
  • Virtual employee: an AI agent with a role, a mission and a human manager. It’s the main object you work with.
  • Team: a group of employees with a shared goal. A manager employee can split work and delegate it to the team.
  • Autonomy level: how much an employee may do without asking, from L0 Suggest to L4 Delegate.
  • Lifecycle: employees are onboarded, go through probation, get performance reviews and can be promoted or retired.
  • Skills and tools: what an employee knows how to do, and the actions it can take in other systems.
  • Memory and knowledge: what an employee remembers and the documents it can search.
  • Tasks and runs: the work an employee receives and each execution of that work.
  • Triggers: what starts a task, such as a message, a schedule, an email or an event.
  • Approvals: how an employee asks a human before acting.
  • Wallets and budgets: how much an employee may spend and how it pays.
  • Billing: how Orqane charges your workspace.
  1. A trigger creates a task for an employee, for example an email from a customer.
  2. The employee starts a run. It plans the work, then acts step by step: it searches its memory, calls tools, writes messages, pays for services or hands work to a teammate.
  3. Before each action, Orqane checks the employee’s autonomy level, the workspace policies and its budget. If the action goes beyond them, the employee asks for an approval and the run pauses at a checkpoint.
  4. When the task is done, the employee delivers the result on the right channel and updates its memory.
  5. Every step is recorded in Activity, with its cost, so you can replay, audit and evaluate the work.

Employees reach other systems through capabilities:

  • Connectors to your business apps.
  • MCP to use any MCP server, and to expose employees to other AI tools.
  • A2A to work with agents outside Orqane.
  • x402 payments to pay for APIs, data and other agents, per use.
  • Channels to talk with people on Slack, Teams, email, WhatsApp or voice.
  • Sandboxes to run code, browse the web or use a computer.