Lab testing
Proxy
QUIC relay proxy for managed desktop egress
Enterprise proxy split into a local desktop agent and a secure QUIC relay for HTTP, HTTPS CONNECT, and SOCKS5 egress.
What ships on day one
- Local HTTP and SOCKS5 listeners for OS and browser proxy settings
- Bearer-token authenticated QUIC session to the relay
- Relay-side hostname resolution and outbound TCP forwarding
- Certificate-pinned relay trust without TLS interception
Deployment choices
Deploy the relay as a Linux OCI image and run the desktop client on managed devices with a JSON config.
- Self Hosted
Engineering blueprint
Practical control without extra complexity.
Local agent
- Expose one HTTP proxy port and one SOCKS5 proxy port
- Use standard OS or browser proxy settings
- Forward each local flow over an authenticated QUIC stream
Relay session
- Authenticate clients with a configured bearer token
- Pin relay trust to the certificate configured on the client
- Keep HTTPS as CONNECT tunneling without TLS interception
Remote egress
- Resolve hostnames at the relay
- Block configured wildcard hostname patterns before DNS
- Open outbound TCP connections from the relay network
Flow logs
Tracks local flow setup, relay selection, and outbound targets
Listener visibility
Shows the local HTTP and SOCKS5 addresses the client exposes
Relay status
Reports QUIC authentication and outbound connection failures
Operational readiness
Cutovers that keep sessions flowing.
- Works with standard HTTP CONNECT and SOCKS5-aware applications
- Keeps enterprise egress on relay-side DNS and networking
- Ships relay images plus desktop binaries for Linux, macOS, and Windows
Next step
Want a migration plan for your proxy stack?
Email labs@titaniumguard.in for migration support and deployment planning.