mudcat
mudcat.io · Egress and tunnels · 1 record · JSON
mudcat Egress and tunnels
fails: quotaanonymousno cardDretention-clamped
| Free tier | Yes. You can use it for free. However, in the case of free users, there are restrictions on usage time, transmission speed, and amount of transmission data. unit unlimited; metered on unstated |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | The vendor states restrictions on usage time, transmission speed, and amount of transmission data, with no numbers published. The support forum answers the same question with: At this moment, no restriction because it is under alpha status.; ingress: tcp+udp free_allowance: none published |
| Identity | anonymous The client assigns a Device UUID and needs no account, email or card on the page read; the download page lists only operating-system binaries. |
| Limits | |
| Binding | retention-clamped Two constraints sit on the free tier: the assigned hostname expires after 8 hours, and the operator states a cap on data volume whose figure is unpublished. The 8-hour lease is the one with a number, so it is the binding kind, and either one defeats a 1 TiB month. |
| Interface | cli ./mudcat udp --local-port 25565 --remote-port 25566. |
| Tooling | Single binary from mudcat.io/download, subcommands tcp, http and udp. |
| Composes with | Carries a WireGuard handshake to a free VM, or exposes a game server directly; the 8-hour hostname means it needs a supervisor that re-registers and re-points DNS. |
| Reliability | Alpha software at version 0.0.3; hostnames expire every 8 hours; the vendor reserves the right to cap time, speed and data without publishing numbers. |
| Notes | The alpha status is the important fact: the free tier works today with no stated cap, and the caps are promised but unwritten. Version 0.0.3 and a 2024 forum thread mean this is not a 2026 launch, only a 2026-live one. The conservative verdict is kept: the 8-hour lease and an unpublished byte cap both defeat the test, and neither can be designed against. |
| Evidence rung | documented The free-tier byte and speed limits are unpublished; one measured transfer and a reconnect after 8 hours would move this from documented to measured. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | www.mudcat.io/ | HTTP, TCP and UDP port sharing; UDP example with an 8-hour Access Domain TTL; free use with unpublished restrictions on time, speed and data. |
| 2026-10-23 | forums.mudfish.net/t/what-are-the-restrictions-on-mudcat-fre | Vendor staff answer of 2024-08-13 that there is no restriction while the service is in alpha, which means the published restriction has no number behind it. |
| 2026-10-23 | www.mudcat.io/download | Client version 0.0.3 for Windows, macOS and Linux, which supports the alpha reading. |
| 2026-10-23 | mudcat.io/ | 'Yes, it can be used free of charge. However, in the case of free users there are restrictions on usage time, transmission speed, amount of transmitted data and so on'; no figure is published |
More fields (7)
{
"wg_path": "inside-udp",
"wg_detail": "The vendor documents a UDP forwarding mode: Forwarding: UDP 583-841-3346.mudcat.io:25566 -> 127.0.0.1:25565. A WireGuard handshake is an opaque UDP datagram and passes through that path.",
"ingress": "tcp+udp",
"volume_tib_month": null,
"volume_stated": "The vendor states restrictions on usage time, transmission speed, and amount of transmission data, with no numbers published. The support forum answers the same question with: At this moment, no restriction because it is under alpha status.",
"bytes_transit": "yes",
"transit_note": "A Mudfish-operated remote access node forwards the datagrams."
}Unknown or withheld values (3)
$.notespartly-held$.per_object_cap.statednot-applicable$.retention.statednot-applicable