I just asked Claude about what it'd cost to use Cloudflare R2 and it came up with this (based on the pricing page). If this is accurate and the cost really is $0-5 USD per month, then this might be a good option (Seqera could own to mitigate risk).

is there a script behind these calculations or did it just come up with the table?

full response

I have quickly checked Tigris (without AI) for comparison, and they have lower limit on the ops, so would be 0.7$ for storage, but about 1.5$ for the requests monthly.

Thanks! If Seqera is going to pay then I think it needs to be CloudFlare to be honest (assuming no major negatives), as we already use them for a lot of infra so it's little to no additional administrative overhead

Is cloud flare also S3 based? Regardless I think switching to object storage would make sense if it's easy to transfer between providers

Cloudflare storage uses their own name R2, but yes it's s3 API compliant. So AWS s3 = Cloudflare R2 for all intents and purposes

Absolutely, I agree that administrative overhead is a major issue and I did not necessarily mean to imply that Seqera should pay. I think costs in that range could also be covered by NGI/SciLifeLab or even privately - I am already privately sponsoring OS developers for more a month than that. 😉 The reason why I was looking elsewhere as well is that we are also considering to somewhere put up new references to replace/supplement the AWS iGenomes once the #C073ZDLNC92 pipeline is released. I seem to remember having heard in a NGI meeting that SciLifeLab is planning to cover hosting them and it makes sense to think test data and references together if we are looking for an object storage provider, no? Compared to the references, the test data will likely be small? PS: Most of the S3-compatible providers to not implement the full API, Conditional Writes is for example a feature that some like Backblaze B2 do not support. But all functionality that we need in a write once, share with everyone scenario is covered.