Connect your application
Choose where your application runs. We’ll show the right place to configure its outgoing connections.
Preview: this guide does not activate a subscription, create credentials or change your hosting configuration. Public endpoint provisioning and hosted customer setup are still in progress.
1. Choose your environment
2. Configure your application
3. Verify before routing more traffic
- Start with one non-sensitive test request or a disposable database.
- Confirm the destination response and its TLS certificate.
- Check your account’s activity for the expected project, destination and worker.
- Test an unavailable proxy: your app should report the error, not silently bypass the proxy.
Only traffic explicitly sent through Latch Proxy is covered. A proxy setting alone does not automatically capture every request made by your application.
Common setup problems
My website has no backend
Use a backend or server-side function that supports the required proxy transport. Do not place your project key in HTML, browser JavaScript, public build variables or a mobile app bundle.
My cloud provider accepts environment variables, but traffic is unchanged
Your HTTP client must explicitly support an HTTPS CONNECT proxy. Environment-variable names are application settings, not universal routing switches. Confirm your runtime supports outgoing TCP/TLS and the client’s proxy configuration.
My database URL does not accept an HTTPS proxy
A database driver needs a compatible CONNECT transport or a private forwarding connector. Do not replace the database hostname with an HTTPS URL. Database-driver integration is not ready for this pilot.
What will appear in activity?
Your account’s tunnel destinations, worker assignments and finalized byte totals. Encrypted query text, passwords and HTTP paths are not shown. Traffic outside this proxy is not monitored.