LoginSign Up
← Back to all sparks
T

Tigris

DEVOPS
Velocity5.0

Tigris is positioning object storage as the substrate for AI agents

object-storageai-agentss3-compatiblebucket-forkingdeveloper-infra
◆Current state
Tigris is building S3-compatible object storage with a distinct thesis: buckets as forkable, snapshot-able substrate for AI agents. Concrete releases in this window are solid storage primitives — soft delete with 90-day recovery, a streaming tar bundle API to pull thousands of objects in one request, prefix-filtered lifecycle rules, and a CLI migrate command. But much of the feed is engineering-blog material (agent sandboxes, forking LangGraph state, a git server stored in a bucket) that argues the thesis rather than shipping a feature.
◆Where it's heading
The direction is clear and consistent: make storage the durable home for agents that otherwise live in disposable sandboxes — copy-on-write bucket forks, agent shells, provider-agnostic SDKs with snapshots and forks built in. The product releases keep S3 parity table-stakes (soft delete, lifecycle, migration) while the narrative work stakes out the agent-substrate position. Worth noting that the changelog leans heavily on blog posts, so raw entry cadence overstates shipping velocity.
◆Prediction
Expect more agent-oriented primitives around forking and snapshotting to graduate from blog demos into shipped API surface; the entries point that way but don't pin a specific next release.

◆Recent moves

  1. 19h ago

    Migrate your data with the Tigris CLI

    A Tigris CLI migrate command moves an entire bucket from any S3-compatible provider in one command, scanning and transferring every object. A practical onboarding feature that lowers the switching cost onto Tigris.

    View source ↗
  2. 2d ago

    Where Does the Agent Live?

    A long-form blog post arguing that an agent's world should live in one forkable bucket rather than a disposable sandbox. Thesis-building content that reinforces the agent-substrate positioning, with no product change attached.

    View source ↗
  3. 9d ago

    Every Tenant Has a Past: Evaluating LangGraph Agents

    A blog post demonstrating how forking a customer's LangGraph agent state lets you replay conversations through a prompt change and judge it before shipping. Illustrative of Tigris's forking pitch, but a write-up rather than a release.

    View source ↗
  4. 16d ago

    I taught a bucket to speak git

    An engineering blog about objgit, a single-binary git server that stores repositories directly in Tigris with no disk or database. A side-project demonstration of the storage's flexibility, not a product feature.

    View source ↗
  5. 28d ago

    Tar saved Unix backups in 1979. Now it saves your dataloader.

    A bundle API lets clients pull thousands of objects in one HTTP request as a streaming tar archive, replacing one GET per object. A real throughput feature aimed at data-loader and ML workloads.

    View source ↗
  6. 1mo ago

    Introducing Soft Delete for Tigris Buckets and Objects

    Soft delete for buckets and objects makes every delete recoverable for up to 90 days before permanent removal, enabled once per account. A meaningful data-protection primitive that brings Tigris to parity with mature object stores.

    View source ↗