Tigris Data
@tigrisdata.com
Tigris is a globally distributed S3-compatible object storage service that provides low latency anywhere in the world. | https://tigrisdata.com | Based in SFO
Tigris is basically a database company that turned into an object storage company, so we have a lot of opinions about what you can do with them. We use FoundationDB as the backbone of our business. Wouldn't it be great to insert message queue items in the same transaction as inserting data?
September 22, 2026 at 3:14 PM
Tigris is basically a database company that turned into an object storage company, so we have a lot of opinions about what you can do with them. We use FoundationDB as the backbone of our business. Wouldn't it be great to insert message queue items in the same transaction as inserting data?
If our objgit post was so good last time, where's objgit post 2?
Today we have an update on the epic saga of Xe reinventing Git storage on top of object storage: making seek-native packfiles. What does this mean? Well, git is complicated. Huddle into this thread!
Today we have an update on the epic saga of Xe reinventing Git storage on top of object storage: making seek-native packfiles. What does this mean? Well, git is complicated. Huddle into this thread!
You can run git on object storage if you re-make packfiles | Tigris Object Storage
Git packfiles were designed for mmap and local disk, so pulling one object out of a bucket means guessing at a byte range. I wrote a new format instead.
www.tigrisdata.com
September 15, 2026 at 3:36 PM
If our objgit post was so good last time, where's objgit post 2?
Today we have an update on the epic saga of Xe reinventing Git storage on top of object storage: making seek-native packfiles. What does this mean? Well, git is complicated. Huddle into this thread!
Today we have an update on the epic saga of Xe reinventing Git storage on top of object storage: making seek-native packfiles. What does this mean? Well, git is complicated. Huddle into this thread!
An agent can run off a VM image that is larger than the disk it runs on.
AgentENV by KVCache.AI keeps microVM disk images in object storage and pulls down only the blocks each machine actually needs. That is how image size stops being limited by local disk.
AgentENV by KVCache.AI keeps microVM disk images in object storage and pulls down only the blocks each machine actually needs. That is how image size stops being limited by local disk.
August 21, 2026 at 3:42 PM
An agent can run off a VM image that is larger than the disk it runs on.
AgentENV by KVCache.AI keeps microVM disk images in object storage and pulls down only the blocks each machine actually needs. That is how image size stops being limited by local disk.
AgentENV by KVCache.AI keeps microVM disk images in object storage and pulls down only the blocks each machine actually needs. That is how image size stops being limited by local disk.
𝗪𝗵𝘆 𝗽𝘂𝘁 𝗮𝗴𝗲𝗻𝘁 𝘀𝗮𝗻𝗱𝗯𝗼𝘅 𝘀𝘁𝗮𝘁𝗲 𝗶𝗻 𝗼𝗯𝗷𝗲𝗰𝘁 𝘀𝘁𝗼𝗿𝗮𝗴𝗲?
For one sandbox on one machine, a host mount is fine. It starts to matter 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝗿𝘂𝗻 𝗮 𝗳𝗹𝗲𝗲𝘁, where sandboxes are created and destroyed constantly and land on whichever node has room.
For one sandbox on one machine, a host mount is fine. It starts to matter 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝗿𝘂𝗻 𝗮 𝗳𝗹𝗲𝗲𝘁, where sandboxes are created and destroyed constantly and land on whichever node has room.
Tigris Volume Integration Guide | CubeSandbox
Instant, Concurrent, Secure & Lightweight Sandbox Service for AI Agents
cubesandbox.com
August 20, 2026 at 3:26 PM
𝗪𝗵𝘆 𝗽𝘂𝘁 𝗮𝗴𝗲𝗻𝘁 𝘀𝗮𝗻𝗱𝗯𝗼𝘅 𝘀𝘁𝗮𝘁𝗲 𝗶𝗻 𝗼𝗯𝗷𝗲𝗰𝘁 𝘀𝘁𝗼𝗿𝗮𝗴𝗲?
For one sandbox on one machine, a host mount is fine. It starts to matter 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝗿𝘂𝗻 𝗮 𝗳𝗹𝗲𝗲𝘁, where sandboxes are created and destroyed constantly and land on whichever node has room.
For one sandbox on one machine, a host mount is fine. It starts to matter 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝗿𝘂𝗻 𝗮 𝗳𝗹𝗲𝗲𝘁, where sandboxes are created and destroyed constantly and land on whichever node has room.
How does Tigris work? What are the moving parts? Today we have a transcript of our CTO Himank's talk about how Tigris works at a high level and how FoundationDB makes it possible.
August 18, 2026 at 3:27 PM
How does Tigris work? What are the moving parts? Today we have a transcript of our CTO Himank's talk about how Tigris works at a high level and how FoundationDB makes it possible.
Delete doesn't have to mean the data is gone. Tigris lets you un-delete your most precious objects and buckets if you(r agent) didn't really mean to actually remove it for others.
August 11, 2026 at 6:49 PM
Delete doesn't have to mean the data is gone. Tigris lets you un-delete your most precious objects and buckets if you(r agent) didn't really mean to actually remove it for others.
If you use RAGFlow by InfiniFlow to answer questions from your documents, everything it knows lives in its storage backend.
By default, if you use MiniIO, RAGFlow re-reads your corpus every time you tune it.
By default, if you use MiniIO, RAGFlow re-reads your corpus every time you tune it.
July 30, 2026 at 5:04 PM
If you use RAGFlow by InfiniFlow to answer questions from your documents, everything it knows lives in its storage backend.
By default, if you use MiniIO, RAGFlow re-reads your corpus every time you tune it.
By default, if you use MiniIO, RAGFlow re-reads your corpus every time you tune it.
@apache.org OpenDAL fully supports Tigris Data.
This storage layer with one API across 50+ backends, in 17 languages. Tigris config is just three lines.
Get the benefit of multi-region workers, with no cross-region egress charges and no per-region bucket topology to maintain.
This storage layer with one API across 50+ backends, in 17 languages. Tigris config is just three lines.
Get the benefit of multi-region workers, with no cross-region egress charges and no per-region bucket topology to maintain.
July 29, 2026 at 3:59 PM
@apache.org OpenDAL fully supports Tigris Data.
This storage layer with one API across 50+ backends, in 17 languages. Tigris config is just three lines.
Get the benefit of multi-region workers, with no cross-region egress charges and no per-region bucket topology to maintain.
This storage layer with one API across 50+ backends, in 17 languages. Tigris config is just three lines.
Get the benefit of multi-region workers, with no cross-region egress charges and no per-region bucket topology to maintain.
1/ The era of manual install scripts for Blessed Frameworks™ is over. New post on `tigris init --agent` and why agent-native onboarding is becoming the baseline.
July 28, 2026 at 3:41 PM
1/ The era of manual install scripts for Blessed Frameworks™ is over. New post on `tigris init --agent` and why agent-native onboarding is becoming the baseline.
If you use dlt by dltHub to move data, you can set up the pipeline to save your results into a cloud storage bucket that everything else reads from.
Most teams put that bucket on AWS, right next to the pipeline. However, when something reads the data back, AWS charges an egress fee.
Most teams put that bucket on AWS, right next to the pipeline. However, when something reads the data back, AWS charges an egress fee.
July 23, 2026 at 4:27 PM
If you use dlt by dltHub to move data, you can set up the pipeline to save your results into a cloud storage bucket that everything else reads from.
Most teams put that bucket on AWS, right next to the pipeline. However, when something reads the data back, AWS charges an egress fee.
Most teams put that bucket on AWS, right next to the pipeline. However, when something reads the data back, AWS charges an egress fee.
If you self-host ClickHouse, you need to avoid paying egress every time your cluster reads its own data back.
The standard production playbook assumes an S3 bucket sitting next to your cluster. So you point at AWS, and every restore, audit query, and backfill turns into a bandwidth bill.
The standard production playbook assumes an S3 bucket sitting next to your cluster. So you point at AWS, and every restore, audit query, and backfill turns into a bandwidth bill.
July 22, 2026 at 4:03 PM
If you self-host ClickHouse, you need to avoid paying egress every time your cluster reads its own data back.
The standard production playbook assumes an S3 bucket sitting next to your cluster. So you point at AWS, and every restore, audit query, and backfill turns into a bandwidth bill.
The standard production playbook assumes an S3 bucket sitting next to your cluster. So you point at AWS, and every restore, audit query, and backfill turns into a bandwidth bill.
We benchmarked @TigrisData vs S3 vs R2 on 10M small objects...agent state, checkpoints, logs etc.
p90 reads: 7.9ms (Tigris) vs 42ms (S3) vs 681ms
(R2)Sub-10ms means object storage stops being an archive and starts being your app's working memory.
Full report: www.tigrisdata.com/blog/benchma...
p90 reads: 7.9ms (Tigris) vs 42ms (S3) vs 681ms
(R2)Sub-10ms means object storage stops being an archive and starts being your app's working memory.
Full report: www.tigrisdata.com/blog/benchma...
July 21, 2026 at 4:03 PM
We benchmarked @TigrisData vs S3 vs R2 on 10M small objects...agent state, checkpoints, logs etc.
p90 reads: 7.9ms (Tigris) vs 42ms (S3) vs 681ms
(R2)Sub-10ms means object storage stops being an archive and starts being your app's working memory.
Full report: www.tigrisdata.com/blog/benchma...
p90 reads: 7.9ms (Tigris) vs 42ms (S3) vs 681ms
(R2)Sub-10ms means object storage stops being an archive and starts being your app's working memory.
Full report: www.tigrisdata.com/blog/benchma...
One of the quiet lies of self-hosted @ClickHouseDB is that your hot data lives on your hardware. Your backups and cold partitions usually live on AWS S3, and AWS charges $0.09/GB to read your own bytes back.
www.tigrisdata.com/blog/clickho...
www.tigrisdata.com/blog/clickho...
The Most Expensive ClickHouse Query Is the Restore | Tigris Object Storage
Self-hosted ClickHouse runs on cheap compute, but its backups and cold tier usually live on AWS S3, and AWS charges $0.09/GB to read your own data back. Point BACKUP TO S3 and TTL tiering at Tigris in...
www.tigrisdata.com
July 16, 2026 at 3:48 PM
One of the quiet lies of self-hosted @ClickHouseDB is that your hot data lives on your hardware. Your backups and cold partitions usually live on AWS S3, and AWS charges $0.09/GB to read your own bytes back.
www.tigrisdata.com/blog/clickho...
www.tigrisdata.com/blog/clickho...
When dealing with complicated authentication schemes, sometimes the biggest weakness in your process is actually the key thing that makes a feature possible. Learn about how presigned URLs work in object storage and how they flip a weakness into a feature!
Presigned URLs are technically a security vuln | Tigris Object Storage
Presigned URLs are replay attacks you commit on purpose. How SigV4 signs the clock, what a presigned URL grants on Tigris storage, and what it costs you.
www.tigrisdata.com
July 14, 2026 at 4:33 PM
When dealing with complicated authentication schemes, sometimes the biggest weakness in your process is actually the key thing that makes a feature possible. Learn about how presigned URLs work in object storage and how they flip a weakness into a feature!
What is an agent? Is it the LLM......the harness?....the context?
We think it's the state. You can burn everything down, but you will always be able to rebuild an agent from its state files.
State files can either be stored in a database, or in a plain s3 bucket.
We think it's the state. You can burn everything down, but you will always be able to rebuild an agent from its state files.
State files can either be stored in a database, or in a plain s3 bucket.
Where Does the Agent Live? | Tigris Object Storage
Your agent runs in a disposable sandbox, but it can't live there. A breakdown of everything in the agent's world, and why it should be one forkable bucket.
www.tigrisdata.com
July 13, 2026 at 4:06 PM
What is an agent? Is it the LLM......the harness?....the context?
We think it's the state. You can burn everything down, but you will always be able to rebuild an agent from its state files.
State files can either be stored in a database, or in a plain s3 bucket.
We think it's the state. You can burn everything down, but you will always be able to rebuild an agent from its state files.
State files can either be stored in a database, or in a plain s3 bucket.
Object storage finally branches like Git
We helped ComputeSDK build storagesdk. With this universal SDK, you can fork a bucket, let an agent or experiment run wild, then keep it or throw it away.
Your production data never moves and the agent knowledge base is secure.
We helped ComputeSDK build storagesdk. With this universal SDK, you can fork a bucket, let an agent or experiment run wild, then keep it or throw it away.
Your production data never moves and the agent knowledge base is secure.
July 10, 2026 at 4:04 PM
Object storage finally branches like Git
We helped ComputeSDK build storagesdk. With this universal SDK, you can fork a bucket, let an agent or experiment run wild, then keep it or throw it away.
Your production data never moves and the agent knowledge base is secure.
We helped ComputeSDK build storagesdk. With this universal SDK, you can fork a bucket, let an agent or experiment run wild, then keep it or throw it away.
Your production data never moves and the agent knowledge base is secure.
Moving storage providers usually means writing a migration script and babysitting it.
Tigris does it in one CLI command. You can point it at your old provider with a read-only key, run it, walk away. If interrupted, it resumes where it left off.
Tigris does it in one CLI command. You can point it at your old provider with a read-only key, run it, walk away. If interrupted, it resumes where it left off.
Migrate your data with the Tigris CLI | Tigris Object Storage
Move an entire bucket to Tigris in one command. The Tigris CLI scans every
object and migrates it safely from any S3-compatible provider. Here's how to
set it up.
www.tigrisdata.com
July 9, 2026 at 3:39 PM
Moving storage providers usually means writing a migration script and babysitting it.
Tigris does it in one CLI command. You can point it at your old provider with a read-only key, run it, walk away. If interrupted, it resumes where it left off.
Tigris does it in one CLI command. You can point it at your old provider with a read-only key, run it, walk away. If interrupted, it resumes where it left off.
Why back agent checkpoints with object storage?
For one agent on one machine, SQLite or Postgres are just fine. It starts to matter when you run a fleet of agents or a multi-tenant platform, where traffic gets bursty and parallel.
www.tigrisdata.com/blog/eval-ag...
For one agent on one machine, SQLite or Postgres are just fine. It starts to matter when you run a fleet of agents or a multi-tenant platform, where traffic gets bursty and parallel.
www.tigrisdata.com/blog/eval-ag...
Every Tenant Has a Past: Evaluating LangGraph Agents | Tigris Object Storage
Fork a customer's entire LangGraph agent state, replay their conversations through a prompt change, and judge it head-to-head before you ship to prod.
www.tigrisdata.com
July 8, 2026 at 3:11 PM
Why back agent checkpoints with object storage?
For one agent on one machine, SQLite or Postgres are just fine. It starts to matter when you run a fleet of agents or a multi-tenant platform, where traffic gets bursty and parallel.
www.tigrisdata.com/blog/eval-ag...
For one agent on one machine, SQLite or Postgres are just fine. It starts to matter when you run a fleet of agents or a multi-tenant platform, where traffic gets bursty and parallel.
www.tigrisdata.com/blog/eval-ag...
"Where does the agent run?" is a solved question: a Daytona sandbox that boots in 90ms and dies on purpose.
The question nobody asks: if the place an agent runs is built to be destroyed, where does the agent live?
www.tigrisdata.com/blog/where-d...
The question nobody asks: if the place an agent runs is built to be destroyed, where does the agent live?
www.tigrisdata.com/blog/where-d...
Where Does the Agent Live? | Tigris Object Storage
Your agent runs in a disposable sandbox, but it can't live there. A breakdown of everything in the agent's world, and why it should be one forkable bucket.
www.tigrisdata.com
July 7, 2026 at 5:37 PM
"Where does the agent run?" is a solved question: a Daytona sandbox that boots in 90ms and dies on purpose.
The question nobody asks: if the place an agent runs is built to be destroyed, where does the agent live?
www.tigrisdata.com/blog/where-d...
The question nobody asks: if the place an agent runs is built to be destroyed, where does the agent live?
www.tigrisdata.com/blog/where-d...
FYI - you can reliably use object storage as a key-value store. You probably already do, you just put a database in front of it. blob in the bucket, key in the DB.
We say.... drop the db. Object storage is already a KV store.
t.ly/oxC_T
We say.... drop the db. Object storage is already a KV store.
t.ly/oxC_T
Using Tigris as a key-value store | Tigris Object Storage
Learn how to use Tigris object storage as a powerful key-value store for both structured and unstructured data, eliminating the need for separate databases.
t.ly
July 6, 2026 at 4:52 PM
FYI - you can reliably use object storage as a key-value store. You probably already do, you just put a database in front of it. blob in the bucket, key in the DB.
We say.... drop the db. Object storage is already a KV store.
t.ly/oxC_T
We say.... drop the db. Object storage is already a KV store.
t.ly/oxC_T
Object storage finally has an undo button: tigrisdata.com/blog/soft-de...
You can turn on soft delete and every delete drops into a holding state for 7–90 days.
You can turn on soft delete and every delete drops into a holding state for 7–90 days.
July 3, 2026 at 4:47 PM
Object storage finally has an undo button: tigrisdata.com/blog/soft-de...
You can turn on soft delete and every delete drops into a holding state for 7–90 days.
You can turn on soft delete and every delete drops into a holding state for 7–90 days.
Tigris is happy to be partnering with Isorun to bring persistent state to their agentic runtime.
Isorun gives agents fast, hardware-isolated compute. We give them durable, forkable disks, so sandboxes stay disposable, and the state that matters survives.
Isorun gives agents fast, hardware-isolated compute. We give them durable, forkable disks, so sandboxes stay disposable, and the state that matters survives.
July 2, 2026 at 5:11 PM
Tigris is happy to be partnering with Isorun to bring persistent state to their agentic runtime.
Isorun gives agents fast, hardware-isolated compute. We give them durable, forkable disks, so sandboxes stay disposable, and the state that matters survives.
Isorun gives agents fast, hardware-isolated compute. We give them durable, forkable disks, so sandboxes stay disposable, and the state that matters survives.
We built a self-updating knowledge base with Tigris! It reads your feeds nightly and posts a digest to Slack.
Our product gives agents durable storage they can write to unattended, where a failed run can never corrupt what's already there.
Our product gives agents durable storage they can write to unattended, where a failed run can never corrupt what's already there.
July 1, 2026 at 1:22 PM
We built a self-updating knowledge base with Tigris! It reads your feeds nightly and posts a digest to Slack.
Our product gives agents durable storage they can write to unattended, where a failed run can never corrupt what's already there.
Our product gives agents durable storage they can write to unattended, where a failed run can never corrupt what's already there.
Your agent's regressions don't show up against fixtures. They show up against real customer history, the kind a hand-written test thread never has.
www.tigrisdata.com/blog/eval-ag...
www.tigrisdata.com/blog/eval-ag...
Every Tenant Has a Past: Evaluating LangGraph Agents | Tigris Object Storage
Fork a customer's entire LangGraph agent state, replay their conversations through a prompt change, and judge it head-to-head before you ship to prod.
www.tigrisdata.com
June 30, 2026 at 2:11 PM
Your agent's regressions don't show up against fixtures. They show up against real customer history, the kind a hand-written test thread never has.
www.tigrisdata.com/blog/eval-ag...
www.tigrisdata.com/blog/eval-ag...
Point a git server at an object storage bucket and see if it works: t.ly/8e8RJ
We think of git as living on a disk, but Xe says that the disk was never essential. git is an object store that happens to use a filesystem to persist itself.
If git doesn't need a filesystem, what else could back it?
We think of git as living on a disk, but Xe says that the disk was never essential. git is an object store that happens to use a filesystem to persist itself.
If git doesn't need a filesystem, what else could back it?
I taught a bucket to speak git | Tigris Object Storage
objgit is a single-binary git server that stores repositories directly in
Tigris — no disk, no git binary, no database. To my shock and horror, it
worked.
www.tigrisdata.com
June 29, 2026 at 4:36 PM
Point a git server at an object storage bucket and see if it works: t.ly/8e8RJ
We think of git as living on a disk, but Xe says that the disk was never essential. git is an object store that happens to use a filesystem to persist itself.
If git doesn't need a filesystem, what else could back it?
We think of git as living on a disk, but Xe says that the disk was never essential. git is an object store that happens to use a filesystem to persist itself.
If git doesn't need a filesystem, what else could back it?