---
title: "Introduction"
description: "ÆTERION BRAIAN is an AI operating system: a software product that runs finance, legal, sales, marketing, procurement, risk and HR processes as governed automation. Agents execute the work, policies constrain what they may do, and every decision is logged, versioned and auditable across the systems a company already operates."
url: "https://aeterion.tech/en/docs"
locale: "en"
publisher: "AETERION SA"
---
# Introduction

> ÆTERION BRAIAN is an AI operating system: a software product that runs finance, legal, sales, marketing, procurement, risk and HR processes as governed automation. Agents execute the work, policies constrain what they may do, and every decision is logged, versioned and auditable across the systems a company already operates.

Source: https://aeterion.tech/en/docs
Last updated: 2026-09-20

## What does this documentation cover?

These pages describe how BRAIAN is modelled, deployed and operated. They are written for the people who run the platform: process owners, platform engineers, risk and compliance teams.

- Core concepts: the six objects every BRAIAN deployment is built from.
- Quickstart: from an empty workspace to a governed process running in a sandbox environment.
- Guides: task-oriented walkthroughs for recurring operational work.
- Integrations: how BRAIAN connects to SAP, Microsoft 365, Salesforce, ServiceNow and databases.
- Governance and compliance: how runtime evidence maps to the EU AI Act, the General Data Protection Regulation (GDPR) and the Swiss Federal Act on Data Protection (nFADP).

## How is BRAIAN structured?

A deployment has four layers. The control plane holds policies, credentials and environments. Orchestration turns a process definition into running work. Evaluation scores every run against expected outcomes. Observability records what happened, in an append-only audit log.

- **Control plane** — Where policies, secrets, roles and environments are defined and versioned.
- **Orchestration** — Executes process definitions: steps, agents, tool calls, retries and escalations.
- **Evaluation** — Compares each run against expected outcomes and flags regressions before they reach production.
- **Observability** — Append-only records of inputs, decisions, approvals and system calls for every run.

## Conventions used in these pages

Definitions in YAML describe objects stored in the control plane. Command examples use the BRAIAN command line, which authenticates against the environment selected in your workspace.

```bash
braian env use sandbox
braian process list
```

> **Every page is available as markdown** — Append .md to any documentation URL to retrieve the same page as raw markdown, without navigation or styling.