Twingate Overview

Cloud-managed Zero Trust Network Access with resource-level policy, identity integration, and outbound Connector deployment.

Twingate is a cloud-managed Zero Trust Network Access platform that controls access to defined private Resources rather than exposing an entire private network to an authenticated user. Its architecture uses Controllers, Clients, Connectors, and global Relays. Connectors are deployed inside private networks and initiate outbound connections; Twingate attempts direct Client-to-Connector connectivity where network conditions permit and uses Relays as a fallback transport path.

Twingate Plans

Starter (free, up to 5 users), Home ($15/month, up to 7 users, non-commercial use), Teams ($5/user/month), Business ($10/user/month), and Enterprise (custom). Paid self-service plans offer trial options.

View Twingate Pricing →
No affiliate relationship — direct link only.
ArchitectureZTNA / Split Tunnel
ProtocolTLS 1.3 / QUIC
DeploymentCloud-Managed
Access ModelLeast Privilege

What is Twingate?

Twingate is a Zero Trust Network Access platform organized around Resources, Remote Networks, users, groups, and access policies. Instead of assigning broad network access after authentication, administrators define which identities and devices can reach individual private addresses, applications, services, or network ranges.

Connectors run inside protected networks and require outbound connectivity rather than public inbound firewall exposure. For data transport, Twingate attempts direct Client-to-Connector connections using NAT traversal and QUIC where possible. Its global Relay infrastructure provides a fallback path when direct connectivity cannot be established, while Client-to-Connector traffic remains protected by certificate-pinned TLS.

Operational Fit

  • Teams moving remote access from network-level VPN connectivity toward resource-level policy
  • Engineering and operations teams controlling access to cloud and on-premises private Resources
  • Organizations incorporating device posture and endpoint trust into access policies
  • IT teams integrating private-resource access with supported identity providers
  • Distributed organizations applying centralized access policy across multiple Remote Networks
  • Teams managing Twingate configuration through Terraform, Pulumi, or administrative APIs

Documented Strengths

  • Connectors initiate outbound connectivity and do not require public inbound firewall ports
  • Twingate attempts direct Client-to-Connector connections using NAT traversal and QUIC, with Relays as fallback
  • Resource-based traffic interception supports split-tunnel access to defined private Resources
  • Terraform and Pulumi providers support infrastructure-as-code administration
  • Native device posture checks are available on Teams and higher plans, with additional endpoint integrations on Business
  • Connector software can be deployed on supported Linux systems or as OCI containers without a dedicated hardware appliance

Considerations

  • The standard Twingate service uses a Twingate-operated cloud control plane; Connectors remain customer-deployed
  • Advanced identity provisioning, endpoint integrations, and administrative capabilities vary by plan
  • Starter is limited to 5 users and 50 Resources; Teams supports up to 100 users and Business up to 500
  • Support levels and additional support options vary by plan and account size

Base Layer Evaluation Notes

Access Model

Resource-level Zero Trust Network Access. Administrators define private Resources and assign access through users, groups, and policies. Client traffic for authorized Resources is intercepted locally, while unrelated traffic can continue outside the Twingate path.

Network Architecture

Cloud control plane with customer-deployed Connectors and direct-or-relayed transport. Connectors initiate outbound connectivity. Twingate attempts peer-to-peer Client-to-Connector paths using NAT traversal and QUIC; global Relays provide fallback transport when a direct path is unavailable.

Identity & Policy

Identity, group, device, and contextual controls feed resource policies. Identity-provider availability varies by plan. Native device posture checks are available from Teams, while Business expands identity provisioning, endpoint integrations, and policy capabilities.

Platform & Deployment

Endpoint Clients plus Linux- or container-based Connectors. Twingate supports major desktop and mobile platforms. A Connector can provide access to multiple reachable Resources within a Remote Network, and additional Connectors can add capacity, load balancing, and failover.

Core Capabilities

Connector Architecture

Lightweight software components deployed inside your private networks. Connectors make outbound-only connections — no inbound firewall ports required. Multiple Connectors per network provide automatic load balancing and failover.

Understanding Connectors →

Device Posture Checks

Native posture checks can evaluate device properties such as OS version, disk encryption, screen lock, firewall, antivirus, and biometric configuration, with availability varying by client platform. Trusted Device Profiles can also use supported MDM and EDR integrations. Native posture checks are available from the Teams plan; additional endpoint integrations are available on higher tiers.

Device posture docs →

SSO & IdP Integration

Google Workspace SSO is available on Teams, while Business and Enterprise add broader identity-provider support including Okta, Microsoft Entra ID, OneLogin, JumpCloud, and Keycloak. Automatic user provisioning and directory synchronization are available through supported identity-provider integrations on applicable plans.

IdP integrations →

Terraform & Pulumi

Native infrastructure-as-code providers for Terraform and Pulumi allow teams to programmatically deploy and manage their Twingate network alongside other infrastructure. Service accounts support unattended CI/CD pipeline access.

Terraform provider →

Compare Remote Access Platforms

Compare Twingate with other remote access platforms using the same criteria across access model, network architecture, identity and policy controls, platform coverage, and deployment requirements.

View Remote Access Platforms Comparison →
Evaluation note: Base Layer separates documented provider facts from operational interpretation. Twingate plan limits, identity integrations, posture capabilities, and platform features can change; official Twingate resources are linked above for verification.

Commercial relationship: Base Layer has no affiliate relationship with Twingate. Links on this page point directly to official Twingate resources.

Review date: October 2026.