Source

Access model & connectivity — found from sitemap — Twingate

Checked for Twingate on 5 Nov 2026

Technical details

type: page
http status: 200
content hash: sha256:a6968d0392233eee574d6b3471e740fda31468d9548e5e158db24d976ebff349
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Remote network definition Report an error

“The “Remote Network” concept in Twingate is a logical container that groups Resources together.”
Connector required Report an error

“At least one Connector must be deployed to allow access to Resources configured in a Remote Network.”
Connector deployment location Report an error

“Connectors are deployed behind the firewall and provide access to a Remote Network’s Resources for authenticated, authorized users.”
Recommended connector count Report an error

“We recommend that you deploy at least two Connectors in every Remote Network that you configure in Twingate.”
Connector max count Report an error

“You can deploy as many Connectors within a Remote Network as required for your needs.”
Connector load balancing Report an error

“Load balancing is performed automatically as the number of Connectors deployed within a Remote Network is changed.”
Connector capacity Report an error

“A single Connector is generally capable of handling traffic for hundreds of users, depending on your usage patterns.”
Remote network mapping Report an error

“each Remote Network will approximately correspond to an existing physical network or VPC you’d like to provide remote access to.”