NodeMesh
nodemesh.app · Egress and tunnels · 1 record · JSON
NodeMesh Egress and tunnels
caveatemailno cardD
| Free tier | One host - your own PC - is free with no time limit, for as many game servers as your hardware can run: the web panel and console, the config editor, the mod manager, auto-restart on crash and the traffic relay. unit mixed; metered on none |
|---|---|
| Price | USD 0 for the first node |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No byte allowance is published anywhere read: 'Your first BYOH node is completely free - no time limits, no credit card, all features included.'; ingress: tcp+udp free_allowance: none published |
| Identity | email A signup with a verified email: 'Create a free account', and crash alerts go to 'your verified email'. |
| Limits |
|
| Binding | none Nothing published caps 1 TiB/month, so the volume test can be neither failed nor passed from documents. The named constraint is the one the vendor states instead of a quota: the relay is 'Not DDoS protection', and in relay mode 'The game sees every player as one local address, so IP bans don't work.' |
| Interface | unknown An agent binary plus a web panel; the pages read describe no public API and no tunnel-only command. |
| Tooling | nodemesh agent (sudo install script on Linux), web panel, console; no standalone tunnel CLI is documented |
| Composes with | The agent is the only thing that must run, so it fits a free Linux VM; the game server itself is installed by the platform. |
| Reliability | Relay mode collapses every player to one local address, so per-player IP bans stop working; the vendor says the relay is not DDoS protection; a node that goes offline pauses its servers and disconnects players. |
| Notes | Beta, stated on the page: 'you can create this server today, but we have not run it on our own hardware yet'. The free unit is one host, so a second machine needs credits. The relay is documented for game servers; the site does not offer a generic arbitrary-UDP port, so whether a non-game UDP listener works behind it is unstated. |
| Evidence rung | documented Running the agent and pushing a counted volume through the proxy would show whether an unpublished cap or throttle exists, and a probe record would make this measured. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (6)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | nodemesh.app/games/minecraft-bedrock | 'Bedrock uses UDP on port 19132 (IPv4) and 19133 (IPv6). The relay forwards them to your PC, so you make no changes to your router.' |
| 2026-10-23 | nodemesh.app/docs | 'TCP and UDP both supported' under Traffic Proxy, and 'Included free with your first BYOH node' |
| 2026-10-23 | nodemesh.app/docs | In relay mode: 'The game sees every player as one local address, so IP bans don't work.' and 'Not DDoS protection.' |
| 2026-10-23 | nodemesh.app/pricing | 'Your first BYOH node is completely free - no time limits, no credit card, all features included.' and 'This is free forever - not just during beta.' |
| 2026-10-23 | nodemesh.app/pricing | Extra nodes 'cost 5 NMC/month each', so the free unit is one node rather than a byte count |
| 2026-10-23 | nodemesh.app/docs | The agent install is 'curl -sSL https://install.nodemesh.app | sudo sh', and the origin must be Linux: 'It needs a Linux host' |
More fields (7)
{
"wg_path": "inside-udp",
"wg_detail": "No WireGuard mode of its own; the relay is documented as carrying UDP, so a WireGuard datagram to the proxy address is the same path. Untested.",
"ingress": "tcp+udp",
"volume_tib_month": null,
"volume_stated": "No byte allowance is published anywhere read: 'Your first BYOH node is completely free - no time limits, no credit card, all features included.'",
"bytes_transit": "yes",
"transit_note": "NodeMesh's edge proxy carries the player traffic; the origin only makes an outbound connection."
}Unknown or withheld values (3)
$.interfaceinterface-unknown$.per_object_cap.statednot-applicable$.retention.statednot-applicable