Viz Flowics is a cloud-based platform that requires outbound internet access to function correctly. If your organization uses a firewall, proxy, or content filtering system, make sure the domains and ports listed below are allowed before deploying Flowics in your production environment.
Required ports
Port | Protocol | Purpose |
80 | HTTP | Fallback communication |
443 | HTTPS | Primary communication: Graphics Editor, Remote Control, API |
All Viz Flowics services communicate over standard web ports. No non-standard ports are required.
Domains to allowlist
The following domains must be accessible from any machine running Viz Flowics:
Core platform
*.flowics.com*.engage.flowics.com*.api.flowics.com
Assets and media delivery
*.cloudfront.net*.amazonaws.com
Authentication
*.auth0.com(if using Flowics native authentication)Your SSO provider domain (if using SSO — e.g.
*.okta.com,*.azure.com)
Social media connectors (if using Flows or social data)
*.twitter.com/*.x.com*.facebook.com*.instagram.com*.youtube.com*.twitch.tv
Note: If you are unsure which social connectors your organization uses, contact your Flowics administrator or the support team.
Bandwidth recommendations
Use case | Recommended speed |
Graphics Editor (design work) | 5 Mbps or more |
Remote Control / Rundown Control (live operations) | 3 Mbps or more |
Middleware (data sync) | 3 Mbps or more |
Multiple operators simultaneously | 10 Mbps or more |
These are minimum recommendations. Higher bandwidth improves responsiveness, particularly when working with large assets or real-time data updates.
Note: For live operations, latency and network stability are often more important than raw bandwidth. A stable 3 Mbps connection will generally outperform a 50 Mbps connection with intermittent drops.
Proxy and VPN considerations
Viz Flowics is designed to work over standard internet connections. If your organization uses a proxy or VPN:
Ensure WebSocket connections are not blocked: Viz Flowics uses WebSockets for real-time communication between the editor, remote control, and the output
If graphics load in the browser but do not update in real time, a WebSocket restriction is the most likely cause
Contact your IT team to confirm WebSocket traffic is allowed through your proxy configuration
For IT teams
If you need to validate connectivity before deploying Flowics, a quick way to confirm is:
Open
https://engage.flowics.comfrom the target machineConfirm the login page loads correctly
Open the browser developer tools (F12) → Network tab and look for any blocked requests
If specific domains need to be added to an allowlist and are not listed above, contact the Flowics support team, and we will provide the full list for your configuration.
Self-hosted assets and CORS
If your organization hosts assets such as images or videos on your own servers and references them from Flowics graphics, your server must be configured to allow cross-origin requests from Flowics.
Contact your IT team or hosting provider to configure CORS and allow requests originating from Flowics domains. Without this, the browser will block the asset from loading, and it will not appear in the graphic output. This is a common cause of images or fonts appearing correctly in the Graphics Editor but not in the live output.
Before you deploy
✅ Ports 80 and 443 are allowed outbound
✅ Required domains are allowlisted
✅ WebSocket traffic is permitted
✅ The authentication provider is reachable
✅ Connectivity test completed successfully