Has anyone tried using lacinia to run two distinct graphql servers on two different http routes? I know this is sort of counter to the GraphQL philosophy, but considering doing it, for reasons, and wondering if anyone ever does this, if there are any caveats etc.

We don't do that, but there's no reason not to. You could even have one server two sets of routes for two schemas.

Our code uses on Jetty instance to listen on two ports, and applies different authentication based on the port (one port represents external requests, the other internal- within the firewall- requests).

thanks!

We do the same, and we’re also planning on having a separate graphql api on another endpoint to allow (in)direct access to an unstable database.