KobiGPT vs Dust
Dust is a flexible agent platform; flexibility costs engineering effort. This decision turns on your team's technical capacity.
TL;DR
Choose KobiGPT when you need specialist assistants with citations from your files, TR/EN support, and predictable Kobi Kredi usage. Dust 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)
- Paraşüt (MCP)
- self_hosted(parasut_mcp)
- Tek Sistem ERP (MCP)
- self_hosted(teksistem_mcp)
- Hukuk kaynakları (MCP)
- self_hosted(hukuk_mcp)
- 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)
The trade between platform flexibility and setup effort
Agent platforms let you build customisable workflows and tool chains. That flexibility is a genuine advantage for scenarios a standard product does not cover — but it demands configuration, testing, and maintenance in return. Who will build it and who will update it are part of the deployment decision.
KobiGPT makes the opposite choice: department templates ship ready, the flow is fixed, and the customisation surface is deliberately narrow. You do not design a flow to stand up an HR assistant; you pick the template and attach documents. For complex multi-step automation scenarios, that narrowness is a limit.
Who builds it, who maintains it
This question is decisive in an SME context. A 30-person company usually has no dedicated platform team; setup falls to the HR manager or the finance lead. A platform requiring configuration either never gets deployed in that profile, or becomes dependent on a consultant — in which case total cost rises well above the licence price.
When evaluating, write setup and maintenance cost next to licence cost. Who will build it, how long will it take, and who takes over if they leave. Those three questions usually prove more decisive than a feature comparison.
What KobiGPT does on the tool-calling side
KobiGPT is not tool-free; it reaches live systems through MCP-based connectors. The Paraşüt connector reaches accounting records, the Tek Sistem ERP connector reaches production data, and the legal connector reaches official sources. The difference is that these arrive ready, with a predefined flow.
Tools requiring write permission ask for individual confirmation on every call; the assistant never creates or deletes a record on its own. That constraint reduces flexibility but increases auditability — which is usually what regulated processes want.
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 add our own tools?
You can connect your own MCP server over the MCP protocol. Custom tools outside the catalogue require configuration on the mcp-host side.
How much technical knowledge does setup require?
None for a document-based assistant — pick a template and attach files. Self-hosted connectors do require infrastructure-side setup.
Comparison
| Feature | KobiGPT | Alternative |
|---|---|---|
| Document RAG | Core | Varies |
| Assistant templates | Yes | Varies |
| SME pricing page | Public | Often sales-led |
| Self-hosted | Optional | Varies |