The VU.CITY Hub allows users to run VU.CITY and SiteSolve through a web browser without the need for high-spec computer hardware or a traditional desktop installation. We use real-time streaming and WebSocket technology to deliver this interactive design environment via our cloud infrastructure.

VU.CITY and Sitesolve require access to a modern operating system and web browser to function.

Supported operating systems

Windows 10 or later

macOS 14 or later

Mobile devices running iOS or Android are not currently supported.

Supported browsers

Chrome, Firefox, Edge, Brave, Safari*

Note: Internet Explorer is not supported.

* Safari is supported but may occasionally present issues with cursor position and display resolution. An alternative browser is recommended where possible.

Networking Requirements

Support for WebSockets can be tested using any standard WebSocket testing service, such as this one.

VU.CITY now fronts all streaming traffic through its own Secure Gateway Appliances (SGAs):

• sga1.vu.city (IP 54.246.37.83)
• sga2.vu.city (IP 34.243.85.79)

The wildcard domain *.vu.city covers legacy VU.CITY-managed application, gateway, and platform endpoints, including VU.CITY 3D, SiteSolve, Secure Gateway Appliances, and related services and should be retained for the time being.

Outbound Ports:

• TCP 443
• TCP 80
• UDP/TCP 3478

Inbound Ports:

• UDP 49152–65535 (to VU.CITY SGAs only)

Third-Party Requirements

VU.CITY and SiteSolve interact with the following third-party domains;

• vucity-frame.web.app
• *.nutanix.com
• *.difr.com
• *.cloudfunctions.net
• *.auth0.com
• api-js.mixpanel.com
• api.hsforms.com

Further detailed third-party requirements can be found here, if required;

Auth0

Nutanix Frame / Dizzion

Proxy, inspection and filtering requirements

• All traffic between the end user and VU.CITY infrastructure is encrypted.
• Explicit proxy servers (proxy servers that the web browser is aware of) are supported.
• Transparent proxy servers (proxy servers that the web browser is unaware of) may interfere with WebSockets and should be bypassed for the above domains.
• If your organisation uses SSL inspection / HTTPS interception, exempt the listed domains. Inspecting authentication or long-lived WebSocket traffic can disrupt session loading.