Architecture

Control API, edge gateway ports, and Solana settlement — how a request flows through ProxyHubb.

ProxyHubb splits into three planes: control, data, and settlement.

Ports and hosts

Remember: buyers use 8090; providers use 3128. Mixing them is the most common ops mistake.

Request flow (buyer)

Buyer app / SDK
    │  JWT or API key → create intent / order credentials / pool endpoints
    ▼
Control API  (api.proxyhubb.com)
    │  returns token or username/password
    ▼
Edge gateway :8090  (HTTP CONNECT or SOCKS5)
    │  tunneled bytes ↔ upstream / provider path
    ▼
Edge meters usage → signed reports → Control API ledger → settlement batches

Planes

Control API

Go service behind api.proxyhubb.com. Owns:

• Wallet auth and /v1/auth/*
• Marketplace listings, orders, escrow confirmations
• Access Passes / entitlements
• Bulk pools and API keys
• Usage ledger reads and settlement orchestration

Edge gateway

Rust data plane. Owns:

• Buyer listeners on :8090 (CONNECT + SOCKS5 only — no absolute-URI forward proxy)
• Provider tunnel on :3128
• Session binding and byte metering
• Signed usage reports to control (X-Gateway-Auth)

Settlement

Solana program + custody paths for marketplace escrow and batch settlement. Buyers interact mainly via pay/solana + wallet confirm; providers earn from metered, accepted usage.

Where to read next