darkflare vs tunn
TCP-over-CDN tunneling and SSH port-forward management compared
darkflare tunnels TCP traffic through HTTP(S) requests routed via a CDN, while tunn organizes SSH port forwards defined in a YAML file. darkflare provides a client-server tunnel for reaching TCP destinations across restrictive networks; tunn runs the system OpenSSH client to manage selected forwards.
darkflare: Tunnel TCP Traffic Through a CDN
DarkFlare is a Go client-server tool that carries TCP connections through HTTP(S) requests routed via a CDN. It is intended for authorized access to TCP services across restrictive networks, with encryption for sensitive traffic supplied separately.
tunn: Manage SSH Tunnels from a YAML Config
tunn launches and monitors SSH port forwards from a single YAML configuration, using your existing OpenSSH setup. It suits developers who need a simple way to run selected tunnels together or manage them in the background.
| darkflare | tunn | |
|---|---|---|
| Language | Go | Go |
| License | — | MIT |
| Stars | 1.6k | 252 |
| Forks | 90 | 11 |
| Last analyzed | Oct 3, 2026 | Oct 3, 2026 |
Key differences
- darkflare carries TCP traffic through a CDN; tunn manages SSH port forwards using OpenSSH.
- darkflare uses client and server components, with a reachable server and CDN configuration; tunn uses a YAML configuration and the system `ssh` executable.
- darkflare supports local-port forwarding and stdin/stdout mode; tunn defines named tunnels with multiple local-to-remote port mappings.
- darkflare documents optional SOCKS5, HTTP, or HTTPS outbound proxies; tunn reuses existing OpenSSH hosts, keys, and settings.
- darkflare lists 1.6k stars and 90 forks; tunn lists 252 stars and 11 forks.
- darkflare cautions that its tunnel obscures traffic but does not provide end-to-end confidentiality; tunn relies on the authentication and host behavior of the user's OpenSSH setup.
Choose darkflare if you…
- need to carry TCP traffic through a CDN across a network that permits HTTPS but restricts other connections.
- want a client-server tunnel with local-port or stdin/stdout forwarding.
- need optional outbound SOCKS5, HTTP, or HTTPS proxy support for the client's connection.
Choose tunn if you…
- want to define and start several named SSH port forwards from one YAML configuration.
- need to run selected forwards concurrently or detach them and check their status or stop them.
- want to use existing OpenSSH configuration, keys, and settings on macOS or Linux.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.