Governed by default. Auditable by design.
Gaur is the serving layer for your analytical data. Access rules and audit logs travel with every contract, so every caller is governed by the same posture, human or otherwise.
Access, data handling, compliance.
Every call goes through a contract.
Apps and agents call contracts, never raw SQL or raw schemas. Each contract carries the access rules; each request carries its context.
- Per-API-key auth context, bound at key creation
- Per-request context set by your trusted backend, never the end user
- Row-level security resolved before any query runs
- Audit log of every query, every result, every caller
Read-only on the way in. Isolated on the way out.
Ingest uses read-only credentials on your source systems. Your data lives inside Gaur's engine, scoped to your workspace, served only through the contracts you publish.
- Read-only credentials on Snowflake, BigQuery, Postgres and the rest
- Workspace-level isolation between customers
- Encryption in transit and at rest
- No end-user-supplied context is trusted at query time
Working toward what enterprise teams expect.
We're early. We're honest about what's in place and what's in progress.
- SOC 2 Type II: in progress
- GDPR posture: data residency and DPA available on request
- HIPAA: not in scope today
- Security questionnaires answered on the demo call
From your sources to every consumer, through one engine.
Read-only credentials on your sources. Workspace-isolated storage inside Gaur. Every consumer reaches the data through a contract, never the warehouse directly.
A wrong query returns a clear error, not a wrong number.
Every contract is validated at definition time and again at query time. When something doesn't add up, Gaur returns an error with a stable code your backend can branch on. The dashboard never silently shows a number you can't trust.
You run your business.
We run your analytics.
Hop on a 30-minute call. We'll connect a sandbox to your warehouse and show you Gaur on your numbers.
