My company wants to use a project composed by many microservice that are AGPL licensed. We're not worried by about distributing the AGPL parts in open source of course, but some of our services remains proprietary. (I mean, the code was written by us and we just want to connect our backend services to the AGPL project for data analysis)
By example, we have a service A which call a service B. Normally the open source projet do this:
A --> B
But in order to fetch data from A without making any modification on A, we have a proxy service C which acts as B. From C we code anything in order to use other proprietary services.
So the AGPL calls our service C instead of B but we can also redirect the request to B after all.
A --> C or A --> C --> B or even A --> C --> ? (other services) |---> B
Of course we need to modify the docker-compose file to connect C or we need to deploy C with exactly the same configuration as B.
Honestly I think C is illegal here because C is on the same network and the user doesn't know anything from it, it acts like a black box that allows us to use our services.
What should I do ? Making the entired project open source ? Or do you think C is legal here ?
Thank you for reading.