Deploying a reverse proxy to PostHog Cloud

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 e.yourdomain.com) 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 us.i.posthog.com or eu.i.posthog.com.

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:

• PostHog's managed reverse proxy (Recommended, requires the Teams add-on)
• AWS CloudFront
• Caddy
• Cloudflare
• Kubernetes Ingress Controller
• Netlify
• Next.js rewrites
• Next.js middleware
• Vercel
• Nuxt

Reverse proxy requirements

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

- route: e.yourdomain.com/static/*
  reverse_proxy: https://us-assets.i.posthog.com/static/*
  host_header: us-assets.i.posthog.com

- route: e.yourdomain.com/*
  reverse_proxy: https://us.i.posthog.com/*
  host_header: us.i.posthog.com