fshy

fshy / Egress and tunnels

Innernet

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

Innernet Egress and tunnels

fails: egressanonymousno cardD

github.com/tonarino/innernet · WireGuard overlay (private only) · egress/innernet · JSON · compare

Free tier'A private network system that uses WireGuard under the hood.' MIT licensed and self-hosted; no quota of any kind.
unit unlimited; metered on none
PriceUSD 0
Per-object capnot applicable
Retentionnot applicable
EgressNo allowance exists: the coordination server is the operator's.; ingress: none
free_allowance: none published
Identityanonymous self-hosted; peers are invited by an admin running 'innernet-server add-peer', so identity is a key handed out locally
Bindingnone Nothing counts bytes. At 1 TiB/month only the host's own link binds, and there is no public listener through which a reader could spend it.
Interfacecli innernet-server and the innernet client
Toolinginnernet and innernet-server
Composes witha private mesh control plane; composes with a public ingress but adds none
Reliability'should be considered experimental software'; the coordination server's uptime is the constraint
NotesSelf-described as similar in goal to nebula and Tailscale. The README's own warning - 'This has not received an independent security audit' - is a technical reliability fact, not a reason to exclude it.
Evidence rungdocumented Reading the client documentation would settle whether innernet writes a standard wg config.
Checked2026-10-23 (live); stale on 2026-11-22
Parsed numbers
  • $.price_per_tb_month price-per-tb USD0.0 TB / month
Evidence (1)
datesourcewhat it proved
2026-10-23github.com/tonarino/innernet'A private network system that uses WireGuard under the hood'; 'Every innernet network needs a coordination server to manage peers and provide endpoint information so peers can directly connect to each other'
More fields (7)
{
 "wg_path": "unknown",
 "wg_detail": "The README states WireGuard under the hood and a coordination server that 'manages peers and provide endpoint information so peers can directly connect', but no page read today documents a .conf export.",
 "ingress": "none",
 "volume_tib_month": null,
 "volume_stated": "No allowance exists: the coordination server is the operator's.",
 "bytes_transit": "overlay-only",
 "transit_note": "peers connect directly; the coordination server hands out endpoints and sees no payload"
}
Unknown or withheld values (2)
  • $.per_object_cap.stated not-applicable
  • $.retention.stated not-applicable