1. X
  2. Tigris Data
Log inSign up
Tigris Data
765 posts
user avatar
Tigris Data
@TigrisData
Tigris is a globally distributed S3-compatible object storage service that provides low latency anywhere in the world. Now with bucket forking.
San Francisco Bay Area
tigrisdata.com
Joined March 2022
23
Following
2,363
Followers
RepliesRepliesMediaMedia
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
Don't miss what's happening
People on X are the first to know.
Log inSign up

New to X?

Sign up now to get your own personalized timeline!

Create account

By signing up, you agree to the Terms of Service and Privacy Policy, including Cookie Use.

  • user avatar
    Tigris Data
    @TigrisData
    11h
    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
    103
  • user avatar
    Tigris Data
    @TigrisData
    Jul 22
    If you self-host @ClickHouseDB , 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
    232
  • user avatar
    Tigris Data
    @TigrisData
    Jul 21
    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 methodology + repro
    178
  • user avatar
    Tigris Data
    @TigrisData
    Jul 16
    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. A 500 TB restore costs tens of thousands of dollars. That's why nobody
    The Most Expensive ClickHouse Query Is the Restore | Tigris Object Storage
    From tigrisdata.com
    287
  • user avatar
    Tigris Data
    @TigrisData
    Jul 14
    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!
    274
    user avatar
    Tigris Data
    @TigrisData
    Jul 14
    Read more on the blog:
    Presigned URLs are technically a security vuln | Tigris Object Storage
    From tigrisdata.com
    145
  • user avatar
    Tigris Data
    @TigrisData
    Jul 13
    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. Storing
    Where Does the Agent Live? | Tigris Object Storage
    From tigrisdata.com
    191
  • user avatar
    Tigris Data
    @TigrisData
    Jul 10
    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.
    199
    user avatar
    Tigris Data
    @TigrisData
    Jul 10
    Take a look:
    GitHub - storagesdk/storagesdk: A unified TypeScript SDK for storage with first-class support for...
    From github.com
    59
  • Tigris Data reposted
    user avatar
    Ovais Tariq
    @ovaistariq
    Jul 9
    Loving this collaboration between @prisma Compute and Tigris.
    user avatar
    Kristóf Siket
    @kristofsik
    Jul 9
    Build logs on @prisma Compute are available through the CLI, and now also the Console UI. Creating such a feature requires low latency and durability. We solved this using prisma/streams on top of @TigrisData (modern, fast, and S3-compatible object storage).
    00:00
    2K
  • user avatar
    Tigris Data
    @TigrisData
    Jul 9
    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. To be safe, turn on
    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.
    224
  • user avatar
    Tigris Data
    @TigrisData
    Jul 8
    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.
    Every Tenant Has a Past: Evaluating LangGraph Agents | Tigris Object Storage
    From tigrisdata.com
    243
    user avatar
    Tigris Data
    @TigrisData
    Jul 8
    Object storage has no connection pool to size or exhaust. Checkpoint reads and writes are plain S3 requests. Most LangGraph fleets default to a database, where tenant separation is a WHERE clause. With buckets, it's an IAM boundary. A leaked key touches one tenant, not all of
    Checkpoint LangGraph Agents on Tigris | Tigris Object Storage Documentation
    From tigrisdata.com
    128
    user avatar
    Tigris Data
    @TigrisData
    Jul 8
    If your storage supports forking, you can branch an agent's entire history by reference. Fork prod, point a candidate prompt at it, and replay real conversations. We just shipped a LangGraph checkpoint saver that works exactly this way.
    pypi.org
    langgraph-checkpoint-tigris
    Library with a Tigris object-storage implementation of LangGraph checkpoint saver, with zero-copy bucket-fork branching.
    52
  • user avatar
    Tigris Data
    @TigrisData
    Jul 7
    "Where does the agent run?" is a solved question: a @daytonaio 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?
    Where Does the Agent Live? | Tigris Object Storage
    From tigrisdata.com
    2.3K
    user avatar
    Tigris Data
    @TigrisData
    Jul 7
    Strip an agent to parts: model, harness, sandbox, state. Three are replaceable. The state IS the agent. And today it's scattered across Postgres, Pinecone, Redis, LangGraph, and Temporal. You can't checkpoint an agent that lives in five places.
    149
    user avatar
    Tigris Data
    @TigrisData
    Jul 7
    Put the whole world in one forkable bucket instead. Fork it per run, work against the fork, promote the winner, delete the rest. @daytonaio checkpoints the machine; the bucket checkpoints the agent. An agent you can't fork is an agent you can't trust. Blog:
    Where Does the Agent Live? | Tigris Object Storage
    From tigrisdata.com
    80
  • user avatar
    Tigris Data
    @TigrisData
    Jul 6
    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.
    Using Tigris as a key-value store | Tigris Object Storage
    From tigrisdata.com
    199
  • user avatar
    Tigris Data
    @TigrisData
    Jul 3
    Object storage finally has an undo button: tigrisdata.com/blog/soft-dele… You can 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 coding agent or CI job can write straight to prod, and
    GIF
    826
  • user avatar
    Tigris Data
    @TigrisData
    Jul 2
    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.
    450
    user avatar
    Tigris Data
    @TigrisData
    Jul 2
    Workspace files and snapshots outlive any single sandbox, move between regions, and clone instantly. Agents start fast, run isolated, and keep state when they need it, with no storage layer for developers to manage.
    Persistent Storage · Isorun Docs
    From docs.isorun.ai
    151