Detailed Network Requirements

For multi-user communication, Vrex needs permission to communicate towards our synchronization servers. By providing the following information to your IT department they will be able to open up for multi-user collaboration with Vrex.

SourceDestinationPortUse/reason
Client networkapp.vrex.no443Account administration website
Client networkeu1.com.vrex.vixel.no (18.194.34.130)UDP5055 and UDP5056Audio communication, and visual synchronization with other meeting participants
Client networkapi.vrex.no443Device Authentication
Vrex Issues
Client networkhttps://speech.googleapis.com/443Speech to text
Client networkhttps://cognito-idp.eu-central-1.amazonaws.com/443API - User handling / auth
Client network2uhv8tme94.execute-api.eu-central-1.amazonaws.com443API - Vrex content
Client network5n4hoaxzr1.execute-api.eu-central-1.amazonaws.com443API - User preference
Client network8uslevf82e.execute-api.eu-central-1.amazonaws.com443API - Web sockets (notifications / status changes)
Client networkszpdew7g70.execute-api.eu-central-1.amazonaws.com443API - Analytics
Client networkqcymfi5l22.execute-api.eu-central-1.amazonaws.com443API - Integrations (Issues/models)
Client networkuvn1nqbtvh.execute-api.eu-central-1.amazonaws.com443API - Google Speech to Text
Client networkvrex-projects-production.s3.eu-central-1.amazonaws.com4433D data buffer during sessions
Client networkvrex-projects-release.s3.eu-central-1.amazonaws.com443Application version check, and download of updates.

Typical security mechanisms that may prevent the communication:

  • Firewall
  • VPN
  • Proxy

No manual file-sharing is required. No original CAD-models are distributed to any meeting participants.