AETERION

    Architecture

    How ÆTERION BRAIAN is deployed

    A governed runtime that sits between your systems and the models you use, with data residency and network boundaries you decide.

    How ÆTERION BRAIAN is deployed

    ÆTERION BRAIAN is deployed as a managed environment in Switzerland or the European Union, or inside your own cloud tenancy. The runtime holds process state, policies and traces. Connectors reach your systems over controlled network paths. Model providers are called through a gateway that enforces policy, redaction and cost limits on every request.

    Deployment options

    Managed (CH)

    Hosted by ÆTERION in Switzerland. Fastest to start, Swiss data residency, operated to a published service level.

    Managed (EU)

    Hosted in the European Union for organisations with EU-only residency requirements.

    Your cloud

    Deployed into your own tenancy when internal policy requires the runtime to sit inside your perimeter.

    Data boundaries

    • Operational data stays in your systems; BRAIAN holds process metadata, policies and traces.
    • Redaction rules strip identifiers before a request leaves for a model provider.
    • Model routing is policy: a process can be restricted to providers in a given jurisdiction.
    • Encryption in transit and at rest, with key management aligned to your standard.

    Integration surface

    Connectors
    Governed adapters for ERP, CRM, ticketing, storage and databases, each with its own permissions.
    API
    A documented HTTP API to trigger processes, read state and pull traces.
    Events
    Webhooks and message-queue triggers so processes start from events you already emit.
    Identity
    SSO through your identity provider, with roles mapped to control-plane policy.

    FAQ

    Which models can BRAIAN use?

    Commercial and open-weight models through the gateway, selected per step by policy. Model choice is configuration, not a rewrite.

    Can we run without any external model provider?

    Yes, where self-hosted models are available in your environment; the gateway then routes only to internal endpoints.

    Review the architecture with your team

    We walk your architects through deployment, data flows and network boundaries.