Sorry as this might be recurring question that has been asked multiple times.

First of all, thanks for this awesome piece of software.

I have already looked at the compliance page to understand the license for my use-case. I wasn't able to determine if my usage of SFTPGo will fall under tightly coupled usage (without modification #2 clause) or normal usage.

Use-Case
I was looking at SFTPGo to replace a FTP server for a closed sourced application.
In this application,

• FTP server to allow other application to export files to this application.
• On rare occasion, customer access the FTP server using FTP client (e.g. FileZilla, CyberDuck etc) to preview or download pdf documents.
• If SFTPGo is integrated as docker container (as-is, without any modification) along with the application, it will not provide any Web UI for client. But for attribution I can list the SFTPGo in the FTP server welcome message and also list it in the license file.
• Use SFTPGo REST-API, to create user from a bash script.

Based on these scenario, will I be violating AGPLv3 with additional clause that SFTPGo provides if I integrate SFTPGo docker container?

Thanks in advanced.