Every query through a contract. Every contract audited.
Governance isn't a feature you toggle on. It's how Gaur works. Access rules and audit logs travel with every contract call, whether the caller is a dashboard, a customer-facing app, or an AI agent.
Three things, by default.
Rules attached to each contract. Resolved from the auth context bound to the API key and the request context your backend sends.
Every query, every result, every caller. Whether the caller is a person, an app or an AI agent.
When something is off, Gaur returns a clear error code your backend can branch on, not a wrong number.
Two contexts. One decision.
Each contract's access rules read from two places. The auth context is bound to the API key when it's issued. The request context is sent by your trusted backend on each call, like the tenant or user the request belongs to.
Same data. One place to enforce it.
- Access checks rebuilt for each new endpoint
- Audit trails scattered across services, or missing entirely
- AI agents querying without the same governance as your apps
- Bad queries silently return data anyway
- One contract owns the access rules. Every caller goes through it.
- One audit log, end to end, across every protocol and every caller
- Agents query the same contracts as humans, under the same rules
- Wrong queries return errors with stable codes, not silently wrong data
Governance applies everywhere a contract is called.
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.
