GitBook or Sendora — pick the trade-off, not the marketing.
GitBook nails the docs-site UX. The docs sit alone though — your help center is somewhere else, your AI bot reads a different corpus, your support inbox doesn't know which articles a user read before opening a ticket. Sendora KB delivers the same docs-site surface (`sendoracloud.com/help/<orgSlug>`) AND powers AI chatbot RAG AND in-app `kb.search()` AND Support cross-link in one tenant.
Polished docs site for developers. Beautiful UI. Lives in GitBook's silo — separate from your help center + AI bot.
Knowledge Base whose articles auto-feed the AI chatbot, in-app search, support inbox, and public help site.
Side-by-side
| Capability | GitBook | Sendora |
|---|---|---|
| Public docs site (SEO-indexed) | ✅ industry-leading editor + design | ✅ SSR'd at `/help/<orgSlug>`, 60s revalidate |
| Markdown body | ✅ + rich editor | ✅ — Markdown text, renderer on consumer |
| Article versioning | ✅ | ❌ — single current version only |
| AI bot grounded in docs (RAG) | ✅ GitBook AI add-on | ✅ via Contact Widget (gpt-oss:20b) |
| Custom domain | ✅ | ❌ — not built |
| In-app search SDK | Limited | ✅ `kb.search()` |
| Automatic ticket deflection (Support inbox suggests KB articles) | ❌ | ❌ — not built; chatbot RAG does this for the widget path only |
| Article-view → Customer profile event on analytics bus | ❌ | ❌ — view bump is a column update, NOT an event today |
| Helpful-vote endpoint | ✅ | ❌ — column exists, no endpoint |
| GitHub sync workflow | ✅ | ❌ |
| Pricing model | Premium $65/site + $12/user (5 editors ≈ $125/mo) | Bundle |
Why teams switch to Sendora
- If you also need the Contact Widget AI bot grounded on YOUR docs, Sendora delivers KB + bot in one tenant.
- In-app `kb.search()` SDK out of the box — no separate Algolia DocSearch.
- Bundled price instead of per-collaborator that scales steeply.
When GitBook is the right call
- GitBook's editor UX is genuinely beautiful + has years of polish on us.
- You need versioning, custom domain, GitHub sync workflow, helpful-vote endpoint — none are built in Sendora today.
- Your dev-team-facing docs need GitBook's specific GitHub-sync workflow.
- You don't need the rest of the Sendora surface — KB-as-standalone is GitBook's sweet spot.
Knowledge Base
Write once. Render as public help page (`/help/<org>`), AI chatbot RAG context, in-app `kb.search()`. Honest about the gaps.
Most help-center tools give you one surface. Sendora KB powers three for real today: public SSR'd help page at `sendoracloud.com/help/<your-org>`, AI chatbot grounding via gpt-oss:20b RAG, in-app SDK `kb.search()`. Honest about what's NOT built: custom-domain on the public page, auto-link to incoming Support tickets, KB-read timeline inside ticket detail, helpful-vote endpoint (the column exists but no POST route), `kb.article_viewed` event emitted to the analytics bus (view bump is a column update, not an event).
Switch from GitBook. Keep your weekend.
Free plan covers real product use, no credit card. Bulk hash import for auth, CSV import for profiles, schema-validated event import for analytics — Data Sync module handles the migration in a day.