Built to clear a risk review.
Zahen treats security and governance as the product, not an add-on. Answers are access-filtered before retrieval runs, high-risk actions pause for human approval, credentials are brokered so agents never hold them, and every privileged action is written to an append-only audit log. It's documented here, ungated, for your security and procurement teams.
One governed path, from question to action.
Every agent task follows the same controlled flow inside your own single-tenant instance — access-filtered retrieval, a plan, a human approval for anything high-risk, governed tool execution, and an append-only record of all of it.
Your cloud · private cloud · on-prem — encrypted in transit & at rest
Request
An employee or operator asks in the console — English or Arabic.
Retrieve
Access-filtered before the search runs; answers cite their sources.
Plan
Reasoning is separated from execution; the model provider is your choice.
Approve
High-risk actions pause for a human decision — and no self-approval.
Act
Tools run with brokered credentials, schema-checked, behind a kill-switch.
Every sign-in, retrieval, approval and tool call is written in its own transaction — never edited or deleted. Filter by date, event, user or department, and export to CSV or your SIEM.
Grounded, access-filtered answers
- Retrieval is filtered by your role and department BEFORE the search runs — there is no “filter after the fact”
- Answers cite the approved sources they're drawn from; you can verify them in seconds
- If the documents don't contain the answer, the assistant says so instead of guessing
- Retrieved content is reference material, never instructions — built-in prompt-injection isolation
Human approval, by design
- Risk lives on the tool, not the task — high-risk actions pause automatically
- Nothing high-risk runs until a person with the right role decides
- Five outcomes: approve, reject, edit & approve, request more info, escalate
- No self-approval — you can't decide a request you raised, and this rule cannot be overridden
Append-only audit & observability
- Every sign-in, question, document access, tool call, and approval is recorded
- The log is append-only — entries cannot be edited or deleted after they're written
- Filter by date, event, user, or department; export to CSV for review or your SIEM
- Usage and estimated cost are visible by model and department
Identity & access control
- Multi-factor authentication (TOTP) and modern password hashing
- Role-based access control — roles are re-loaded from the system of record, not trusted from a token
- Document-level access (public / employee / department / restricted)
- De-privilege a user and their pending actions stop — permissions are re-checked at execution
Governed tools & credentials
- Agents can only call tools an administrator has explicitly registered and enabled
- Agents never hold credentials — the platform brokers each call from a secure store
- Instant kill-switch: disable a tool or require approval on it without a code deploy
- Tool inputs are schema-validated, and secrets / PII are redacted in the audit trail
Durable, resumable execution
- Multi-step tasks are checkpointed at every step
- If the system restarts mid-task, the agent resumes from its last checkpoint
- A paused task holds its state until an approver decides — work is never silently lost
Not a mockup — the operator console.
Documents are ingested into an access-governed index: every file carries who is allowed to read it, and that activity streams into the same append-only record as every other privileged action. This is the live Operations view your administrators and security team work in.
- Per-document access (public / employee / department / restricted)
- Ingestion and access recorded in the append-only stream
- Bilingual EN / AR console, single-tenant to your instance
Approval is a decision, not just a gate.
When an agent proposes a high-risk action, the task pauses and an approver sees the proposed action, the risk level, and the agent's evidence and plan. They then choose one of five outcomes — every one of which is written to the audit log with who decided, what, and when.
Approve
The action proceeds exactly as planned; the task resumes automatically.
Reject
The action is blocked permanently; the task stops without performing it.
Edit & approve
Adjust the action (e.g. recipient or content); the task resumes using your edited version.
Request info
Send it back for clarification; it returns to the queue when answered.
Escalate
Hand it to someone else or a higher authority, with a per-request grant.
You can't approve a request you raised yourself. No self-approval — and it cannot be overridden.
Reconstruct exactly what happened — line by line.
Every sign-in, question, retrieved source, approval, and tool call is recorded in its own transaction. Entries are never edited or deleted, and the whole trail filters by date, event, user, or department — and exports to CSV for review or your SIEM.
- Who decided, what they chose, and when
- Secrets and PII redacted in the record
- Exportable to CSV for risk & compliance
| Time | Actor | Event | Detail |
|---|---|---|---|
| 09:41:02 | AAgent | Retrieved source | refund-policy.pdf · clause 3 |
| 09:41:03 | AAgent | Proposed action | billing.refund($1,420) |
| 09:42:18 | RR. Haddad | Approved | with note · authorised |
| 09:42:19 | AAgent | Executed tool | billing.refund · 200 OK |
Dedicated and single-tenant — your data stays in your instance.
Zahen runs as a dedicated, single-tenant instance per customer. There's no shared multi-tenant SaaS boundary, so your documents, embeddings, and logs stay in your instance. You choose where it runs — your own cloud (AWS, GCP, or Azure), a private cloud, or on-premises — and data is encrypted in transit and at rest. Deployment supports regulated and government-adjacent organisations, designed to support your data-protection and compliance review in the regions where you operate.
- OECD AI Principles — human agency and oversight
- NIST AI Risk Management Framework
- EU AI Act — human-oversight expectations
- Maps to the common controls across GDPR, HIPAA & sector regimes
Zahen is bilingual English / Arabic and RTL-first. A language toggle flips the whole interface to right-to-left, in both the operator console and employee mode.
Security answers without a form.
A security pack, architecture overview, and answers to common vendor-risk questions are available without a gate. Need something specific for your review?
Procurement-ready answers.
Do you support SSO?
Do you support Arabic?
Where do data and logs reside?
Is customer data used to train models?
How does this map to data-protection regimes?
See where governed agentic AI fits in your business.
Book a readiness workshop with our team. We'll map your highest-value, lowest-risk first workflow — no obligation to proceed.