wg-tcp-tunnel (arkq)

Free allowance: No service and no account; source under MIT
Verdict: self-hosted, last resortverdict paid-only: no free allowance; listed for its price. Self-hosted options are listed last, because this site is for users who have no hardware.
Cost: no price statedsee Price below
Identity: anonymousno card, no phone
Binding limit: noneno named constraint binds
Evidence: documented4 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	no service and no account; source under MIT unit none; metered on none
Price	USD 0
Binding	none the constraint is a public-IP server at the far end, outside the vocabulary; the build can also reach the far end through ngrok
Identity	anonymous no account; a public-IP server and a client
Egress	not applicable; the software states no volume; ingress: tcp free allowance: none published
Interface	cli wg-tcp-tunnel --src-tcp/--dst-udp on one end, --src-udp/--dst-tcp on the other
Tooling	cmake plus Boost.Asio; systemd and Termux runit units in tree
Composes with	composes with any TCP forwarder that hands over a raw stream, including an ngrok TCP endpoint, and with a plain public-IP host.
Reliability	source-built only; no release artefacts; the ngrok path inherits ngrok's connection accounting
Notes	The only wrapper that ships a mode for a hosted forwarder by name: with -DENABLE_NGROK=ON the client dials an ngrok TCP endpoint instead of the server's IP. That is the shortest documented path from a free hosted tunnel to a WireGuard datagram, and it costs one ngrok connection from the free monthly allowance. No release object exists, so a deployment builds from source with Boost and CMake.
Evidence note	documented a measured run through the ngrok path would raise it, and would be the first measurement of a hosted tunnel carrying WireGuard
Parsed numbers	has-free-tier 0 price USD 0

Evidence 4

date	source	what it proved
2026-10-23	github.com/arkq/wg-tcp-tunnel	the purpose sentence, both invocations, and the Endpoint rewrite
2026-10-23	github.com/arkq/wg-tcp-tunnel	"-DENABLE_NGROK=ON ... --ngrok-api-key=KEY --ngrok-dst-tcp-endpoint=ENDPOINT"; the tunnel can use an NGROK endpoint as its destination
2026-10-23	github.com/arkq/wg-tcp-tunnel	tags v1.1.2 latest, no GitHub release objects, last commit 2026-08-28; 38 stars
2026-10-23	github.com/arkq/wg-tcp-tunnel	build options -DENABLE_WEBSOCKET and -DENABLE_RUNIT (Termux service)

More fields 9

wg path	none
wg detail	"This project is a simple UDP-over-TCP tunneling. The main purpose of it is to allow WireGuard to work over TCP"; server '--src-tcp=0.0.0.0:51820 --dst-udp=127.0.0.1:51820', client '--src-udp=127.0.0.1:51822 --dst-tcp=<SERVER-IP>:51820' with Endpoint = 127.0.0.1:51822
ingress	tcp
volume stated	not applicable; the software states no volume
bytes transit	yes
transit note	the far end forwards into the local WireGuard listener
hosting requirement	a host on a public address running the server half, or an ngrok TCP endpoint in its place
last release	v1.1.2 tag, no release object, last commit 2026-08-28
stars	38

Unknown values 2