Proxy connection
IPv4:Port ingress for IP Proxy and Proxy Stealth, using the protocols supported by each solution.
- HTTP
- SOCKS5
- SOCKS5H
- SOCKS5 UDP
VLSM.io DELIVERY METHODS
IP Proxy, subnets, Proxy Stealth, and CaptchaBroker: connect each solution to your application with the integration that fits your project.

IPv4:Port ingress for IP Proxy and Proxy Stealth, using the protocols supported by each solution.
Send CAPTCHA resolution tasks to CaptchaBroker and receive the result to continue your workflow.
Integrate subnets into your infrastructure through tunnels, according to the agreed architecture.
Physical connectivity through cross-connect or hosting on a VM and bare metal server.
Each solution has its own delivery options. Protocols, UDP support, and infrastructure resources depend on the selected solution and contracted delivery.
ALL SOLUTIONS
Identify the solution, the integration method, and what your application receives.
The application connects to the same public IPv4 and ingress port. The destination receives IPv4 traffic only.
The application connects to the same public IPv4 and ingress port. The destination receives IPv6 traffic only.
Delivery is defined around your infrastructure: IP Proxy, VXLAN, GRE, cross-connect, VM, or bare metal. The service uses IPv4-only Internet egress.
Tunnels carry the network; VMs and bare metal are hosting options. The architecture combines the resources your project requires.
Explore the solutionDelivery is defined around your infrastructure: IP Proxy, VXLAN, GRE, cross-connect, VM, or bare metal. The service uses IPv6-only Internet egress.
Tunnels carry the network; VMs and bare metal are hosting options. The architecture combines the resources your project requires.
Explore the solutionIntegrate your application through HTTP or SOCKS5. Choose the egress family for your destination and operational requirements: IPv4 only or IPv6 only in each service.
Ingress remains on IPv4. The egress family is selected when contracting the service; delivery is not dual stack.
Integrate VLSM.io’s CAPTCHA resolution service into your application workflow through an API. Our proprietary technology automates resolution, with billing based on delivery of a valid token.
The deliverable is the resolution result. Capacity planning considers tasks, concurrency, and response time for the CAPTCHA type and project.
Host your operation on a VM or bare metal and define the connectivity it needs. Proxy solutions and the CaptchaBroker API are integrated to fit the project.
Keep your application in your environment. Use the proxy connection, applicable tunnels, or the CaptchaBroker API, depending on the selected solution.
Internet egress is IPv4 only.
Internet egress is IPv6 only.
For connectivity, capacity ranges from 1 Mbps to multiple 100 Gbps depending on the project. For CaptchaBroker, planning considers task volume, concurrency, and response time.
Explore network scalability