Skip to main content

Domains to whitelist (firewall / proxy)

Written by Richard Lombos

If Verity pages won’t load, recordings fail to start, or practice-bot conversations never connect, your network security may be blocking required endpoints. Share the list below with your IT or network-security team so they can add the domains to your allow-list (whitelist).

Recommendation: Allow both HTTP (80) and HTTPS (443) traffic for every domain listed.


1. Core Verity platform

Purpose

Domain(s)

App & API traffic, Live AI services

*.wonderway.io

[Text] Conversation routing & streaming

chat-server-production-197480587934.europe-west3.run.app

[Voice] Conversation routing & streaming

practice.wonderway.io

[Video bots] Conversation routing & streaming

avatar-server-197480587934.europe-west1.run.app


2. Google Cloud services

Verity relies on Google Cloud for authentication, storage, and real-time data.

Purpose

Domain(s)

Google APIs

*.googleapis.com

Static assets (fonts, scripts)

*.gstatic.com

Firebase services

*.firebaseio.com
*.firebasedatabase.app

3. For audio/video bots only

Verity relies on Live-kit for audio/video bots

Purpose

Domain(s)

Port

Signal connection over secure WebSocket

*.livekit.cloud

TCP: 443

TURN/TLS. Used when UDP connection isn't viable

*.turn.livekit.cloud

TCP: 443

TURN/UDP servers that assist in establishing connectivity

*.host.livekit.cloud

UDP: 3478

Did this answer your question?