loohive/onion-pipe repository overview

⁠ Onion-Pipe Client (by LOOHIVE)

⁠🚀 Overview

Onion-Pipe is an open-source anonymous webhook system maintained by the LOOHIVE Infrastructure Team. It allows you to receive webhooks on your local machine via the Tor network without any open ports or complex firewall configurations. It is the perfect tool for developers testing multi-service webhooks in a zero-trust environment.

By using the Onion-Pipe community relay network, you get a persistent, encrypted gateway that is identity-verified via GitHub.

⁠⚡ Rapid Setup

⁠1. Authorize via CLI (Recommended)

Skip the manual tokens and authorize directly from your terminal:

docker run -it --rm loohive/onion-pipe login

Follow the prompts to log in via GitHub. It will provide the final command to start your tunnel.

⁠2. Manual Setup (Alternative)

First, generate your E2EE keys:

docker run --rm -v ./registration:/registration loohive/onion-pipe init

⁠Option A: Single Command Deployment

docker run -d --name onion-pipe \
  -v ./registration:/registration \
  -v ./onion_id:/var/lib/tor/hidden_service \
  -e API_TOKEN="YOUR_API_TOKEN" \
  -e SERVICES_MAP="/api=http://host.docker.internal:3000,/web=http://host.docker.internal:8080" \
  loohive/onion-pipe

⁠Option B: Docker Compose Deployment (Recommended)

Use the following docker-compose.yml for multiplexed routing:

services:
  onion-pipe:
    image: loohive/onion-pipe:latest
    container_name: loohive-gateway
    environment:
      - API_TOKEN=your_token_here
      - RELAY_URL=https://onion-pipe.loohive.com
      # Map multiple path prefixes to different backend services
      - SERVICES_MAP=/api=http://app:3000,/web=http://ui:80
    volumes:
      - ./registration:/registration
      - ./onion_id:/var/lib/tor/hidden_service
    extra_hosts:
      - "host.docker.internal:host-gateway"
    restart: always

Note: SERVICES_MAP allows one .onion address to serve multiple backends. For example, a request to /h/token/api/login will be automatically routed to your app container on port 3000 at the path /api/login.

⁠💎 Features & Advantages

⁠🎯 How It Works: The Pipeline

1. The Relay (The Cloud): Someone sends a request to your relay URL (e.g., https://relay.com/h/your-token/api/test). The relay encrypts it instantly.
2. The Bridge (The Transit): The encrypted blob is "blindly" passed through a bridge node to the Tor network.
3. The Client (Your Machine): This container identifies the path (/api/test), decrypts it using your local private key, and forwards it synchronously to the mapped destination (http://api:3000/api/test).

⁠🛠️ Management & Maintenance

⁠Manually Trigger Registration

If you change your environment or need to refresh your relay mapping:

docker exec onion-pipe register

⁠Rotating Encryption Keys

To rotate your E2EE identity (recommended every 90 days):

1. Run init again:

docker run --rm -v ./registration:/registration loohive/onion-pipe init

1. Restart the container.
2. Trigger registration:

docker exec onion-pipe register

⁠⚙️ Performance & Persistence

• Address Persistence: Mount the /var/lib/tor/hidden_service volume to keep your .onion address forever.
• Circuit Security: All data is encrypted with YOUR local public key before reaching the relay.
• Identity: Manage all your hooks via your private GitHub-linked dashboard.

⁠🤝 Project Links

• Repo: github.com/loohive/onion-pipe⁠
• Relay Service: onion-pipe.loohive.com⁠
• Support: [email protected]⁠

⁠⚖️ Legal Disclaimer

This is open-source software provided by LOOHIVE. Tor is a trademark of The Tor Project, Inc. All trademarks belong to their respective owners.