Connect @crewai.bsky.social with zero egress fee storage for your agents:
www.tigrisdata.com/docs/agents/...
Connect @crewai.bsky.social with zero egress fee storage for your agents:
www.tigrisdata.com/docs/agents/...
Agents re-read datasetsβ a lot. The "data leaving storage" is real.
@crewai.bsky.social + Tigris fixes that.
β’ Unlimited reads, no cost penalty
β’ Durable workspace across agents + runs
β’ Snapshots for reproducible state
Storage built for how agents actually behave.
Guide π
If youβre serious about agent infra, worth a read π
www.tigrisdata.com/blog/case-st...
On Agentuity,
β’ Agents create their own storage
β’ Filesystem available on every node (via TigrisFS + bottomless object storage)
β’ Durable sandbox snapshots
β’ No region-locked architecture
This isnβt about βfaster object storage.β
Itβs about letting agents run anywhere.
AI agents break most infra assumptions.
They pause. Resume. Fork. Snapshot. Move regions.
Thatβs not stateless microservices.
Weβve been working with @agentuity.com
as they build a new cloud for AI agents β and their storage model looks very different
Migrating off MinIO? Guide β
www.tigrisdata.com/docs/migrati...
Running MinIO yourself avoids big cloud egress feesβbut with MinIO retiring its open source project, many teams are rethinking object storage.
Tigris checks many boxes for compliance:
β’ We sign BAAs (healthcare)
β’ Region restrictions for data residency
β’ SOC 2 Type II compliant
β’ Fine-grained IAM
Get started with the Tigris Skills Library: www.tigrisdata.com/blog/skill-l...
We open-sourced our Agent Skills Library β reusable skills that teach AI agents how to use the Tigris SDK, convert images to webp, write conventional commits, and more.
Install them all: npx skills add github.com/tigrisdata/s...
Read more about it π
Neoclouds are challenging hyperscalers with a distributed computing architecture-modeled storage layer that supports computing across any cloud.
Thanks to @tigrisdata.com
Get started with the mcp oidc provider and make auth the easy part: www.tigrisdata.com/blog/mcp-oid...
Building a hosted MCP server? Auth shouldn't be the hard part. We open-sourced our MCP OIDC provider, a minimal, vendor-neutral OIDC layer that works with real MCP clients (Claude, Cursor, etc.) and any IdP.
Blog + code π
Read more on the blog: www.tigrisdata.com/blog/tigris-...
Bam, your terminal now has the power of global dynamic data placement as soon as you type in:
tigris login
If you're a developer, you live in the command line. Tigris' new CLI lets you supercharge your shell with bucket forking, object management, and more all from one easy to use program. It's just an npm install away:
npm install -g @tigrisdata/cli
Want to learn more about how we made it happen? Check out the blog: www.tigrisdata.com/blog/storage...
We're happy to announce that we have a Go SDK for using Tigris in Go programs. We've made the Tigris SDK for Go with deep understanding of the problems of object storage as well as making a simpler interface.
Bom dia all! Xe here and I'm in Portugal this month!
Are you ready to Go? Tigris is!
Update: admin console access is restored. Please follow this thread for updates as they happen: status.tigris.dev/incidents/01...
Due to an upstream DNS provider issue, t3.storage.dev will return NXDOMAIN errors. Please migrate your workloads to use t3.storageapi.dev instead. We are actively working on the situation. Follow this thread for more updates: status.tigris.dev/incidents/01...
You've asked for it and now you've got it: Tigris has a Discord server! www.tigrisdata.com/blog/discord...
Enjoy this mildly hinged Xe post about how they square peg -> round hole'd the backlog of question/answer data into Discord.
Stay safe y'all!
Today we're gonna show you how to use Tigris itself as a key-value store so that you can design your applications around being object storage native.
Check out more on the blog: www.tigrisdata.com/blog/tigris-...
What have you gotten done with object storage? Let us know in the comments!
The way you link things together is via "object storage pointers" where you store the key of a value in a database record, using that to reify and glue everything together.
This does work*, but it sucks.
Usually when you set up an architecture with object storage, you have the "two sources of truth" paradigm. You have your database for structured data (records) and your object storage for unstructured data (AI models, images, datasets, etc).
Fun fact: object storage (AKA: cloud based unlimited FTP server) is actually a key-value store under the hood! There's nothing stopping you from using it as one! Today's blogpost covers the gorey details about how and why you'd want to do that.
More teams are moving out of Big Cloud to neoclouds better built for AI workloads. How does the growth of neoclouds change the storage layer?
Our CEO talked with @thenewstack.io about the new cloud and how distributed computing is taking over and what that means for storage.
ππ
π Read the full recap: www.tigrisdata.com/blog/2025-wr... π