andydunstall/piko

Health v2 · maintenance only

Adoption not part of the score

2185 stars · 87 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Piko is an open-source reverse proxy for tunneling traffic to services that are not publicly routable, serving as a self-hosted alternative to Ngrok. Upstream services open outbound-only connections to a Piko cluster, which forwards incoming HTTP(S) and TCP traffic over those tunnels with load balancing and fault tolerance.

Use cases

• expose a local development server to the internet
• self-host an ngrok alternative on Kubernetes
• connect to services inside a customer network without inbound ports
• build a bring-your-own-cloud (BYOC) service that reaches customer deployments
• tunnel TCP traffic to devices behind NAT
• load balance traffic across multiple upstream listeners on the same endpoint

When to choose

• you need production-grade tunneling with clustering, horizontal scaling, and zero-downtime deployments
• you want to self-host tunnels on Kubernetes behind an HTTP(S) load balancer
• your upstream services have no public route but can make outbound connections
• you need both HTTP and TCP tunneling with a Go SDK or CLI agent

When to avoid

• you only need a quick temporary tunnel for local testing and prefer a hosted service with zero setup
• you need features like built-in authentication portals, request inspection UI, or paid-tier capabilities offered by Ngrok
• you want a simple single-node reverse proxy with static routing rules rather than outbound tunnel connections

Facets

service · maturity active

proxy networking http-server routing self-hosted networking backend self-hosted infrastructure-as-code windows go cli self-hosted tunneling reverse-proxy ngrok-alternative tcp-proxy http-proxy kubernetes devops linux macos docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="andydunstall/piko")