Sign in

Tigris Data

@tigrisdata.com
228 followers 375 following 443 posts

Tigris is a globally distributed S3-compatible object storage service that provides low latency anywhere in the world. | tigrisdata.com | Based in SFO

PostsRepliesMedia
Tigris Data @tigrisdata.com · 22/09/2026
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?
121
Tigris Data @tigrisdata.com · 15/09/2026
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!
tigrisdata.com
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.
1203
Tigris Data @tigrisdata.com · 21/08/2026
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.
110
Tigris Data @tigrisdata.com · 20/08/2026
𝗪𝗵𝘆 𝗽𝘂𝘁 𝗮𝗴𝗲𝗻𝘁 𝘀𝗮𝗻𝗱𝗯𝗼𝘅 𝘀𝘁𝗮𝘁𝗲 𝗶𝗻 𝗼𝗯𝗷𝗲𝗰𝘁 𝘀𝘁𝗼𝗿𝗮𝗴𝗲? 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.
cubesandbox.com
Tigris Volume Integration Guide | CubeSandbox
Instant, Concurrent, Secure & Lightweight Sandbox Service for AI Agents
120
Tigris Data @tigrisdata.com · 18/08/2026
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.
100
Tigris Data @tigrisdata.com · 11/08/2026
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.
100
Tigris Data @tigrisdata.com · 30/07/2026
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.
100
Tigris Data @tigrisdata.com · 29/07/2026
@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.
100
Tigris Data @tigrisdata.com · 28/07/2026
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.
110
Tigris Data @tigrisdata.com · 23/07/2026
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.
100
Tigris Data @tigrisdata.com · 22/07/2026
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.
100
Tigris Data @tigrisdata.com · 21/07/2026
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...
010
Tigris Data @tigrisdata.com · 16/07/2026
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...
tigrisdata.com
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...
200
Tigris Data @tigrisdata.com · 14/07/2026
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!
tigrisdata.com
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.
110
Tigris Data @tigrisdata.com · 13/07/2026
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.
tigrisdata.com
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.
100
Tigris Data @tigrisdata.com · 10/07/2026
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.
110
Tigris Data @tigrisdata.com · 09/07/2026
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.
tigrisdata.com
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.
100
Tigris Data @tigrisdata.com · 08/07/2026
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...
tigrisdata.com
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.
100
Tigris Data @tigrisdata.com · 07/07/2026
"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...
tigrisdata.com
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.
100
Tigris Data @tigrisdata.com · 06/07/2026
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
t.ly
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.
000
Tigris Data @tigrisdata.com · 03/07/2026
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.
100
Tigris Data @tigrisdata.com · 02/07/2026
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.
110
Tigris Data @tigrisdata.com · 01/07/2026
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.
100
Tigris Data @tigrisdata.com · 30/06/2026
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...
tigrisdata.com
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.
100
Tigris Data @tigrisdata.com · 29/06/2026
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?
tigrisdata.com
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.
061
Tigris Data @tigrisdata.com · 24/06/2026
Hooking an agent up to your object storage usually means handing it credentials and hoping it behaves. That's a lot of trust for something that occasionally invents a delete. storagesdk ships an MCP server, so storage shows up as tools an agent can call.
100
Tigris Data @tigrisdata.com · 23/06/2026
Every git repo you push is really just a pile of objects: your files, compressed and content-addressed, plus a few tiny pointers that move around. That's the whole storage model.
tigrisdata.com
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.
130
Tigris Data @tigrisdata.com · 22/06/2026
Every time a user downloads something from your app, you get charged. With Tigris Data, your bill stays the same whether you have 10 users or 10,000. We are super happy to see Rishi Raj Jain and LaunchFast support Tigris! www.launchfa.st/blog/tigris-...
launchfa.st
Tigris Storage Support Now Available in LaunchFast Starter…
LaunchFast works with Tigris out of the box. Same STORAGE_PROVIDER=s3, same pre-signed upload flow. Point AWS_ENDPOINT_URL_S3 at…
100
Tigris Data @tigrisdata.com · 18/06/2026
Fifty agents, one bucket. They can't share a bucket without overwriting each other, and copying it fifty times is slow and expensive. StorageSDK gives object storage git semantics. Snapshot a bucket, then fork it. A fork is copy-on-write: constant time, shares the parent's bytes.
100
Tigris Data @tigrisdata.com · 17/06/2026
Every object store has its own CLI. AWS, wrangler, gcloud, az. Tigris and ComputeSDK built one CLI for all of them: github.com/storagesdk/s... List a bucket, switch providers by changing one word. It pipes like a real Unix tool.
110
Tigris Data @tigrisdata.com · 16/06/2026
Trying to do AI training on your dataset but you created everything in it as individual objects? Wouldn't it be great if those freakin' storage nerds would just give you a zipfile with everything you want in it?
tigrisdata.com
Tar saved Unix backups in 1979. Now it saves your dataloader. | Tigris Object Storage
Tigris bundles let you pull thousands of objects in one HTTP request as a streaming tar archive — no more one GET per object. Here's how it works and why.
122
Tigris Data @tigrisdata.com · 15/06/2026
Agents sometimes delete the wrong thing. That's no longer a problem: www.tigrisdata.com/blog/soft-de... We just added Soft Delete to Tigris. You can flip it on once, pick a retention window, and every delete just becomes recoverable.
110
Tigris Data @tigrisdata.com · 11/06/2026
S3, R2, GCS, Azure all great storage options - but can they fork buckets? Turns out storage for agents is different, and our compute-based friends need to experiment and drop buckets at will. storagesdk fixes that with one idea: snapshots and forks as first-class operations.
200
Tigris Data @tigrisdata.com · 10/06/2026
Agents can easily manage S3-compatible storage for their own experiments via agent-kit. When you kick off an agent, @tigrisdata.com hands it its own private bucket and a scoped key just for that run, so it has a clean place to work without you wiring up any storage.
100
Tigris Data @tigrisdata.com · 09/06/2026
Object storage finally has an undo button: www.tigrisdata.com/blog/soft-de... Turn on soft delete and every delete drops into a holding state for 7–90 days. Restore inside the window, or Tigris reclaims it for you. Your agent can write to prod, and a wrong delete is no longer a one-way door.
tigrisdata.com
Introducing Soft Delete for Tigris Buckets and Objects | Tigris Object Storage
Tigris now supports soft delete for buckets and objects. Enable it once, and every delete becomes recoverable for up to 90 days before it's permanently removed.
010
Tigris Data @tigrisdata.com · 04/06/2026
Attention Go programmers: we have something for you for once! We've brought our buckety goodness over to Go with our storage-go library! No more having to attach headers in order to rename/move an object, just call RenameObject!
141
Tigris Data @tigrisdata.com · 04/06/2026
Object storage finally branches like Git: www.tigrisdata.com/blog/storage... We built storagesdk with @computesdk. 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: github.com/storagesdk/s...
010
Tigris Data @tigrisdata.com · 03/06/2026
We partnered with @computesdk to build storagesdk: github.com/storagesdk/s... Buckets should branch like Git, and have forks and snapshots as first-class primitives. Most adapters fake that by copying every object into a sibling bucket. The Tigris adapter does it natively.
github.com
GitHub - storagesdk/storagesdk: A unified TypeScript SDK for storage with first-class support for snapshotting, forking across Tigris, Amazon S3, Cloudflare R2, GCS, Azure Blob, Vercel Blob and many m...
A unified TypeScript SDK for storage with first-class support for snapshotting, forking across Tigris, Amazon S3, Cloudflare R2, GCS, Azure Blob, Vercel Blob and many more. - storagesdk/storagesdk
111
Tigris Data @tigrisdata.com · 28/05/2026
"What if our expense-submission agent yeets all the receipts out of the bucket?" Nobody wants that on a threat model. But how do you safely give an AI agent a shell?
111
Tigris Data @tigrisdata.com · 27/05/2026
When agents use object storage, they should work off of forked buckets, not the original production bucket. This way, any bad write can be quarantined.
101
Tigris Data @tigrisdata.com · 26/05/2026
We just shipped multiple lifecycle rules per bucket for Tigris: www.tigrisdata.com/blog/lifecyc... You can route heavy ML datasets to Glacier while auto-deleting stale logs on autopilot. No more global policies or janky deletion scripts.
110
Tigris Data @tigrisdata.com · 21/05/2026
We embedded a Tigris client on our homepage so that if you're in a pinch and need to fork a bucket, we've got your back!
110
Tigris Data @tigrisdata.com · 20/05/2026
@basicmemory.bsky.social just shipped per-file diff/merge for AI context as markdown. Pick any prior version, see changes, pick the lines you want. Built on Tigris bucket versions: every edit = a new object version, with full revision history from one ListObjectVersions call. No Git required 👇
110
Tigris Data @tigrisdata.com · 19/05/2026
Most AI memory locks your context to one platform. Switch tools, lose everything. @basicmemory.bsky.social flips it: your knowledge graph as plain Markdown in your own bucket editable directly. Claude, ChatGPT, etc reads and writes the same files. Read how a four-person team built it on Tigris. 👇
211
Tigris Data @tigrisdata.com · 18/05/2026
We caught the disco bug 🪩✨
000
Tigris Data @tigrisdata.com · 13/05/2026
Prompt injection via the knowledge base is the agent attack surface nobody's talking about. David Myriel built a TypeScript agent on Mastra.ai using Tigris bucket forking as a last line of defense:
110
Tigris Data @tigrisdata.com · 12/05/2026
The Immutable Agent is a pattern for protecting agents that write back to shared storage: t.ly/fIbfl 1. Every agent run executes against a fork of your storage bucket, not the live one. 2. A validator checks the fork. If it passes, it merges into production. If it fails, it gets quarantined.
100
Reposted by Tigris Data
JauntyWunderKind @jauntywunderkind.bsky.social · 08/05/2026
Slick write up by @xeiaso.net on using S2-lite to stream atproto firehose to S3/Tigris supporting multiple consumers. www.tigrisdata.com/blog/durable... > S2 is serverless storage for streams — like Kafka and S3 had a baby. It's not a message queue; it's a durable, ordered, append-only stream store
tigrisdata.com
Durable global streams in Tigris with S2 | Tigris Object Storage
S2 Lite turns S3-compatible object storage into a durable streaming platform. Run it on Tigris for high-cardinality workloads — per-agent reasoning traces, event firehoses — with zero egress fees and ...
052
Tigris Data @tigrisdata.com · 07/05/2026
Wake up to a fresh LLM Wiki of everything from yesterday. One Slack link, and satisfy your FOMO. We built this on Karpathy's pattern. Runs nightly, costs $0.23/run: www.tigrisdata.com/blog/self-up...
000
Tigris Data @tigrisdata.com · 29/04/2026
Coordinate millions of agents without polling. Agent Kit lets you set up webhooks with a single function call—triggering agents on object writes. Event-driven workflows, built directly on storage.
020