Using Netlify redirects as a reverse proxy

Note: The following self-hosted proxy isn't provided by PostHog, so we can't take responsibility for it! If unsure, we recommend using our managed reverse proxy.

Note: If you are using the EU cloud then use eu instead of us in all domains (e.g. us.i.posthog.com -> eu.i.posthog.com)

Netlify supports redirects and rewrites which we can use as a reverse proxy from an /ingest route. In your netlify.toml file, add a redirect like this:

[[redirects]]
  from = "/ingest/static/*"
  to = "https://us-assets.i.posthog.com/static/:splat"
  host = "us-assets.i.posthog.com"
  status = 200
  force = true

[[redirects]]
  from = "/ingest/*"
  to = "https://us.i.posthog.com/:splat"
  host = "us.i.posthog.com"
  status = 200
  force = true

Note: If deploying SvelteKit on Netlify use _redirects file and place it in static folder, as redirects in netlify.toml configuration are not supported.

/ingest/static/*  https://us-assets.i.posthog.com/static/:splat  200!
/ingest/*         https://us.i.posthog.com/:splat  200!

Note: This proxy configuration works with custom domains but may not work correctly with the default .netlify.app domain. If you're experiencing issues with PostHog requests being blocked, ensure you're using a custom domain rather than the default Netlify domain.

Once done, set the /ingest route of your domain as the API host in your PostHog initialization like this:

posthog.init('<ph_project_api_key>',
  {
    api_host: 'https://www.your-domain.com/ingest',
    ui_host: '<ph_app_host>'
  }
)

Once updated, deploy your changes on Netlify and check that PostHog requests are going to https://www.your-domain.com/ingest by checking the network tab on your domain.