Capability
Control plane
One place to declare who may act, on which systems, with which data and within which limits — enforced on every run.
Control plane
The control plane is the policy layer of ÆTERION BRAIAN. It holds identities, roles, connector permissions, data boundaries, spending limits and approval rules as versioned configuration. The runtime asks the control plane before every step, so an agent can only do what policy currently allows, and every change is attributable to a person and a version.
What does a policy cover?
- Which agents and services may run a step, and on whose behalf.
- Which systems and record types a step may read or write.
- Limits per run and per period: cost, volume, blast radius.
- When a human approval is mandatory before the step continues.
- Which data may leave the environment, and which must stay inside it.
Versioned, not improvised
Policies are stored as configuration with authorship and history. You can diff two versions, promote a policy from staging to production, and roll back a change without touching process code.
Environments and secrets
- Environments
- Development, staging and production hold separate credentials and separate limits, with promotion as an explicit step.
- Secrets
- Connector credentials are held in the control plane and never exposed to agent prompts or process definitions.
- Identity
- Users and service accounts authenticate through your identity provider; roles map to policy, not to individual scripts.
FAQ
Does a policy change require a deployment?
No. Policies are configuration. A new version takes effect on the next step the runtime authorises.
Can two business units have different rules?
Yes. Policies are scoped, so units, regions or subsidiaries can hold different limits under one platform.
Put your rules in one place
We map your current permissions and show them as enforceable policy in BRAIAN.