Thanks for the response, though my question was more about whether you've thought through how your webhooks based approach can work through VPNs.

For example, one of the organisations I work with uses a CheckPoint capsule VPN with some non-standard configuration that's controlled by their IT department that manages and supports client workstations.

To even access the Git server requires the user to be connected through VPN. I suppose you'll need Tara to follow the same route to the Git server that's sitting behind this VPN, right? This would be quite a different story than having Tara connect to a public facing self-hosted Git server, e.g., on our own data center or on AWS.

I suspect this will he a hard (impossible?) problem to solve unless Tara itself goes self-hosted and is on the same VPC as the Git server behind our VPN.

Thanks for clarifying. Yes this would be fairly different and requires an extra layer or configuration on our backend. You’re absolutely right about following the same route to the server per user and since our current configuration allows a workspace level workflow, we would have to write some middleware to handle this use case.

You are absolutely right about a self hosted solution being the better workaround which means it resides on an internally accessible network where the setup experience would be much more seamless.

For those kinds of situations, I've seen SaaS companies offer some kind of internal "connector", which could then establish an outgoing connection to a known domain, thus allowing the IT dept. to limit the access as they require.