Sovereign AI Private Deployments
Available deployment options include HAQQ Cloud, private cloud in your own tenancy and, where agreed, on-premise. The option and region are agreed per deployment with HAQQ, and residency can be committed in your order form.
Choose where HAQQ runs
Where HAQQ runs, in which region and who holds the encryption keys are agreed per deployment.
The drawings show who controls each boundary. They do not show which models a task uses or where those models run.
HAQQ Cloud
We run it, in a region agreed with you. Encrypted and isolated per firm: your data is kept separate and cannot be reached by other customers, even where infrastructure is shared.
Private Cloud
Your own cloud tenancy, where agreed for your deployment. You hold the encryption keys, we operate the software inside your account.
On-Premise
Your own infrastructure, where agreed for your deployment. Your organization controls the infrastructure boundary.
HAQQ Cloud regions
European Union, United States, Middle East
Where residency is a contractual requirement, it is defined in your order form, so your security team knows exactly where processing takes place.
Keep control of data, keys and access
Data
In HAQQ Cloud, you choose the region your data is hosted in: EU, US or Middle East. Residency can be committed in your order form, and you configure retention to match your regulatory obligations.
Encryption keys
Enterprise customers can bring their own key and keep full control of the key lifecycle and rotation. Revoking the key ends our ability to read the data.
Models and training
Justinian® is architected to route different kinds of legal work to different models. The HAQQ terms governing a deployment exclude customer data from model training.
Access
SSO, MFA and role-based access for enterprise deployments, with actions logged, attributable and exportable. By default, HAQQ personnel do not have access to customer matters, and support access to a specific matter needs your explicit approval and is time-limited.
Go from scoping to rollout with a dedicated team
- 01
Scope
We align on deployment model, data residency, and your security and procurement requirements up front.
- 02
Integrate
Guided data migration and integration, mapped to your matters, templates and workflows.
- 03
Roll out
Role-based training and change management so lawyers and staff adopt HAQQ with confidence.
- 04
Support
A named success manager, priority support tiers and ongoing reviews.
Deploy it for your firm, legal team or institution
Law firms
Run matters, drafting, research and billing on one legal AI platform, in your region or on-premise as agreed per deployment.
In-house legal teams
Give your legal department drafting, review and research, with tenant isolation, SSO/SCIM and audit logs.
Bar associations
Bring member services online with eBar, and give members cited research, drafting and contract review.
Law, Justice & Compliance
Research the law with citations, read long files faster and start drafts from sourced answers. Your people review every output and make every decision.
At a glance
- Deployment model agreed with each customer
- HAQQ Cloud regions: EU, US or Middle East
- Customer-managed keys on Enterprise
- SSO, MFA and role-based access
- Actions logged and exportable
Get answers on private deployment
Can we run HAQQ in our own cloud, or on-premise?
It depends on the deployment you agree with us. Available options include HAQQ Cloud as a managed service, a private cloud inside your own tenancy and, where agreed, on-premise. The option, the region and who owns the perimeter are agreed per deployment.
Where is our data stored?
In HAQQ Cloud, you choose the region: EU, US or Middle East. If residency is a contractual requirement, it is defined in your order form so your security team knows exactly where processing takes place.
Can we manage our own encryption keys?
Yes. Enterprise customers can bring their own key and keep full control of the key lifecycle and rotation. Revoking the key ends our ability to read the data.
Does HAQQ use our data to train AI models?
For HAQQ, no. The HAQQ terms governing a deployment exclude customer data from model training.
Who at HAQQ can see our data?
By default, HAQQ personnel do not have access to customer matters. Access is governed through least-privilege controls and logging. Where support access to a specific matter is required, it needs your explicit approval and is time-limited.