A desert mesa at night under a sky full of stars, bands of light traced along its rock layers and a path of lamps climbing from the desert floor toward its summit.

Security and deployment

Control belongs
in the architecture.

Caesar connects AI to information and systems your institution is responsible for. This page explains where it can run, how access and model use are controlled, and what your team should review before deployment.

Discuss your requirements Review the controls

Controls

Define the boundary before the work begins.

A user asking about one project should only reach the records and tools that user is permitted to access. Caesar applies role, workspace and deployment rules when preparing the task and selecting tools and models.

01Access by role
Scope access to the people and teams authorized to do the work. Define what each connected tool can read or change. SSO, MFA and role-based access.
02Workspace isolation
Keep the request within the relevant matter, case or workspace. Configure access across teams and connected systems deliberately.
03Data handling before external calls
Apply the configured anonymization and routing rules before approved external processing. Review what information a provider would receive.
04Model policy
Enable the model routes your institution permits. Restricted workloads can be configured for local processing.
05Human approval
Place review and approval at the points where the workflow requires a person to take responsibility.
06Auditability
Retain a record of the work performed so authorized reviewers can inspect the sources, tool activity and approvals captured by the deployment.

Control each of the five layers.

The same architecture as on every page, with the control that applies at each layer.

Applications

What people use.

HAQQ appHAQQ web workspaceYour own interfaces and systems

Controls 01 · 06SSO, MFA and role-based access. Every action logged and attributed.

SovereignYour people work in HAQQ’s apps or your own, under your access rules.

Data

Laws, regulations and your own documents, structured for the engine.

Domain ontologiesRegulatory knowledgeCorporate knowledge

Controls 02 · 03Kept separate per customer. Encrypted in transit and at rest.

SovereignYour data never reaches the frontier models.

Intelligence

Checks, reasons and governs every request.

Pre-generation checksAnonymizationAgentic loopGovernance

Model routing

Frontier-routedOpen-weight and self-hosted

Controls 03 · 04 · 05The configured anonymization and routing rules apply before approved external processing. A person approves answers and agent actions. Only the models you allow. Never used to train HAQQ's AI models.

SovereignCaesar routes each task to the models you approve, and you can bring your own API key.

Hardware

Where data and compute sit.

HAQQ CloudOn-premise

ControlHAQQ Cloud or on premise. Residency defined in your agreement.

SovereignCaesar runs in HAQQ Cloud or on your own infrastructure.

Energy

The power behind every deployment.

SovereignYour deployment runs on the power of the site you choose.

Deployment

Choose where Caesar lives.

Sovereignty means deciding where information is stored and processed, who can use it and whether a request may reach an outside model. Choose the environment for Caesar and set those rules before the work begins.

Night aerial view of a compute campus set into the desert, its halls lit in a grid, with lines of light running across the dunes toward it. — Illustrative infrastructure scene.

HAQQ Cloud

HAQQ manages the hosting environment. Agree the region, data handling and permitted models as part of the deployment.

On-premise

Run Caesar on your own infrastructure. Use locally hosted models for work that must stay inside the boundary, with external calls enabled only where permitted.

API and MCP · Early access

Connect through the API

An API lets your software send a task to Caesar and receive the result. Your developers can put research, document comparison or drafting inside the application your team uses.

Discuss applications and API access

Hosting and model access are separate choices. A locally hosted engine can use local models, permitted external models, or a combination agreed for the deployment.

HAQQ Cloud runs in EU, US and Middle East environments. Where residency is a requirement, it is defined in your deployment architecture and agreement, so your security team knows exactly where processing takes place.

Discuss your requirements

Deployment strategy

Choose how you use Caesar.

Use Caesar inside software you already run, build a new application on it, or work with HAQQ to deliver the workflow. Your proposal identifies the engine license, usage, applications and implementation services you need.

30We guarantee full deployment in 30 days max.

Engine license

License Caesar to run in the agreed environment. It supplies the shared knowledge, retrieval, model routing and controls behind your AI workflows.

AI usage

Pay for consumption under the agreed plan. The proposal defines whether usage is measured by API call, credit or token, and how your own model credentials affect billing.

Applications

Subscribe to applicable HAQQ applications or commission software for your teams on top of Caesar. Your developers can also integrate the engine into applications they build.

Implementation and support

Work with HAQQ on data connections, workflow configuration, custom development, training and support. Agree the services and responsibilities your deployment needs.

Discuss your requirements

Make every external connection a deliberate choice.

Your data never reaches the frontier models. Your deployment defines which requests stay local and what may be sent outside.

Local models

Use models hosted within the agreed environment for workloads that must remain inside that boundary.

Approved external models

Permit external reasoning where the task and policy allow it. Review data handling, retention and provider terms before enabling the route.

Your model credentials

Use supported model providers through your own API credentials where agreed. This option concerns model access and billing; encryption-key arrangements are reviewed separately.

Customer knowledge stays customer knowledge.

HAQQ’s architecture excludes customer data from training HAQQ models. External providers, if enabled, are subject to their own agreed processing terms. Review those terms as part of the deployment.

Model examples. Enabled integrations and API credential options are defined for your deployment.

Give your team results it can examine.

Review the source material behind an answer, the versions behind a draft and the recorded tool activity behind an action. The deployment defines what is captured and which reviewers can inspect it.

Inspect the basis

Review the source material used and the relationship between the evidence and the result.

Follow the work

Inspect the activity and changes captured in the audit record for the workflow.

Retain responsibility

Define who reviews, who approves and what may proceed after approval. Fit those steps to the consequence of the action.

Agree who owns each decision.

The deployment plan should make responsibilities explicit. Use this as the starting point for the operating model we agree with your team.

Decision	Your institution	HAQQ
Data and sources	Authorize the material and the people who may access it	Configure the agreed connections and access scope
Hosting and model policy	Define residency and permitted processing	Design the deployment and model routes to that scope
Workflow permissions	Decide what the workflow can do and who approves	Configure the tools and review steps
Evaluation	Define the acceptance criteria and responsible reviewers	Support testing and refine the implementation
Operations	Agree internal ownership and escalation	Agree support, monitoring and maintenance responsibilities
Encryption keys	Can manage its own keys, for enterprise deployments	Cannot read the encrypted data once a key is revoked

Put the details on the table.

Bring your security, architecture and procurement teams into the discussion. We’ll work through the requirements that determine whether the deployment fits your institution.

Aligned withSOC 2Trust Services CriteriaCompliant

Aligned withISO 27001Information securityCompliant

Aligned withISO 42001AI managementCompliant

Aligned withGDPRProcessor obligationsCompliant

Data location, processing flows and external providers
Identity, permissions and administrative access
Encryption, retention, deletion and recovery requirements
Logging, human approval and incident responsibilities
Applicable standards, contractual terms and available assurance evidence

Start the security discussion

Bring your requirements. Let’s work through them.

We’ll start with your data boundary, the workflow you want to deploy and the controls your team needs to evaluate.

Talk to HAQQ

A 30-minute conversation with the HAQQ team.

What we’ll cover

The task and the result your team needs
Your data, software and hosting requirements
The first deployment and how to evaluate it

Choose a time

Open the booking page

Calendar not loading? Open the booking page.