We’re enabling billing for Tigris in July

Since we launched our public beta three months ago, our usage has skyrocketed, and hundreds of early adopters have picked Tigris as their storage solution. We’ve implemented tons of requested features and invested heavily in Tigris’ performance, security, and reliability. We’re grateful for your feedback and confident that we are on track to make the most developer-friendly object storage service.

With that, we will start billing for Tigris usage in July because we’re confident that Tigris is reliable enough for us to justify doing that. Check out our pricing page for details on the pricing structure. The beta tag will stay, but we’ll offer the same support expected from a highly reliable production-ready platform. Check out our SLA page for details about our uptime commitment.


  • Data storage is $0.02 per GB
    • Unless you elect to control the data distribution and store multiple copies of your data in different regions, if you create primary copies in two regions, you will be charged twice for the object.
    • Note that this doesn’t apply to Tigris’s default behavior of managing the data distribution for you. As always, that counts as a single copy. Neither does this apply to pull-through caching, which is free, as always.
  • PUT, COPY, POST, and LIST requests are $0.005/1000 requests
  • GET, SELECT, and all other requests are $0.0005/ 1000 requests
  • Data egress: $0.00 per GB
  • Unauthorized requests to your buckets: $0.00 per request

Despite all of this, if you suffer an attack and get an unexpectedly large bill, please contact us at help@tigrisdata.com. We are more than happy to discuss a refund.

Starting June 1st, 2024, you will see detailed usage and costs in your Fly.io organization billing dashboard. The actual charge will be made on your July 1st Fly.io invoice.

Beta program in numbers

We thought you might also be interested in some stats to see how well we have done in the last three months:

  • ~1 PB of storage
  • ~1 B objects
  • ~250 M requests per day
  • ~1 K buckets

New features and enhancements

Supporting Tigris adoption and usage with feature work has been heartwarming. Some of the new features added since our launch include:

And there’s more to come!

We hope you have fun building with Tigris and would love to see what you build. Reach out to us on X (formerly Twitter) or the Fly.io community forum, and give us your feedback. We can’t wait to see what you all dream up.


From General to Fresh Produce

Is this available now or from June 1st?

Will there be an option to have the shadow check that all objects have been moved? It would be good if there was a finalize option where it would copy over any missing objects.

This is available now. Most of our users are already using us in production. Our uptime commitments are available, and we have incident monitoring and reporting in place.

1 Like

We don’t have this yet. But this is good feedback. Thanks.


B is not a metric/SI prefix and large number names vary across natural languages (1 billion has 9 zeroes in English and 12 in Polish for ex), so just to confirm and make it clear to all non-native speakers: this means 10e9 in scientific notation?

I meant 1,000,000,000 objects.

1 Like

Very happy to hear egress is $0/GB and region restrictions are a new feature. Looking forwards to using Tigris more @ovaistariq


You can now also see usage and billing details on Tigris dashboard


@ovaistariq another feature request is to support OIDC authentication (Assuming Cloud Roles on Fly.io Machines - Fresh Produce - Fly.io). That way we wouldn’t need to manage keys and can just specify on a per bucket basis what orgs/apps can access those buckets.

1 Like

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