Six layers. Every one replaceable.
Everything runs inside your perimeter, on models you approve, with connectors that act inside the systems you already run.
The stack behind every agent.Open, sovereign, auditable.
Six layers, each one replaceable, all of them inside your perimeter. Select a layer to see what runs there.
Channels
(01) / 06Agents meet people where they already are, in Arabic or English, typed or spoken.
Why it matters · One agent and one case across every channel. A request started on WhatsApp can finish in the app.
Identity and consent
(02) / 06Every request is tied to a verified person, and every action to a permission they granted.
Why it matters · Read, write and transact are separate grants, revocable in a single step.
Orchestration
(03) / 06A state graph coordinates specialised agents and holds the case from first message to completion.
Why it matters · New services register as sub-agents under one shell instead of starting a new project.
Models
(04) / 06Open-weight models by default, each sized to its job and served inside your perimeter.
Why it matters · No lock-in to one vendor. Models are swapped as better ones ship, without rebuilding the agent.
Engines and knowledge
(05) / 06Deterministic engines calculate, validate and write. Retrieval grounds every answer in your own sources.
Why it matters · The model never computes. Every number a customer sees comes from an engine you can audit.
Infrastructure
(06) / 06Runs on your own hardware or a sovereign UAE cloud, with every turn traced and measured.
Why it matters · You can see what every agent did, why it did it and what it cost, turn by turn.
What a connectoractually is.
A set of approved actions on one system: read availability, create a booking, file a document. The agent can call only those, with validated inputs, and only as the person it is serving.
- Built in the integration step of every project
- Each action scoped, validated and logged
- Anything outside the role is refused, and the refusal is logged too
- read booking.availability · as user 7781
- write booking.create · Thu 17:00
- send whatsapp.confirmation
- read erp.purchase_request · operations
Ask once.
If your institution already holds a piece of data, the agent confirms it rather than asking again. Integration depth, not conversation quality, decides whether a journey actually gets completed.
Bring us one process. We will show you the AI working.
A one-hour meeting with our team, on a real example from your organization.