Netmaker

netmaker.io · Egress and tunnels · 1 record · JSON

Netmaker Egress and tunnels

fails: egressemailno cardDrequest-rate

www.netmaker.io/pricing · WireGuard management (private only) · egress/netmaker · JSON · compare

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
Per-object cap	not applicable
Retention	not applicable
Egress	No byte allowance in any plan; the plans count users, nodes, clients and networks.; ingress: none free_allowance: none published
Identity	email a Netmaker account for the hosted console
Limits	request-rate 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
Binding	request-rate 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.
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.
Evidence rung	documented Reading the external-client documentation would settle wg_path.
Checked	2026-10-23 (live); stale on 2026-11-22
Parsed numbers	`$.price_per_tb_month` price-per-tb USD0.0 TB / month

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 (7)

{
 "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 today states that a .conf is issued, so the export path stays unproven.",
 "ingress": "none",
 "volume_tib_month": null,
 "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 or withheld values (2)

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