Question on license/support/features

[MrLightSpeed0]

Hi quick question in regard to your license and how the product can be used. Do we need to buy a license if we build from the source code to use all features and do self-support via community?

From what I read, it seems that there are two types of support and licenses: community and enterprise, the enterprise one has SaaS or On-Prem. Self-Managed licenses has Starter/Premium/Ultimate options. On the other hand, the community support to me means if we use open source as is (download executable or build from source), we will just go to Github to ask questions if needed. However, from what I red from "enterprise" installation page (the "latest" installation page doesn't mention this at all), it says "...Without a valid license, the application will operate under the Starter license tier, with the following additional limitations:..." then I navigated to "Starter license tier" page, the Starter license is like $718/year (for subscription). With all of these context mentioned, could you please advise, what we would get (features and support) if we just want to build from the source code and may develop/enhance and contribute back on top of the existing source code?

Thank you,

-Rick

[marziaelia]

The community edition of SFTPGo is open source under the AGPLv3 license, and you can build it from the source code and use it without purchasing a license. Commercial licenses are required if you want official support and/or enterprise-only features.

You can find more information here:

https://docs.sftpgo.com/enterprise/#enterprise-edition
https://sftpgo.com/sftpgo-enterprise-on-premises
https://sftpgo.com/compliance.html
https://sftpgo.com/cla.html

[hyaman]

Hi Team,

I’d like to add to Rick’s question regarding the Community Edition.

We are currently testing SFTPGo and plan to deploy it using Docker. The intended use case is to allow multiple external connections to upload files, and then have a scheduled process (e.g. every 10 minutes) that checks for new uploads and downloads the files for further processing.

Are there any limitations in the Community Edition that would affect this scenario, such as:

• Limits on concurrent connections or transfers
• Restrictions when running in Docker
• Any polling, download, or automation constraints we should be aware of

Appreciate any guidance or considerations we should keep in mind when implementing this setup.

Thanks in advance.