tuds.ai Connectivity
Several Robonauts components need outbound HTTPS access to tuds.ai for licensing, updates, or knowledge-base access. Confirm this path with IT before install day.
Applies to
- TUDS — required for Mission Control in end-user browsers; Azure Bridge runs in TUDS-hosted Azure
- TERA — required for license activation / validation
- TEDI — required for license activation / validation
- TAD — optional for client portal / updater paths; not the SQL data path
What to confirm
- The host or browser can reach https://tuds.ai (and related API endpoints used by your product) over outbound HTTPS.
- Corporate proxies or TLS inspection do not block the product or Mission Control.
- For TUDS, end users need outbound HTTPS to tuds.ai — Azure Bridge itself is hosted by TUDS in Azure.
What this is not
- This is not the path to Vista SQL Server. SQL traffic stays on your customer network (or Trimble cloud SQL path) via TUDS-hosted Azure Bridge.
- TEDI and TERA do not require a daily TUDS login to run, but license validation still contacts tuds.ai.