Changelog
What's changed in Tigris? Look here to find out! This is where we document all of the changes to Tigris, its infrastructure, and other things that you'll find relevant for your work.
August 15, 2025
Org admins can enforce two-factor auth under organization settings
Administrators can configure organizations to require two-factor authentication. In order to use this, you must be using a native Tigris organization, not one created with fly.io.
Fixes (1)
Previously you were able to put any S3 or IAM action into policy documents. Tigris now enforces that these be one of the supported policy actions.
Improvements (3)
July 15, 2025
Benchmarks
We've been hearing from a lot of teams using Tigris for low-latency workloads consisting of billions of tiny files--think logs, AI feature payloads, or metadata. We published a benchmark comparing Tigris to AWS S3 and Cloudflare R2 using a mixed workload of 10 million 1 KB objects, 80% reads and 20% writes.
The results are compelling:
- Tigris is 86.6x faster than R2 and 5.3x faster than S3 at the 90th percentile for read latency.
- Throughput under mixed workloads is 4x higher than S3 and 20x higher than R2.
- Writes are consistently low-latency, with P90 latencies under 17 ms.
These gains come from architectural choices designed specifically for small-object performance: inline storage for tiny objects, log-structured caching, and coalesced key layouts that reduce IOPS pressure at scale.
Tigris Benchmark: 86× Faster Than R2 for Small Objects
Deep dive into how Tigris achieves sub-10ms read latencies and key-value store-like throughput for small object workloads. Includes detailed methodology, results, and instructions to reproduce the benchmarks yourself.
Read the BenchmarksImprovements (4)
Wanted to build your own IAM policies but didn't know where to start? Use the new IAM policy builder to make your own policies from scratch.