Who this comparison is for
Chat Core highlights
- Explainable decisions (Trace) + experiments & budgets
- Data residency + model allowlists + prompt firewall
Rasa (open source) highlights
- Full OSS control and extensibility
- Local deployment, components, and policies
Capability matrix
| Capability | Chat Core | Rasa (open source) | Notes |
|---|---|---|---|
| Session orchestration & stitching | Native | Partial | Custom tracker stores; cross-channel stitching DIY |
| Handoff to human (queues/SLA/macros) | Native | Partial | Requires CCaaS integration/workflows |
| LLM provider abstraction & tools | Native | Partial | OSS components possible; central policy in Chat Core |
| Guardrails (moderation/DLP/prompt FW) | Native | None | DIY with middleware/plugins |
| Event bus (Kafka/EventBridge/SSE) | Native | Partial | Connectors/plugins in OSS |
| Self-host/on-prem control | self_hosted | self_hosted | Both support private deployment |
- Use together: keep Rasa dialogs; let Chat Core orchestrate multi-bot routing & handoff.
- Tokens: full/partial/none/native/addon/self_hosted.
Total cost of ownership
Rasa lowers license cost but shifts orchestration, safety, and handoff to custom build. Chat Core centralizes those layers, reducing glue code and day-2 ops.
Assumptions
- Two OSS bots, 4 channels, enterprise governance required
Migration plan
From Rasa · Keep Rasa; register as an Actor; move routing/guardrails to Chat Core
-
1
Expose Rasa endpoint as a tool/function to Chat Core
-
2
Define routing rules/skills and handoff queues
-
3
Enable guardrails, budgets, and event streaming to analytics
Security
- RBAC, audit logs, SIEM export, data residency & redaction
Evidence & sources
| Claim | Value | Source |
|---|---|---|
| Prompt firewall | Input/output policies with block/strip/redact | product_docs |
About Chat Core
Chat Core decides what happens next in any live conversation. It stitches identity across channels, maintains durable sessions, detects intent and sentiment, calls tools and knowledge bases, and chooses between automated replies or human handoff with clear SLAs. Operators get routing/skills rules, cost & safety guardrails, experiments, and an orchestration trace for explainability.
Tightly integrated with PulseGate for transport, LiveConnect for real-time inbox, Agent Desk for tickets, FlowForge for automation, Chronicle for audit-ready timelines, and InsightLake for analytics—so you can ship omnichannel support that scales safely.