Components

pTunnl is designed to be run as part of a distributed architecture. The different components have clear interfaces, and each fulfills its distinct responsibilities and tasks.

Proxy Server

The proxy server loads your assigned IPs and their credentials into its internal state. The component receives requests with any of the supported network protocols and routes them to their designated upstream.

The currently supported protocols to be proxied are:

• SOCKS4

• SOCKS5

• UDP

• HTTP

• HTTPS

Should the authentication of the incoming request be successful, the proxy system will then bind the outgoing IP address with the IP that the downstream client used to reach the system.

Resource Management REST API

Our Resource Management component acts as the control plane for everything that lives behind your pTunnl deployment. Think of it as your inventory and fulfillment service. Here you may register your proxy nodes and manage your subnets.

Once a node is in the registry, our service-discovery layer recognises it as soon as it comes online, validates its identity, and allows it to pull its unique configuration and load the assigned proxies it is responsible for into its internal state.

Beyond node registration, the component is where you shape the inventory itself:

• Subnet onboarding – Create subnets by CIDR and add an optional description. The API atom-splits each subnet into individual IP objects, ready to be assigned either randomly or by explicit address.

• Product assembly – Bundle any set of IPs into a product. You can let the platform choose addresses automatically or specify the exact ones you want in the pack, and control how long the product shall be valid for.

• Tag-driven organisation – Key resources accept arbitrary tags or descriptors: For instance, you may tag a subnet to specify it's usage is primarily for tickets, or perhaps to be used for cryptocurrency.

Because these controls live in a single REST surface, you can wire them into CI/CD, Terraform, or a customer portal just as easily as you script them from the command line. In short, the API turns low-level network primitives into neatly packaged, instantly discoverable proxy products your teams (and customers) can consume on demand.