Our EU cloud, or your own data centre.
HONESTAS runs in our EU cloud in Ireland or in your own data centre, and it is the same platform either way. Your keys and your model credentials stay yours. Sealed records are kept outside the installation, so nobody can rewrite them, not even us.
- Runs in
- Our EU cloud, Ireland
- Data kept
- Ireland, EU
- Backups
- Ireland, EU
- Key store
- Northgate key store
- Model credentials
- Northgate's own
- Rotated
- 1 Oct 2026
- Time stamps
- From outside the firm
- Countersigned
- 2 outside witnesses
One platform. Wherever your rules allow.
Both places get the same decision rooms, checks, seals and apps. What changes is who runs the hardware.
Run for you, in Ireland.
We run HONESTAS for you in our EU cloud in Ireland. Each firm gets its own private space, with its own keys and its own records. We apply updates on a schedule you can see.
- Data stored and processed in the EU
- Your own private space, keys and budgets
- Updates on a schedule you see in advance
- Where data lives
Ireland, in the European Union, for your data, your backups and your sealed records.
- Your own space
No other firm shares your space, your keys or your records.
- Our access
Our engineers reach your space only when you grant it, and every access is recorded.
On your hardware, under your control.
Install HONESTAS on your own Kubernetes, with your team and ours working side by side. Connect your own sign-in, your own key store and your own models on your own GPUs. You choose when each update goes in.
- Installed and checked step by step
- Your models, on your own GPUs
- Updates signed, and applied when you choose
- Your Kubernetes
The same platform as our EU cloud, installed in your own data centre.
- Your key store
Keys are created and held in your own key store, and never leave it.
- Signed updates
Every update is signed. One that fails the check is refused before it is installed.
Your keys. Your model credentials. Yours to withdraw.
Encryption keys live in your key store, and the model providers you use are called with your own credentials. Withdraw a key and the data it protects can no longer be read, in our cloud or yours.
| What | Held by | Last used |
|---|---|---|
| Data key | Northgate key store | 14:03:44 |
| Signing key | Northgate key store | 14:03:41 |
| Model provider B | Northgate's own credential | 14:02:58 |
| Your own model | On your GPUs | 14:02:51 |
Nobody at Adverant can read or use these keys.
Keys stay yours
Created and held in your key store. Rotate or withdraw them whenever you choose.
Credentials stay yours
Model providers are called with your own credentials, under your own contracts.
Records kept outside
Sealed records sit outside the installation, so a change to one would show.
Nobody can rewrite a record. Not even us.
Every sealed record gets a time stamp from outside your firm and is countersigned by outside witnesses. Copies are kept outside the installation, so a regulator or auditor can check any record with no account, wherever HONESTAS runs.
- Time-stamped from outside the firm
- Countersigned by two outside witnesses
- Checked by anyone, with no account
Who does what, in each place.
The platform is the same in both. Who runs it, and where the data sits, is what changes.
| Question | Our EU cloud | Your own data centre |
|---|---|---|
| Who runs the hardware | We do | You do |
| Where data lives | Ireland, in the EU | In your data centre |
| Encryption keys | Your key store | Your key store |
| Model credentials | Yours | Yours |
| Models | Models you approve, in the places you approve | Your own models on your GPUs, plus any you approve |
| Sealed records | Kept outside the installation | Kept outside the installation |
| Updates | We apply them, on a schedule you see | Signed, applied when you choose |
It runs on Adverant Nexus. One path for every model call.
HONESTAS is built on Adverant Nexus, Adverant's AI backplane. Every model call in HONESTAS goes through one dispatch path. It checks that the model is approved for that job and that place, applies your budget and records which model and version answered.
- Only approved models, only in approved places
- Every call recorded with its model and version
- The same path in our cloud and in yours
| Time | Job | Model | Where |
|---|---|---|---|
| 14:02:51 | Case for, CLM-4471 | Your own model 2026.07 | Your GPUs |
| 14:02:58 | Second-model check | Provider B | EU west |
| 14:03:02 | Draft the letter | Provider B | EU west |
| 14:03:10 | Summarise a report | Provider C | Refused |
A call to a model not approved for the job or the place is refused and recorded.
Where it runs, in practice.
Is it the same product in both places?
Yes. The decision rooms, checks, seals, apps and contact centre are the same in our EU cloud and in your own data centre.
Can we start in your cloud and move later?
Yes. Records, settings and sealed history move with you, and every record still checks out after the move.
Whose AI keys are used?
Yours. Model providers are called with your own credentials, under your own contracts, and you can withdraw them at any time.
Where are sealed records kept?
Outside the installation, with time stamps and countersignatures from outside the firm, so neither you nor we can rewrite one without the change showing.
Can another firm see our data?
No. Each firm has its own private space, keys and records. Where firms work together, such as a lead and following markets, walls decide what each one sees.
Go deeper
Tell us where it has to run.
Bring your hosting and data rules. We will show you the setup that fits, and how to move later.