Common architecture
The bridge stays with TRIRIGA. The intelligence layer can move.
Layer 1
Intelligence and control
Semantic routing, evidence composition, governed MCP and REST tools, tenant and environment policy, confirmation, and audit.
AJAEX-operated for Bring your own AI, with or without our AI model. Customer-operated for the local estate licence.
Layer 2
Customer-side bridge
Supported in-JVM access to the TRIRIGA platform surfaces that require local execution, licensed for the named scope.
Installed and operated with the customer in every model.
System of record
Customer TRIRIGA
Platform, database, configuration, records, documents, runtime, and the approved integration identity remain customer-hosted.
Ways to run it
Compare responsibility, data flow, and current availability.
Use our AI model
Most teams: our workspace and AI model on your own TRIRIGA instances, with a usage allowance.
AJAEX: The workspace, model, hosted tools, gateway, tool policy, audit log and administration.
Customer: TRIRIGA, the installed bridge, and the named users.
Bring your own AI
Teams that want to pay for inference on their own model account (Anthropic, OpenAI or AWS Bedrock), under their own contract.
AJAEX: The workspace, hosted tools, gateway, tool policy, audit log and administration, connected to your inference provider.
Customer: The model account, TRIRIGA, and the installed bridge.
Local estate licence
Estates that want the tools in their own cloud account or premises, on their own model.
AJAEX: Releases, set-up help and support for the licensed distribution.
Customer: The host, AI model, secrets, logs, network, TRIRIGA and operating controls.
Responsibility matrix
Who operates each component.
Scroll horizontally to compare all models.
| Component | Bring your own AI | Use our AI model | Local estate licence |
|---|---|---|---|
| UI and user experience | Customer | AJAEX | Customer |
| AI model or model account | Customer | AJAEX and its model provider | Customer |
| Intelligence, MCP, and admin layer | AJAEX | AJAEX | Customer |
| Bridge inside TRIRIGA | Customer | Customer | Customer |
| TRIRIGA and system of record | Customer | Customer | Customer |
Data flow
Bring your own AI keeps the AI client with you; tool data still passes through AJAEX's gateway.
Each service design documents regions, provider terms, retention, backup, support access, deletion, and subprocessors.
Scroll horizontally to compare all models.
| Data category | Bring your own AI | Use our AI model | Local estate licence |
|---|---|---|---|
| Prompts and conversations | Your AI client and model provider; AJAEX only if your client sends them | AJAEX workspace and its model provider | Customer systems and selected provider |
| Tool arguments and results | AJAEX gateway | AJAEX gateway | Customer-hosted tooling |
| Service credentials | AJAEX secret store for the named environment | AJAEX secret store for the named environment | Customer secret store |
| Identity and audit metadata | Your AI client plus AJAEX gateway audit | AJAEX workspace, admin, and gateway | Customer-hosted audit |
| TRIRIGA system of record | Customer | Customer | Customer |
| Licence, update, and support traffic | Documented for the selected tooling service | Documented for the hosted workspace | Online, offline, or proxied route agreed during solution design |
The gateway runs in AWS London (eu-west-2). Any contractual commitments for residency, retention, backup, support access, or recovery are set out in the selected service agreement.
Control questions
Review the controls behind each deployment model.
AJAEX LTD holds Cyber Essentials Plus (renewal 13 November 2026). Cyber Assurance and ISO 27001 certification are in progress. It holds no ISO 27001 or SOC 2 certificate today, and no independent penetration test has been run. The security pack lists each control and each open item.
Service identity and least privilege
The customer supplies a dedicated TRIRIGA integration identity. Its permissions and the enabled tool list together define the maximum reachable scope.
Credentials kept apart
The TRIRIGA service user's password is held in a per-customer secret store. The solution design records who can reach it and how it is rotated.
Tool policy and confirmation
Read, write, administrative, and deployment capabilities are separated. You choose the exact tools for each environment. Write tools stay off until the policy turns them on, and a person confirms each change before it is written.
Explicit data flow
Prompts, arguments, results, credentials, identity metadata, logs, diagnostics, and provider processing are mapped for the selected model.
Customer-operated bridge
The supported bridge is installed inside the customer's TRIRIGA or MREF environment, in the javax or Jakarta build that matches the platform.
Assurance follows the model
Every tool call is logged with environment, action and outcome, without secrets, and kept for 90 days. Ask for the security pack to review retention, backup, support access, recovery and the open items before agreeing the service scope.
Hosted MCP connections authenticate with a credential for your tenant, not one per person. Calls run in TRIRIGA under the tenant's integration identity: per-user TRIRIGA identity and user-level OAuth are not standard controls, so any production engagement that requires them must address that before use.