You can set up paths that route to different local ports. As long as your apps don't need to live at the root path you can have as many as you like. And you can still have something on the root path as long as it doesn't need the subpath.

Here's `tailscale funnel status` on my machine:

    $ tailscale funnel status
    
    # Funnel on:
    #     - https://my-machine.tailXXXX.ts.net
    
    https://my-machine.tailXXXX.ts.net (Funnel on)
    |-- /            proxy http://localhost:3000
    |-- /foo         proxy http://localhost:3001
    |-- /bar         proxy http://localhost:3002
    |-- /baz         proxy http://localhost:4004

or just use a tailscale sidecar[0] in a docker container and give it any hostname you want

[0]: https://tailscale.com/blog/docker-tailscale-guide

I have multiple funnels running at once. I just put a tailscale container into my compose stack and that way each compose stack gets its own tailscale instance and thus its own funnel. Happy to share the setup if at all interested.

That's why I keep using tsnet directly, where you can have as many virtual machines, doing sharing or funneling, as you want to.

The CLI doesn't let you do as much as the go library does.

Reverse proxy to additional endpoints.