Architecture
That is the whole system in one line. The rest of this page is the detail an architect asks for: which API a connector calls, how permissions are enforced at query time, where a model actually runs, what a write is allowed to change, and what lands in the audit log afterwards.
nothing left the perimeter0 B egress
Layer 01 · Connect
Connectors query source systems over their own APIs and carry the caller’s identity on every request. There is no staging bucket, no vendor-side replica, no overnight dump. The record you query is the record in the system of origin.
Customer 4471
same record · no copy made · ACLs enforced at the source0 B egress
Layer 02 · Unify
The Brain is a graph over your sources, not a copy of them. Identifiers are matched into entities, conflicting values are kept alongside their provenance instead of being overwritten, and every result is cut against the caller’s permissions before it is returned.
Company Brain
7 sources · 1.2M entities resolvedinherited ACLs
Layer 03 · Reason
Each request is classified and dispatched to whichever model scores best on that class of work. The routing decision, the model version and the parameters are recorded with the run, so an answer can be reproduced later on the model that actually produced it.
Barie picks the model. You keep the infrastructure.no token bill
Layer 04 · Act
Execution is a sequence of scoped, logged operations against systems you already control. Each write is attributed to the person who invoked it, gated wherever policy demands it, and recorded in enough detail to reconstruct, or reverse, what a run changed.
Every step signed to an immutable log0 B egress
Measured, not asserted
GAIA · hardest tier
92%
Level 3 tasks chain a dozen or more dependent steps across tools, and most agents lose the thread partway and return something confidently wrong. This figure is from the shipping configuration: same routing, same boundary, no bench-only settings. Public method, public numbers. Audit them yourself.
Run it yourself
Deployment
Barie installs where your data already is. The sovereignty guarantee does not change between them. Only the walls around it do.
Runs in your own data centre, on hardware you procure and keep.
Deployed inside your own cloud tenancy. Your account, your network policy, your region.
Installed into a fully isolated environment. Updates arrive through your existing controlled-media process.
Security & trust
The claim is falsifiable, which is the point of making it. Stand the deployment behind a default-deny egress policy and it runs unchanged: no degraded mode, no feature that quietly needs a callback. Your egress monitoring has nothing to report because there is nothing to report.
The test is simple: watch the boundary while it works, and see what crosses it. Nothing does.
Stand the deployment behind a default-deny egress policy and nothing degrades. There is no allow-list to maintain and no exception to review.
Barie keeps no user directory of its own. Accounts, groups and revocations stay in your IdP and are read from it.
Rights are evaluated per request against the source system, so a revocation takes effect on the next query rather than the next rebuild.
The trail is queryable and exportable in full, so it can go to an examiner directly without a vendor sitting in the loop.
You size the hardware once. There is no meter turning a more productive team into a larger invoice.
Jurisdiction is settled by where you install, not by a clause in a contract that a change of ownership can revisit.
Technical fact sheet
See Barie running inside your own environment: your systems, your models, your controls, on your infrastructure.