Tigris and egress billing

Questions / Help
, ,
1

I’m evaluating tigris (and fly itself) for my upcoming project.

I see on the tigris docs that there are no egress fees. However, fly does charge egress fees, and it only calls out that data transfer to tigris is not billed. It’s also unclear on the pricing page for fly tigris:

This pricing can change as data transfer costs are worked out between Fly.io and Tigris.

So I’m curious, given the following line implying tigris deploys on fly:

Tigris is a globally caching, S3-compatible object storage service built on Fly.io infrastructure.

Will provisioning tigris storage with fly storage create subject the storage to fly’s egress fees? I’m comparing vs. Cloudflare R2 which is already slightly cheaper as below:

Tigris

  • Data Storage: $0.02 / GB / month
  • Class A Operations: $5.00 / million requests
  • Class B Operations: $0.50 / million requests
  • Data Transfer (Egress): Free

Cloudflare R2 (Standard)

  • Data Storage: $0.015 / GB / month
  • Class A Operations: $4.50 / million requests
  • Class B Operations: $0.36 / million requests
  • Data Transfer (Egress): Free

Assuming egress is free for both, I’d like to go with tigris to have everything contained in fly. But if fly’s egress fees apply, I will likely need to go with R2.

2

Hi @zaco, it is great to hear that you are evaluating Tigris and Fly.

Indeed, Tigris has no egress fees, which means all data transferred into or out of Tigris is free. The pricing listed in Pricing | Tigris Object Storage Documentation is the source of truth, and what you are charged is based on this pricing, irrespective of whether you create the bucket from the dashboard or from the fly storage command.

Let me know if you have any follow up questions.

3

Excellent, thank you!

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.