HTTPS stays HTTPS.
HTTPS tunneling carries encrypted traffic to the destination. Always validate destination certificates in your client.
ONE FOUNDATION. FAMILIAR PROTOCOLS.
Connect your way.
Keep your flow.
From a simple web request to an application connection, choose the protocol that fits your tools.
A familiar starting point.
Use HTTP proxying for requests and HTTPS tunneling for encrypted web traffic. A natural fit for browsers, API clients, and data tools.
CONNECTION EXAMPLE
curl --proxy http://USER:PASS@PROXY_HOST:PORT \
https://example.comIllustrative syntax. Replace placeholders with your launch credentials.
A LITTLE CONNECTION CLARITY
Choose the right path.
DNS is a client choice.
SOCKS5 clients can support proxy-side name resolution. Check your application’s settings and connection syntax.
Compatibility comes first.
UDP and newer transports depend on the capabilities of both your client and the proxy. Launch docs will provide supported configurations.
GROW FROM HERE
Your next connection
starts with Pine.
We’re putting down roots. Explore what’s coming.