On-premise chat
Fully featured on-premise chat
The TalkJS chat API lets you build chat on your own servers, giving you full control over messaging data. Keep chat infrastructure within your own environment while delivering secure, real-time messaging inside your product.
Filter offensive or unwanted language to keep conversations respectful and safe.
Track individual chats in real time to keep discussions on topic and within guidelines.
Review chat activity over specific periods to understand engagement patterns and growth.
What you can build with TalkJS
Build any chat use case into your product with just a few lines of code. Frontend UI SDK and out-of-the-box notifications included.
Connect any two users in your product with private 1-on-1 conversations.
Let multiple users communicate in shared conversations for collaboration or discussion.
Enable real-time chat for large audiences during live events and broadcasts.
Let users message your support team inside your product, async or in real time.
Heads up: we’re seeing a spike in 429s on the REST API. Not huge, but it started after yesterday’s deploy.
Is it one endpoint or spread out? I can pull a breakdown by route + tenant.
Could be the new webhook delivery change causing clients to re-send when they don’t get a fast 200.
Do we have request IDs we can surface in the dashboard logs? Would make support triage way faster.
Yeah. We can thread a requestId through gateway → app → worker and include it in the webhook payload too.
Core capabiities
These core capabilities outline how TalkJS is deployed, operated, and maintained, giving you a clear view of the infrastructure, reliability, and operational requirements.
The TalkJS on-premise deployment matches the version we run on our own infrastructure. A single app server with failover support is sufficient, as each TalkJS server is built to handle many concurrent users, conversations, and messages.
TalkJS software updates are designed to be seamless and easy to manage. Updates are delivered via new Docker images published to Docker Hub, with ongoing updates and bug fixes included in the Enterprise on-premise package.
TalkJS stores all chat data in a Postgres database. If your application already uses Postgres, we recommend running TalkJS on a separate, dedicated database to ensure isolation, performance, and operational clarity.
Hardware requirements vary based on your use case and expected traffic. If you are unsure which hardware to provision, our solutions engineers can help you determine the right setup for your needs.