Netmaker

Free allowance: Community: 'Free', '1 Netmaker Server', '3 users', '10 nodes', '10 external clients', '2 Networks'.
Verdict: self-hosted, last resortverdict fails-egress: data cannot be read back out at a usable rate or price. Self-hosted options are listed last, because this site is for users who have no hardware.
Cost: free tier
Identity: emailno card, no phone
Binding limit: request-rateThe 3-user and 10-node caps are the published meters and the vocabulary has no token for a count; request-rate is the nearest. No byte meter exists and nothing listens publicly.
Evidence: documented3 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23

Free tier	Community: 'Free', '1 Netmaker Server', '3 users', '10 nodes', '10 external clients', '2 Networks'. unit users; metered on identity-count
Price	USD 0
Limits	request-rate (binding) The 3-user and 10-node caps are the published meters and the vocabulary has no token for a count; request-rate is the nearest. No byte meter exists and nothing listens publicly. source
Identity	email a Netmaker account for the hosted console
Egress	No byte allowance in any plan; the plans count users, nodes, clients and networks.; ingress: none free allowance: none published
Interface	cli netclient join, plus the console
Tooling	netclient, netmaker server, Kubernetes operator
Composes with	the mesh half of a two-part chain; it needs Caddy, Traefik or Pangolin on a public host to finish the job
Reliability	the public-facing half of any deployment is a reverse proxy the operator runs, not a Netmaker feature
Notes	The vendor's word 'ingress' is a false friend here: its Ingress Proxy Service forwards to devices on the Netmaker network, and the public recipe requires a reverse proxy the reader deploys. That distinction is the whole reason exists.
Parsed numbers	has-free-tier 1 price USD 0

Evidence 3

date	source	what it proved
2026-10-23	www.netmaker.io/pricing	Community is Free with 1 server, 3 users, 10 nodes, 10 external clients and 2 networks
2026-10-23	learn.netmaker.io/how-to-guides/how-to-use-netmaker-with-a-r	publishing publicly needs a third component: 'deploy a reverse proxy server in the cloud', 'deploy a Netmaker node on that server', and then 'your service will now be accessible to the internet', read through the search index
2026-10-23	docs.netmaker.io/docs/features/k8s-operator	Netmaker's own 'Cluster Ingress' is internal: 'Expose Kubernetes services to devices on your Netmaker network'

More fields 6

wg path	unknown
wg detail	The free plan counts '10 external clients', which is the slot where WireGuard configs are handed out, but no page read states that a .conf is issued, so the export path stays unproven.
ingress	none
volume stated	No byte allowance in any plan; the plans count users, nodes, clients and networks.
bytes transit	unknown
transit note	WireGuard peer to peer where possible, with Relay fallback for nodes that cannot connect directly

Unknown values 2