Remote networks

Remote networks are the logical containers that group Resources together. As implied by the name, a Remote network should correspond to a network you are providing remote access to.

At least one Connector must be configured as part of a Remote network. Connectors are the Twingate components that provide access into a remote network, and without a Connector deployed and running, Resources are inaccessible.

We recommend running at least two Connectors in every Remote network that you configure in Twingate. There are two primary reasons to do this:

  • Redundancy and failover. If any one Connector fails, additional Connectors will be available for redundancy.
  • Scalability. As your needs grow, it may be necessary to add additional Connectors to forward additional traffic.

You can deploy as many Connectors within a Remote network as required for your needs.

Note: Because Connectors within the same Remote network are interchangeable, it’s important that they all have the same network routing and access rules on the Remote network.

Updated 8 months ago

What's Next

Best Practices

Remote networks

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.