BlazorChat - Real-time chat component
Real-time chat component powered by BlazorRTE and BlazorEmo for embedded service workflows.
The Problem
Ever done a deployment and used MS Teams for coordination? If you have dozens of Favorites and multiple Teams, there's not enough room to show all the member names in bold when you have an unread message—they're pushed out of view. You literally have no idea there's a message waiting.
Beyond notification nightmares:
- Channel overload
Creating a Teams channel for every release, incident, or ticket gets messy fast. - SaaS pricing
Embedded chat APIs (Stream, SendBird) charge per message or MAU—costs scale with your growth. - Data sovereignty
You can't control where messages live, how long they're retained, or who has access. - Manual scoping
No way to auto-bind chat to your workflow ID (release number, ticket ID, task reference).
BlazorChat solves this by embedding chat directly in your workflow UI, auto-scoping to context, and giving you full control over data and infrastructure.
Built for operational workflows
BlazorChat is a real-time chat component designed for operational workflows such as deployment runbooks, incident response, change management, system monitoring, and more. Each chat thread is bound to your workflow identifier (release number, ticket ID, task reference, etc.), automatically isolating conversations by context without the need for manual channel creation. It enhances messaging with BlazorRTE for rich text editing and BlazorEmo for emoji support. We provide access to the messages—you control where they're stored, who can view them, how data is secured, and compliance with applicable regulations.
Features
- Context-scoped threads
Conversations auto-bound to your workflow ID with no manual channel setup. - Blazor-native integration
Consume the component entirely in C#; all JavaScript for scroll management and browser interactions is bundled and handled internally. - Rich text editing
Bold, italic, code blocks, and inline formatting — powered by BlazorRTE, with no additional configuration. - Emoji reactions
Powered by BlazorEmo. Users can react to any message; summaries broadcast to all connected clients in real time. - Full message lifecycle
Send, edit, delete, and react in real time. - @mention & offline notifications
Mention team members by name. The host app receives anOnOfflineMentionevent to notify users who aren't active — via email, push, Teams, or any channel you choose. - Rich event callbacks
Hook into message lifecycle, reactions, presence changes, connection state, and inbound messages — without modifying the component. - Flexible transport
Use the built-in in-memory service for demos and prototypes, or swap in SignalR via BlazorChat.Server for production — no component changes required. - You own your data
Bring your own storage, security, and compliance pipeline. - Component license, not SaaS
No per-message fees, no SaaS subscription.
Use Cases
- Deployment & Release Management
Chat scoped to each release automatically. - Incident Response
Real-time coordination tied directly to the incident ticket. - Change Management
Audit-friendly discussion thread per change record. - IT Service Management
Contextual chat embedded in your ticketing workflow. - Operations Dashboards
Team commentary attached to the data they are watching.
Cost Model
Most embedded chat solutions charge per monthly active user or per message delivered — costs that scale directly with your product's growth. BlazorChat is a flat annual organisation License: no SaaS subscription, no per-message fees, no MAU tiers. Your infrastructure bill stays flat regardless of message volume or team size.
- No per-message fees
Send as many messages as your app needs. - No MAU billing
Your user growth doesn't increase your licensing cost. - No vendor data pipeline
Messages never leave your infrastructure. - Predictable cost
A flat annual License costs less than a single month of comparable SaaS chat APIs.
Community
Free
Download, evaluate, and prototype with no commitment.
Runs on the built-in in-memory transport — ideal for local development
and demos. No persistence, no cross-server messaging, and no
BlazorChat.Server required.
Single-Tenant
Commercial
One organisation, unlimited developers, unlimited internal applications.
Includes BlazorChat.Server for SignalR-backed real-time messaging
with persistence via your own IChatRepository.
Ideal for teams embedding chat into their own operational tools.
Multi-Tenant
Commercial
For ISVs and SaaS platforms that redistribute BlazorChat within a product
served to multiple end-customer organizations. Tenant data isolation is
implemented through your own IChatRepository — BlazorChat
has no opinion on your storage or tenancy model.
Contact us for pricing.