WebChat — Deployment & Integration Guide

💡 Using Banza-hosted WebChat? No deployment needed. Skip directly to Section 4. Getting the Widget Embed Code.

Local Deployment (Special Cases Only)

⚠️ WebChat and m3 can be deployed locally on the client’s infrastructure only in special cases (e.g. data residency requirements, isolated networks). Contact Banza before proceeding with local deployment.

1. Network Communication Diagram

image.png

image.png

Communication Flow

All WebChat components are deployed on the client’s infrastructure using Docker Compose.

From To Protocol Description
Browser Load Balancer HTTPS All inbound traffic from the end user
Load Balancer WebChat Backend :5000 HTTPS REST + WebSocket API calls and real-time GraphQL subscriptions
Load Balancer WebChat Frontend :3000 HTTPS Admin portal traffic
WebChat Backend m3 Product HTTPS Outbound requests to client’s chat engine
m3 Product WebChat Backend HTTPS Webhooks and callbacks from m3
WebChat Backend PostgreSQL :5432 TCP (internal) Database access within Docker network

🔒 Security Recommendation (ISO 27001 — Least Privilege Access)

Block access to the following endpoint from external networks via Firewall:

<webchat-backend-url>/api/Auth/Login

Allow this endpoint only from the internal network or trusted IP addresses (m3 server, admin hosts).

2. Deploying WebChat on Client Side

Prerequisites