Deploying a reverse proxy to PostHog Cloud

Last updated:

|Edit this page

A reverse proxy allows you to send events to PostHog Cloud using your own domain.

This means that events are less likely to be intercepted by tracking blockers. You'll be able to capture more usage data without having to self-host PostHog.

Setting up a reverse proxy means setting up a service to redirect requests from a subdomain you choose (like to PostHog. It is best practice to use a subdomain that does not include posthog, analytics, tracking, or other similar words.

Note: PostHog Cloud requires that the proxy sets the Host header to the same host it is calling. Check the guides below on how to do that for several proxies.

You then use this subdomain as your api_host in the initialization of PostHog instead of or

Make sure to pass the proper ui_host parameter when initializing our browser integration, so that links to the PostHog interface point to the correct host.

Deploying a reverse proxy

Options for deploying a reverse proxy include:

Reverse proxy requirements

If you want to use an alternative reverse proxy that we have not documented, it must meet the following requirements:

- route:*
- route:*


Was this page useful?

Next article

Managed reverse proxy

PostHog's managed reverse proxy service enables you to route traffic through PostHog's infrastructure, simplifying the deployment and management of your PostHog reverse proxy. This guide will walk you through the setup and configuration process. Prerequisites Before setting up the managed reverse proxy, ensure you have the following: A PostHog Cloud account with the Teams add-on Access to your domain's DNS settings. Creating a managed reverse proxy Navigate to organization proxy settings…

Read next article