Connect sources once
Website pages, files, Drive, Notion, Slack, Zendesk, and Intercom sync into one workspace-scoped knowledge base.
The living knowledge layer
Your docs, answering — with citations, in every channel.
Braize sits between your sources (Drive, Notion, Slack, your website, your files) and every place customers and employees ask questions. Connect once. Get cited answers everywhere — freshness-aware, permission-pre-filtered, region-pinned.
Free tier — no credit card. me-central-1 live, eu-central-1 on request.
Speaks fluently:DriveNotionSlackWhatsAppZendeskIntercomMCP
Watch it work
How Braize works, in thirty seconds
Sources connect, knowledge stays current, an answer arrives with its citation, and the same answer lands in every channel — no glue, no five separate bots. The controls below let you scrub, pause, or restart.
The product, plainly
What is our product?
Braize is a living knowledge layer that turns your company sources into fresh, permission-aware, cited answers across every customer and employee channel.
How does it help?
It removes the operational work of keeping five answer channels accurate, permission-safe, and synchronized with the source of truth.
Keep knowledge alive
Changed chunks re-index without re-embedding everything, stale documents are flagged, and conflicts are surfaced before answers drift.
Filter before retrieval
Workspace, region, user identity, groups, and public scope travel with every request, so unauthorized content is never retrieved.
Answer with proof
Every response is grounded in source documents and returned with citations that customers, employees, and auditors can inspect.
Serve every channel
The same brain powers a web widget, WhatsApp, Slack, REST API, MCP agent endpoint, and helpdesk feed.
Stay region-bound
Each workspace has one isolated regional data store; processing policy controls where inference is allowed to run.
Three jobs, one product
What Braize does
Connect anything
Website · Files · Google Drive · Notion · Slack · Zendesk · Intercom. ACLs mirrored, freshness inherited.
Answer everywhere
Widget · WhatsApp · Slack · REST API · MCP. One brain, five mouths. No glue layer.
Stay alive
Chunk-diff re-indexing · conflict detection · staleness prediction. Every answer is verifiably current.
How it works (the technical version)
Sources → Living knowledge → Cited answers
Each stage is independent, so we can scale or replace one without disturbing the others. Region and workspace context travel with every request — your data never lands in the wrong place.
Sources
Website crawler
Files (PDF/DOCX/…)
Google Drive
Notion
Slack (read)
Zendesk / Intercom
Pipeline
Parse + Chunk + Embed
vision · forms · tables · content-hash
Freshness Engine
diff-aware reindex · conflict triage
ACL pre-filter
identity · groups · public-scope
Brain (workspace)
Isolated data store
docs · embeddings · ACLs
Hybrid search
keyword · semantic · context
Answer + cite
region-bound · ZDR-aware
Groundedness check
every answer · 100%
Channels
Web widget
Slack app
REST API
Agent endpoint
Helpdesk feed
Infrastructure
SSO + identity
standards-compliant · per-workspace
Scheduled jobs
freshness · reindex · conflict triage
Event bus
transactional · idempotent · auto-retry
Outbound proxy
SSRF guard · safe fetches
Edge routing
regional · fail-over · cached
Connect anything
The sources Braize already speaks
- Google DriveFull ACL mirroring
- NotionPages + databases
- SlackChannels + threads
- ZendeskArticles + tickets
- IntercomHelp center + chats
- WebsiteSitemap + JS-rendered
Answer everywhere
The mouths Braize already drives
- Web widget<50KB · streaming
- WhatsAppofficial messaging API
- Slack@mention + DM
- REST APItyped contracts · streaming
- MCPagent-ready endpoint
- Helpdesk feedsearch integration
Who Braize is for
Four people whose week Braize changes
Amal
Operations lead, e-commerce
“Our return policy changed last week. The bot still quotes the old one.”
Braize's freshness engine flags the stale doc, links every answer back to the policy file, and the new one ships to the widget in under five minutes.
Web widget · WhatsApp
Dev
Platform engineer, B2B SaaS
“I need an MCP endpoint our customers' Claude agents can call — without writing five auth flows.”
The MCP endpoint comes with four search tools, delegated identity, and a region-bound URL — your customers' Claude or ChatGPT agents discover it automatically and respect each end-user's permissions.
REST API · MCP
Elena
Internal-tools lead, HR + IT
“People keep asking @aize public questions, but engineers want it to see private Drive folders too.”
ACL mirroring from Google Drive — each Slack user sees only what their Drive identity is allowed to. Permission pre-filtered inside the query, not after.
Slack · Drive
Omar
CTO, regulated industry
“Compliance requires our data — and our inference — stay in-region. ZDR endpoints only.”
One workspace, one isolated data store, one region. Choose which regions inference can happen in, require zero-data-retention endpoints only, or lock everything in-region. Hard fail, never silent fallback.
All · region-pinned
Every feature, in one place
The full inventory
Pick a category to dive in. Every feature lists the tier it becomes available at.
Ingestion
7 featuresf1Website crawler
Sitemap discovery, JS-rendered pages, learned-cadence re-crawl.
Free+f2File upload
PDF / DOCX / XLSX / CSV / MD / HTML / images, malware-scanned at ingest.
Free+f3Google Drive sync
Full ACL mirroring, group expansion, deletes ≤15 min.
Growth+f4Notion connector
Page + database selector; workspace-visible ACL (disclosed).
Starter+f5Slack as a source
Channel selector with membership ACL honored, threads as documents.
Starter+f6Zendesk / Intercom feed
Help-center articles + opt-in tickets; PII redacted before indexing.
Growth+f31Outbound security proxy
Blocks malicious outbound fetches at the network boundary, including DNS-based attacks.
Free+
Honest pricing
Pricing
Real values from plans.json. Annual: two months free.
Free
$0
100 pages · 200 q/mo · widget only
StartStarter
$59
2,000 pages · 2,000 q/mo · +1 channel
StartGrowth
$249
20,000 pages · 10,000 q/mo · all channels
StartBusiness
$699
100,000 pages · 50,000 q/mo · SSO · audit
StartBuilt for sovereign teams
UAE PDPLEU GDPREU AI Act Art 50ZDR-aware routingRegion-pinned data
Live: me-central-1 (UAE). Ready: eu-central-1 (EU). Each workspace is pinned to one region; embeddings never leave it.
FAQ
How does Braize avoid making things up?
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.
What does 'region-pinned' actually mean?
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.
How fresh is the answer?
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.
Can Braize see my employee's private files?
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.
Do I have to wire every channel?
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.
What about hallucinations from prompt injection?
Ingested content is scrubbed before indexing — HTML stripped, hidden instructions removed. Retrieved content is then treated as data, not instructions, at answer time.
How do I switch language?
Profile → Language. English (default) and Persian (Farsi RTL). The preference follows you across devices and is persisted to your identity profile.
Why one region per workspace?
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.