Deployment
Three ways to run it. Same platform in all three.
Where the data sits and who operates the environment are the two decisions that shape everything else. They are yours to make, and nothing about the product changes with them: the same models, the same workspace, the same admin console.
Pick the row your policy allows
Start from the constraint you cannot move — a residency rule, a classification, an existing cloud account — and the mode follows from it.
Your infrastructure
Deployed into your own AWS, Azure or GCP account, in the region you choose.
- Data never leaves your cloud account
- Your keys, your network policy, your region
- Fits an existing landing zone and its controls
Suits
Organisations with an established cloud footprint and a residency requirement they can satisfy inside it.
Who operates it
You own the account and the network policy. We deploy into it and support it.
Your data centre
Runs inside your own perimeter, with an air-gapped option.
- Zero external access when air-gapped
- Suits regulated and classified environments
- Nothing egresses without your say-so
Suits
Regulated and classified environments, and anywhere egress is the thing being controlled.
Who operates it
You operate it end to end. We provide the build, the upgrades and the support.
Fully managed
A dedicated environment we run, shared with no other organisation.
- Not co-tenanted with other organisations
- Managed upgrades and monitoring
- Fastest route to a pilot
Suits
Teams who want the isolation without standing up infrastructure — and the fastest route to a pilot.
Who operates it
We operate it. You keep the admin console, the policies and the audit log.
The differences, in one table
Read down your column. Anything not listed here is identical across all three, which is most of the product.
| Private cloud | On-premise | Isolated tenant | |
|---|---|---|---|
| Where documents are stored | Your cloud account | Your data centre | A dedicated environment we run |
| Who operates the environment | You, with our support | You, with our support | We do |
| Model access | The full roster | The full roster | The full roster |
| Air-gapped option | No | Yes | No |
| Admin console, policies and audit log | Yours | Yours | Yours |
| Training on your content | Never | Never | Never |
| Edition | Enterprise | Enterprise | Enterprise |
| How it is priced | Quoted | Quoted | Quoted |
All three deployment modes are Enterprise-edition capabilities. Team and Growth run on our standard cloud storage, which is encrypted and access-controlled but not dedicated to one organisation.
What a pilot actually is
“Start your pilot” appears on this site more than once, so here is the shape of it rather than the phrase.
| Length | 30 days. |
|---|---|
| What it runs on | Your own documents, not a demo corpus. |
| Where it runs | Your infrastructure or ours — the pilot does not commit you to a deployment mode. |
| Security review | Yours, on your terms, before anything is uploaded. We would rather answer the hard questions early. |
| Support | A named person for the duration. |
| Seats | Agreed with you before it starts, sized to the team doing the evaluating. |
| What counts as success | Agreed with you before it starts, in your terms, and reviewed against those terms at the end. |
| What happens at the end | You keep your data and your documents either way. If it does not prove out, nothing carries over. |
Deployment questions
Where data lives, what reaches a model, and who can see what.
Where is my data stored?
You choose. AI+ Pro supports institution-owned storage (data stays on infrastructure you control), private cloud options (dedicated environments not shared with other organizations), and standard cloud storage (enterprise-grade encrypted storage managed by us). All options include end-to-end encryption and strict access controls.
What happens to my files after I upload them?
Files are processed within your approved infrastructure and remain under your control. They're used only to answer your specific queries through RAG and are not shared with other users or organizations, used to train AI models, accessible to third parties, or retained longer than your data retention policy specifies.
Can my organization control who has access to what?
Yes. AI+ Pro includes enterprise-grade access management allowing you to set role-based permissions at user, team, and department levels, control which AI models different users can access, restrict certain features based on security policies, monitor usage through detailed audit logs, and revoke access instantly when team members change roles.
How does AI+ Pro ensure data protection?
We implement multiple security layers: data encryption in transit and at rest, role-based permissions determining who sees what, complete tracking of system access and usage, no external training on your data, and infrastructure designed to support GDPR, CCPA, PDPA, and industry-specific requirements.
Can we run a pilot before full deployment?
Yes, pilot programs are supported to test the platform with a smaller group.
Can we use AI+ Pro with our existing systems?
Yes — and it plays beautifully with the tools you already use. From Notion, Slack, G-suite and more than 10 other systems, AI+ Pro fits right into your workflow.
Tell us the constraint you cannot move — a residency rule, a classification, an existing cloud account — and we will tell you which of the three fits and what the review needs.