Twingate

twingate.com · Egress and tunnels · 1 record · JSON

Twingate Egress and tunnels

fails: egressemailno cardDrequest-rate

www.twingate.com/pricing · zero trust access (private only) · egress/twingate · JSON · compare

Free tier	Starter: 'Free per user / month', 'Up to 5 users'. unit users; metered on identity-count
Price	USD 0
Per-object cap	not applicable
Retention	not applicable
Egress	No byte allowance is published; the plan is priced per user.; ingress: none free_allowance: none published
Identity	email a Twingate account at auth.twingate.com
Limits	request-rate The only published meter is the 5-user cap, and the vocabulary has no token for an identity count; request-rate is the nearest. It is also moot: with no public ingress there is no 1 TiB/month to spend. source
Binding	request-rate The only published meter is the 5-user cap, and the vocabulary has no token for an identity count; request-rate is the nearest. It is also moot: with no public ingress there is no 1 TiB/month to spend.
Interface	cli the Twingate client on each device and the Connector in the private network
Tooling	Twingate client and Connector
Composes with	carries nothing on its own; it is a private access layer, so it composes with a public ingress rather than replacing one
Reliability	Relays carry traffic only when peer-to-peer fails, and the free plan is bounded by users rather than bytes
Notes	Fails the ingress test by design: every path needs a Twingate client and an ACL issued by the Controller. The Connector does proxy 'TCP and UDP traffic for protected Resources', which is why UDP appears in the product and still carries nothing to a public reader.
Evidence rung	documented A live attempt to reach a Resource without the Twingate client would confirm the private-only claim.
Checked	2026-10-23 (live); stale on 2026-11-22
Parsed numbers	`$.limits[0].value` limit:request-rate 1.0 TiB / month `$.price_per_tb_month` price-per-tb USD0.0 TB / month

Evidence (2)

date	source	what it proved
2026-10-23	www.twingate.com/pricing	Starter is 'Free per user / month' with 'Up to 5 users'
2026-10-23	www.twingate.com/docs/how-twingate-works	'The Connector is intended to be deployed behind the firewall of a private Remote network'; the client-to-connector path is a 'certificate-pinned TLS tunnel'

More fields (7)

{
 "wg_path": "none",
 "wg_detail": "No WireGuard. 'The Client is responsible for establishing an encrypted tunnel with the appropriate Connector to access a protected Resource. This TLS tunnel is established based on the anonymous, unique Connector ID'. No .conf exists.",
 "ingress": "none",
 "volume_tib_month": null,
 "volume_stated": "No byte allowance is published; the plan is priced per user.",
 "bytes_transit": "unknown",
 "transit_note": "peer-to-peer between client and Connector where possible, with a Relay as backup"
}

Unknown or withheld values (2)

$.per_object_cap.stated not-applicable
$.retention.stated not-applicable