SFTPGo sustainability

[drakkan]

Unfortunately SFTPGo is not financially viable yet which means its sustainability model is failing.
SFTPGo users have increased a lot but only a few of you support the project with sponsorships/donations.

With few exceptions, companies/people generally start sponsoring for a few dollars a month ask a lot of questions/features and once they have their answers/features they stop sponsoring. Not to mention the people who don't sponsor at all and who contact me privately if I close as invalid their issues whose answer is in the documentation or big companies using SFTPGo without returning anything back.

SFTPGo offerings on Azure and AWS are by far the cheapest of similar products, and SFTPGo has more features than many commercial products there, yet subscriptions are low.

I can't keep investing all this time in SFTPGo under these conditions. If each of you donated a small amount there would be no sustainability problems but unfortunately this is not the case.

I'm sorry but I'm considering switching to an open core model or something similar where not all features are available in the free version.

I'm posting this in hopes that something will change, but honestly I'm skeptical now. I lost about 10 sponsors, for no reason, this month alone.

[maxiride]

I lost about 10 sponsors, for no reason, this month alone.

It might be due to the new Github sponsorship policies, in case you were unaware they no longer accept PayPal as a payment method and a lot of other projects lost sponsors due to this change. It's also very plausible that many don't know (or ignored the warning emails) and are even unaware that their subscriptions were terminated.

[drakkan]

I lost about 10 sponsors, for no reason, this month alone.

It might be due to the new Github sponsorship policies, in case you were unaware they no longer accept PayPal as a payment method and a lot of other projects lost sponsors due to this change. It's also very plausible that many don't know (or ignored the warning emails) and are even unaware that their subscriptions were terminated.

Maybe this can be true for some sponsors. For some of them I have no contacts other than github username and obviously I can't mention them here or in another post. I tried to contact the other ones but no reply so far

[zbutt-badal]

@drakkan email me zbutt@badal.io ... lets connect there.

[Art3mK]

I just started to evaluate sftpgo, but feature wise it looks very powerful. I'll poke around in my place to see if I can arrange sponsorship for this.

[PlenipotentSS]

I am getting leverage for a company to use SFTPGo for our applications. I will work on a budget addition to try to get some more support.

[jorgelaranjo]

[drakkan]

For those interested, please use the offer from "SFTPGo Authors", the other one is deprecated and will not be updated anymore. Thank you

[drakkan]

Hello,

as a last attempt to keep SFTPGo completely open source I have added some support plans which can be purchased from the SFTPGo website. Thank you

[maxiride]

Glad to hear you worked something out! When the agreed sponsorship period we paid in advance ends, do you prefer we switch over to the subscription plan?

Best,
Federico D'Eredità — INDI

[drakkan]

Glad to hear you worked something out! When the agreed sponsorship period we paid in advance ends, do you prefer we switch over to the subscription plan?

Best, Federico D'Eredità — INDI

as you prefer. I can generate a payment link that matches our current deal (annual payments instead of monthly and the same amount). Thanks for supporting SFTPGo!

[dwoods]

I've just created a subscription to the AWS marketplace "container edition".

I've added a service account to run the app with the recommeded IAM permissions.

Usage Instructions: Run the container using an IAM role with the following permissions:
AWSMarketplaceMeteringRegisterUsage, required for AWS marketplace integration.
SecretsManagerReadWrite, required to store and retrieve the initial installation code.

Is there a specific container registry I need to use for this version and have it register with AWS, or just the standard one (ghcr.io/drakkan/sftpgo)?

Thanks

• Darryl

[drakkan]

I've just created a subscription to the AWS marketplace "container edition".

I've added a service account to run the app with the recommeded IAM permissions.

Usage Instructions: Run the container using an IAM role with the following permissions:
AWSMarketplaceMeteringRegisterUsage, required for AWS marketplace integration.
SecretsManagerReadWrite, required to store and retrieve the initial installation code.

Is there a specific container registry I need to use for this version and have it register with AWS, or just the standard one (ghcr.io/drakkan/sftpgo)?

Thanks

• Darryl

Hello,

thank you for subscribing to container offer, you have to run the images on Amazon ECS or EKS to use the offer.

Below the usage istructions there are the credentials and the links to the Amazon ECR registry to pull the images

the latest version are

709825985650.dkr.ecr.us-east-1.amazonaws.com/sftpgo-authors/sftpgo:v2.5.1
709825985650.dkr.ecr.us-east-1.amazonaws.com/sftpgo-authors/sftpgo:v2.5.1-distroless

distroless images have just been removed from the public repository and will remain available only on ECR (or a private registry for project sponsors who don't want to use AWS services).
If you have never used ECS or EKS it might be a bit tricky to get started with these services

[dwoods]

Thanks for the quick response @drakkan, I guess I didn't go far enough and didnt click the "Launch software" to get to that screen.

I am using EKS and have a lot of services running already, but haven't needed to pull images from ECR yet, just from public and our private registries.

Now I just need to setup something to automatically renew the registry credentials in a pull secret automatically as it looks like they expire after 12 hours...

Would it be acceptable to pull the image locally and push to our own private container registry that we are already have the cluster setup to pull from?

I'm haven't looked into how AWS Marketplace container products work, so not sure if it's a requirement that they're pulled directly from ECR from a metering perspective.

Thanks again

[drakkan]

Thanks for the quick response @drakkan, I guess I didn't go far enough and didnt click the "Launch software" to get to that screen.

I am using EKS and have a lot of services running already, but haven't needed to pull images from ECR yet, just from public and our private registries.

Now I just need to setup something to automatically renew the registry credentials in a pull secret automatically as it looks like they expire after 12 hours...

Would it be acceptable to pull the image locally and push to our own private container registry that we are already have the cluster setup to pull from?

It should work, as an AWS subscriber you can contact us by writing to support at sftpgo.com, please write there for follow up questions, this is a bit off topic here. Thank you!

I'm haven't looked into how AWS Marketplace container products work, so not sure if it's a requirement that they're pulled directly from ECR from a metering perspective.

Thanks again