LATCH PROXY · PRIVATE PILOT

Control your application's outbound connections.

Authenticated HTTPS tunnels, IPv6 with IPv4 fallback, and an activity view scoped to your own service.

Setup in progress. Public proxy endpoints and subscription checkout are not available yet. Wrooms is the first planned integration; production traffic has not been migrated.

One service. Clear controls.

Your activity only

See your project, worker, destination hostname and metered bytes. Other customers cannot view your connection history.

Stable or rotating

Use a 15-minute session for stable worker assignment, or rotate between healthy workers on new connections. An active tunnel keeps its route.

Encrypted end to end

No root certificate installation. Destination HTTPS remains encrypted. Private and metadata destinations are blocked.

Connect from your backend

Open setup guide
  1. Sign in to your Latch Proxy account once the pilot opens.
  2. Create an application key and store it in your server's secret manager.
  3. Configure the HTTPS proxy endpoint and approved destination domains.
  4. Verify your first tunnel and review its activity.

Keys belong on your backend, never in browser JavaScript. Activity records describe tunnels, not decrypted HTTP requests or unrelated activity on your computer.