Pricing

Every factual claim links back to its source. A groundedness check audits every answer; ≥90% grounded is the target. When the knowledge base doesn't cover a question, Braize says 'I don't know' rather than guess.

Each workspace lives in one isolated data store in your chosen region. Embeddings — which are personal data — never leave that store. Logs, analytics, backups, none of it.

Every change to a source document triggers a targeted re-index of just what changed; the answer cache invalidates the moment the document does, not on a clock. Every doc carries a 0–100 freshness score you can act on.

Only what they're allowed to see. ACLs from the source — Google Drive folder permissions, Slack channel membership, Notion workspace visibility — are pre-filtered inside the retrieval query, not post-filtered.

No. Configure the knowledge once, then ship the widget snippet, install the WhatsApp app, add the Slack app, hand a developer the REST endpoint, or share the agent endpoint. Same brain, every mouth.

Ingested content is scrubbed before indexing — HTML stripped, hidden instructions removed. Retrieved content is then treated as data, not instructions, at answer time.

Profile → Language. English (default) and Persian (Farsi RTL). The preference follows you across devices and is persisted to your identity profile.

Data residency. UAE PDPL and EU GDPR both reward clarity here. Per-workspace processing policies (allowed_inference_regions, ZDR-required, local-only) hard-fail rather than silently fall back.