proxy-relay
Lightweight peer-to-peer IP relay. Share your residential IP with another device so its traffic exits from your network. Built in Go — zero dependencies, single binary, works on Termux/Android.
How it works
User A (home, residential IP) Relay (public VPS) User B (CLI tools)
proxy-relay serve proxy-relay relay proxy-relay connect <key>
- User A runs
serve→ generates a 4-word key → shares it - User B runs
connect <key>→ gets a local HTTP proxy on:8080 - All traffic from User B now exits through User A's residential IP
No root, no kernel modules, no inbound ports — just outbound TCP.
Install
# Via pip (recommended)
pip install proxy-relay
# Via Go
go install github.com/Zaidux/proxy-relay@latest
# Prebuilt binary
curl -L https://github.com/Zaidux/proxy-relay/releases/latest/download/proxy-relay-linux-amd64 -o /usr/local/bin/proxy-relay
chmod +x /usr/local/bin/proxy-relay
Usage
1. Start the relay (on a publicly reachable VPS)
proxy-relay relay --port=9000
2. Share your IP (on your home device)
proxy-relay serve --relay=<vps-ip>:9000
# Prints: Key: coral-echo-pine-dawn
3. Use someone's IP (on any machine)
proxy-relay connect coral-echo-pine-dawn --relay=<vps-ip>:9000
# Local HTTP proxy running on :8080
export HTTP_PROXY=http://localhost:8080
Verify
curl --proxy http://localhost:8080 http://ipinfo.io/ip
# Should show User A's IP, not the VPS IP
Riciplay integration
Set the proxy in ~/.config/riciplay/config.json:
{"proxy": "http://localhost:8080"}
All riciplay tools (browse, nuclei, dalfox, sqlmap, etc.) route through the residential IP.
Building from source
git clone https://github.com/Zaidux/proxy-relay.git
cd proxy-relay
go build -o proxy-relay .
Or cross-compile:
make cross # builds linux/darwin/windows for amd64/arm64
License
MIT
Metadata
Release files for riciplay-relay 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| riciplay_relay-0.1.0.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| riciplay_relay-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.4 kB
Release files / riciplay_relay-0.1.0.tar.gz
| Download URL | riciplay_relay-0.1.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75d96a0703ad5249fe44c7830b22b9cd7049b459c0a6f6ed8735c2ccbeaf74d7
|
|
BLAKE2b-256 checksum How to use checksums |
51f6962decd45bf1623e2b6e490af24778e02ba696ec62fdce2e3924e65a5cb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / riciplay_relay-0.1.0-py3-none-any.whl
| Download URL | riciplay_relay-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aacd518bb7802db96d375749e00ef27e2fdd909327baae306a05d2ee868697fd
|
|
BLAKE2b-256 checksum How to use checksums |
4caca50ea6ed8a7c6046bf8b55f5b31b0b755ef2113d44095ff1944f939fe242
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for riciplay-relay 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.