darkflare vs pgrok
TCP tunneling projects compared
darkflare carries TCP connections through HTTP(S) requests routed via a CDN, while pgrok exposes local services through SSH remote port forwarding. darkflare focuses on reaching TCP destinations across restrictive networks; pgrok focuses on shared development tunnels with stable subdomains and OIDC sign-in.
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.
pgrok: Share Local Services Through SSH Tunnels
pgrok is a self-hosted reverse-tunnel service for small teams that need to expose local development services through stable subdomains. It uses SSH port forwarding and OIDC sign-in, with support for HTTP and raw TCP traffic.
| darkflare | pgrok | |
|---|---|---|
| Language | Go | Go |
| License | — | MIT |
| Stars | 1.6k | 3.6k |
| Forks | 90 | 132 |
| Last analyzed | Oct 3, 2026 | Oct 3, 2026 |
Key differences
- darkflare tunnels TCP over HTTP(S) through a CDN; pgrok uses SSH port forwarding for HTTP and raw TCP traffic.
- darkflare is designed for authorized access to TCP services across restrictive networks; pgrok targets small teams sharing local development services.
- darkflare offers local-port and stdin/stdout client modes; pgrok provides stable user subdomains and can route selected HTTP paths to alternate local services.
- pgrok requires a public server, domain, DNS, OIDC integration, and PostgreSQL; darkflare requires a reachable server and suitable CDN hostname and origin configuration.
- Both are written in Go and are not archived. pgrok is MIT-licensed; darkflare's license is not described in the supplied project information.
- pgrok has 3.6k stars and 132 forks, compared with darkflare's 1.6k stars and 90 forks. pgrok cautions against production use where availability is required.
Choose darkflare if you…
- need to reach TCP services across a network that permits HTTPS but restricts other connections.
- want local-port forwarding or stdin/stdout integration with SSH ProxyCommand.
- need optional outbound SOCKS5, HTTP, or HTTPS proxy support for the client.
Choose pgrok if you…
- want a small team to share local development services through stable subdomains.
- need OIDC sign-in and HTTP path routing to alternate local services.
- can operate the required server infrastructure, including its domain, DNS, OIDC integration, and PostgreSQL database.
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.