1. X
  2. Tigris Data
Log inSign up
Tigris Data
762 posts
Image
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,355
Followers
RepliesRepliesMediaMedia

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.

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
  • 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
    Image
    The Most Expensive ClickHouse Query Is the Restore | Tigris Object Storage
    From tigrisdata.com
    2590259
  • 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!
    2660266
    user avatar
    Tigris Data
    @TigrisData
    Jul 14
    Read more on the blog:
    Image
    Presigned URLs are technically a security vuln | Tigris Object Storage
    From tigrisdata.com
    1390139
  • 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
    Image
    Where Does the Agent Live? | Tigris Object Storage
    From tigrisdata.com
    1860186
  • 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.
    Image
    1940194
    user avatar
    Tigris Data
    @TigrisData
    Jul 10
    Take a look:
    Image
    GitHub - storagesdk/storagesdk: A unified TypeScript SDK for storage with first-class support for...
    From github.com
    55055
  • 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).
    Image
    00:00
    2K02K
  • 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
    Image
    Migrate your data with the Tigris CLI | Tigris Object Storage
    From tigrisdata.com
    2210221
  • 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.
    Image
    Every Tenant Has a Past: Evaluating LangGraph Agents | Tigris Object Storage
    From tigrisdata.com
    2420242
    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
    Image
    Checkpoint LangGraph Agents on Tigris | Tigris Object Storage Documentation
    From tigrisdata.com
    1270127
    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.
    Image
    pypi.org
    langgraph-checkpoint-tigris
    Library with a Tigris object-storage implementation of LangGraph checkpoint saver, with zero-copy bucket-fork branching.
    51051
  • 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?
    Image
    Where Does the Agent Live? | Tigris Object Storage
    From tigrisdata.com
    2.3K02.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.
    Image
    1480148
    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:
    Image
    Where Does the Agent Live? | Tigris Object Storage
    From tigrisdata.com
    79079
  • 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.
    Image
    Using Tigris as a key-value store | Tigris Object Storage
    From tigrisdata.com
    1980198
  • 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
    Image
    GIF
    8240824
  • 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.
    Image
    4460446
    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.
    Image
    Persistent Storage · Isorun Docs
    From docs.isorun.ai
    1490149
  • user avatar
    Tigris Data
    @TigrisData
    Jul 1
    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. The agent writes through Tigris
    Image
    1940194
  • user avatar
    Tigris Data
    @TigrisData
    Jun 30
    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.
    Image
    Every Tenant Has a Past: Evaluating LangGraph Agents | Tigris Object Storage
    From tigrisdata.com
    2200220
    user avatar
    Tigris Data
    @TigrisData
    Jun 30
    To catch them you need to test against the agent's real state. On Postgres that means a dump-and-restore that gets slower with every checkpoint. So most teams fall back to fixtures and ship blind.
    1120112
    user avatar
    Tigris Data
    @TigrisData
    Jun 30
    langgraph-checkpoint-tigris stores checkpoints on object storage, so you can fork the whole agent by reference: no data copy, constant time. Fork prod, replay real threads through the change, compare to baseline, drop the fork.
    Image
    GitHub - tigrisdata/tigris-langgraph
    From github.com
    1020102
Advertisement
Advertisement