Skip to content

Architecture & network

Overview

Like the on-premises edition, the Cloud platform is built on the same two pieces:

  • Drovio Server: hosted and operated by Drovio. Serves the web client, manages users and license allocation, and coordinates app connections.
  • Drovio app: installed on end-user machines, or the web client accessed from a browser.

Screen sharing traffic is peer-to-peer whenever possible. When a direct P2P connection can't be established (restrictive firewalls / NAT), traffic is relayed through managed TURN servers.

Endpoints

The Drovio app connects to the Cloud out of the box. These are the hosts it and the web client reach:

Purpose Endpoint Protocol / port
Application and web client app.drovio.com TCP 443
STUN / TURN relays relay.drovio.com UDP and TCP 443
App updates repository.drovio.com TCP 443

relay.drovio.com resolves to the closest healthy relay: the record is latency-routed across our AWS regions and backed by health checks, so a user in Europe and a user in Asia do not get the same address.

Allow by hostname, not by address

Relays are spread over more than ten AWS regions and their addresses follow the infrastructure. Allow the hostnames above rather than IP addresses. If your firewall can only work with addresses, contact support@drovio.com for the current list.

Network & firewall requirements

For the app and web client to work from within a corporate network, the following must generally be reachable:

Traffic Protocol / port Notes
HTTPS to Drovio Server TCP 443 Web client and sign-in
WebSocket (WSS) TCP 443 Persistent signaling connection
P2P media Outbound UDP and its return traffic Ephemeral ports on both endpoints
STUN / TURN UDP and TCP 443 Media relay when P2P is impossible

Outbound UDP is what makes a session direct. Where a firewall blocks it, nothing breaks: the session falls back to a relay and everything goes through port 443. It does cost latency and it moves the traffic through our infrastructure, so allowing outbound UDP is worth it. The ports involved at each step are detailed in Protocols & ports.

Note

Drovio's P2P architecture means the bulk of the screen sharing bandwidth flows directly between participants; the Cloud servers primarily handle signaling and fallback relaying.