Tessera

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.

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.

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.

tigrisdata.com

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...

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.

tigrisdata.com

"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...

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.

tigrisdata.com

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

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

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.

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.

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.

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...

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.

tigrisdata.com

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?

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.

tigrisdata.com

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.

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.

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.

tigrisdata.com

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-...

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…

launchfa.st

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.

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.

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?

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.

tigrisdata.com

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.

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.

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.

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.

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.

tigrisdata.com