Security
Your data stays home.
The engine runs on your own machine. Raw values and identifiers never leave it — the language model that plans the analysis only sees aggregate results and column names.
What crosses the boundary
Stays on your machine
- Raw values
- Identifiers
- Your data files
Reaches the model
- Column names
- Statistics and counts
- Chart-ready summaries
How it is enforced
Privacy by architecture.
Designed for HIPAA-regulated environments and other settings where sensitive data, including PHI, cannot be uploaded to a third party.
Data boundary in the engine
An explicit boundary mechanism controls what can leave the engine. It is part of the architecture, not a policy promise.
Sign-in with Auth0
Authentication is handled by Auth0, with access organised into plan-based tiers.
Private networking
Cloud infrastructure runs on private networking with managed identities.
Per-engine identities
Each engine has its own identity, which can be enrolled and revoked.
Read the details.
The white paper explains the architecture and the data boundary in full.