Read-only by construction
Chat SQL runs as a dedicated read-only Postgres role, then a second check rejects anything that is not a single SELECT (or WITH). Generated queries cannot insert, update, or delete warehouse rows.
Security
Designed so Chat cannot rewrite your data
The warehouse role Chat uses is read-only. Queries are validated before they run. Connector secrets are encrypted. That is the contract — not a promise we’ll add later.
Your warehouse, your tenancy
Each organisation’s connectors and warehouse tables are scoped to that organisation. Members only see data they are allowed to query.
Credentials stay encrypted
OAuth tokens and API keys for connectors are stored encrypted. You can revoke access in the source system or disconnect in Mirrorstone.
Sign-in you can tighten
Password login, optional authenticator 2FA, and organisation-level controls. OData feeds can be restricted to an IP allowlist.
You choose the model path
In-app Chat can use Mirrorstone’s shared AI, an organisation key, or a personal key. Questions and schema context go to the provider you configured — not a mystery third pipeline.
Evidence over black boxes
When an answer matters, open Evidence. See the steps and the SQL. That is the product, not a slide.
Organisation admins control members, connectors, and (where the plan allows) OData IP allowlists. Platform operations are handled by Mirrorstone App Admin — not by other tenants.