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:cc81d07d9c71d8945e4252ac9ed39543bca817c3145abf367763ec696ea302ae
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Connectors definition Report an error

“Connectors are Twingate components that are deployed behind your firewall to provide access to private Resources.”
Connectors run as Report an error

“Connectors run either as a container or a Linux systemd service.”
Connector deployment environments Report an error

“Docker K8s (via Helm Chart) Azure (via ContainerInstance) Linux (generic systemd deployment script) AWS ECS Fargate AWS AMI Connectors on Docker for Microsoft Windows”
Connector windows docker warning Report an error

“We recommend against deploying Connectors via Docker on Microsoft Windows due to a known issue with Docker (see here for some details). The recommended way to deploy Connectors on Microsoft Windows is inside of a Linux VM using Hyper-V.”
Connector names Report an error

“Connector names are randomly generated on creation. This name may be edited at any time. If you decide to edit a Connector name, note that the name must be unique across all Connectors in your account.”
Connector status emails Report an error

“Admins will receive an email when a Connector goes offline and again when it comes back online. To stop these notifications, turn off status emails for specific Connectors.”