To clarify this bit, I don’t mean multiple installs, I mean a single gateway and dashboard but tenants must bind their API listen paths to custom domains so that there is no overlap.
OR
You disable the listen path entry system in the UI, and set Tyk Dashboard up to force defaults, in which case listen paths are actually API IDs and then you can control which virtual tenant API to target from NGINX using a rewrite. This guarantees unique paths and allows you to control how to target those via your rewrites, it also means your tenants can’t break things by editing or adding APIs.
We actually have a service called the host manager that manages NGinX and the relebvant configurations for you.
Here’s all the relevant docs for working in tandem with NGinX:
https://tyk.io/docs/tyk-api-gateway-v1-9/configuration/working-with-nginx/
https://tyk.io/docs/tyk-api-gateway-v1-9/configuration/tyk-domains-and-url-handling/