I think there is a fundamental "proxy problem" with AGPL-like licenses. If I put a transparent proxy in front of the service and let users connect to that am I

I think there is a fundamental "proxy problem" with AGPL-like licenses. If I put a transparent proxy in front of the service and let users connect to that am I exposing it to them? Almost certainly yes. What about a proxy that provides a HTTP API for the database and then translates it to the native protocol? Probably also considered exposing. If I put stock data into the database and put up a website that displays a stock ticker am I exposing the database to them? Very likely not? But what if the user can also write stock values? What if they can sum the values of various stocks. Basically there is no clear line where you stop exposing the database to the user and you stop needing to provide the source of whatever intermediate services you are using. So lawyers will recommend erring on the side of caution and just not touching it.