KobiGPT vs CustomGPT
The split is directional: an outward-facing website bot, or an internal department assistant?
TL;DR
Choose KobiGPT when you need specialist assistants with citations from your files, TR/EN support, and predictable Kobi Kredi usage. CustomGPT may win on ecosystem lock-in—validate with your IT checklist.
Quick facts
- Citations
- KobiGPT: document snippets
- Deployment
- SaaS + self-hosted path
- Pricing model
- Published SME tiers + Kobi Kredi
- Languages
- Turkish and English
Why teams choose KobiGPT
- Compare total cost including indexing and support hours.
- Test answer quality on your own PDFs and policies.
- Check data residency and KVKK alignment.
- Use our compliance checklist tool before rollout.
Product facts
- Ücretsiz plan
- 100 doküman · 2 departman · 120 Kobi/ay(PLAN_CONFIG)
- Starter
- 1000 doküman · 5 departman · 1000 Kobi/ay(PLAN_CONFIG)
- Pro
- 12500 doküman · 25 departman · 12500 Kobi/ay(PLAN_CONFIG)
- Doküman yükleme maliyeti
- 0.1 Kobi(packages/types/src/plan-config.ts → TOKEN_COSTS.DOCUMENT_UPLOAD)
- AI mesajı asgari maliyeti
- 0.1 Kobi(packages/types/src/plan-config.ts → KOBI_MIN_TURN)
Outward bots and internal assistants solve different problems
The common use case for RAG chatbot products is outward-facing: a bot embedded on a website answering visitor questions. In that scenario content is already public, access control is unnecessary, and the success metric is conversion.
An internal assistant solves a different problem. The content is confidential, "who can see which document" is the central question, and the success metric is a reduction in repeated internal questions. KobiGPT is built for the second scenario — which is why role-based access and per-assistant document scope sit at the centre of the product.
Why access control is central
In internal use the most serious risk is not a wrong answer but a right answer to the wrong person. A viewer-level user obtaining an answer from the payroll file is a design failure independent of model quality. In KobiGPT, assistants see only the files attached to them, and user roles determine which assistant can be reached.
When evaluating, test this scenario directly: attach a restricted file to an assistant, then try to query its content as an unauthorised user. That test tells you more than any feature list.
Multi-assistant structure and department templates
KobiGPT's default arrangement is not a single bot but one assistant per department. The Starter plan allows up to 5 and the Pro plan up to 25 assistants. Each runs with its own document set and its own system instruction.
Templates ship ready: general, accounting and finance, customer service, sales and marketing, human resources, legal and compliance. These are more than labels; each carries a system instruction written for its domain — the accounting assistant works in a VAT and tax context, the legal assistant in a data-protection context.
FAQ
Which is faster to pilot?
KobiGPT targets same-week pilots with direct document upload.
Can we use both?
Some teams keep Copilot for M365 and KobiGPT for SME docs.
Hallucinations?
RAG reduces but does not eliminate—always verify citations.
Enterprise SLA?
Contact sales for enterprise; cite public pages only.
Can we embed it on our website?
KobiGPT is designed for internal use. A public website bot is not the primary use case.
Can we write a separate system instruction per department?
Department templates come with their own instructions, and these can be adjusted to the organisation's needs.
Comparison
| Feature | KobiGPT | Alternative |
|---|---|---|
| Document RAG | Core | Varies |
| Assistant templates | Yes | Varies |
| SME pricing page | Public | Often sales-led |
| Self-hosted | Optional | Varies |