Built to be handed data not everyone may see.
Governance isn't a setting you switch on — it runs through every query, every share, and every scheduled send.
Encrypted & authenticated
Customer data encrypted at rest (provider-managed keys); connection credentials sealed separately; role-based login with revocable sessions; HTTPS, secure cookies, security headers, and login rate-limiting.
Row-level security that fails closed
Each viewer sees only the rows they're entitled to, enforced server-side inside the query. If a policy can't resolve, it shows nothing rather than leaking.
Governed AI
The assistant reads only approved data through a guarded query layer with a read-only allow-list. It can't run arbitrary commands or reach beyond what you permit.
We don't train on your data
Qeries does not train or fine-tune any AI model on your data. Our AI provider, Anthropic, is contractually barred from training on the data we send it. If you connect your own Anthropic key, your own agreement with Anthropic applies. Anthropic keeps requests for a limited period for safety monitoring. Each organization's data is isolated from every other organization's, and this is enforced on the server.
Access control that holds
Grant access by person or group at the dashboard, folder, or data-source level, with a clear deny-wins model and request-and-approve sharing. No "anyone with the link".
Isolated by organization
Every client is a separate workspace with its own users, data, connections and dashboards. Cross-workspace access is denied by default and enforced on the server, not in the browser — so a reader who goes around the interface gets the same answer.
Hosted in the EU · data residency
Your data is stored in Frankfurt, in the EU. When you ask the AI a question, the question, a limited sample of result rows and any file you attach are processed by Anthropic outside the UAE. We do not offer UAE hosting today.
Audit & cost control
Logins, permission changes, shares, and scheduled sends are recorded per workspace, and AI usage is rate-limited with a hard spend ceiling.
Straight about where we are.
We're in private preview and won't claim certifications we don't yet hold. Here's the honest state — and where we're headed.
GDPR-aligned, EU-hosted
Data is hosted in the EU by default and handled in line with GDPR principles — data minimisation, purpose limitation, and your right to deletion.
No certifications yet
We hold no SOC 2 or ISO 27001 certification and have not had an external penetration test. We would rather say so than imply otherwise, and we'll walk your security team through the controls in place today.
One shared instance, in Frankfurt
Qeries runs today as one multi-tenant instance in Frankfurt. It is containerised, but no dedicated, in-country or customer-cloud deployment exists yet, so we don't offer one.
Shared infrastructure, bounded
Workspaces are isolated in data and access, not in compute — today they share processing, with a memory ceiling per query so no workspace can exhaust the platform.
Two-factor and Microsoft/Google sign-in today
Two-factor sign-in and Microsoft or Google sign-in for company accounts are available today, with role-based access and revocable sessions. SAML single sign-on and SCIM provisioning are not built yet; they are on the roadmap.
Recovery objectives
Recovery point objective: 24 hours (backups are taken daily). Recovery time objective: 8 hours from when Qeries becomes aware that the service cannot be restored in place. These are objectives, not service levels.
