LoginSign Up
← Back to all sparks
T

Tigris

DEVOPS
Velocity5.0

Tigris still ships features inside essays, and the newest one is a recycle bin.

object-storageimmutabilityagent-natives3-compatibilityegress-costs
◆Current state
The feed is a blog, not a changelog, and each post is an engineering argument that happens to carry a product change. This window has three: a recycle bin for objects and buckets built on immutable storage so deletion in a geo-replicated active-active system stops meaning data loss, agent-native onboarding via tigris init --agent, and a CLI that migrates an entire bucket from any S3-compatible provider in one command. The rest are essays on SigV4, presigned URLs, and ClickHouse restore economics.
◆Where it's heading
Two arguments run underneath everything: object storage should be the durable state layer for agents, and S3 compatibility is a surface to be explained rather than merely claimed. The SigV4 and presigned-URL posts are the second argument in practice — publishing where the protocol is dangerous is a credibility play against the incumbent. The recycle bin extends the immutability story into a place immutable systems usually struggle, which is undoing a mistake.
◆Prediction
Expect more posts that pair a protocol critique with the Tigris behavior that answers it; the egress-cost framing from the ClickHouse post is the one most likely to recur as a paid migration path.

◆Recent moves

  1. 21h ago

    Extending immutability: deletion without losing data

    A recycle bin for objects and buckets, built on top of immutable storage so a delete in a geo-replicated active-active system is recoverable rather than final. It extends the immutability thesis into the case that usually breaks it, though the entry is a blog teaser rather than a release note.

    View source ↗
  2. 5d ago

    SigV4 authentication is surprisingly complicated

    An engineering essay on implementing SigV4 — canonicalization, clock skew, and a cache that cannot hold the key. Credibility content for an S3-compatible vendor, with no product change attached.

    View source ↗
  3. 14d ago

    Humans don't install software themselves anymore, their agents do

    Agent-native onboarding: tigris init --agent prints instructions meant for a coding agent rather than a human installer. It is a concrete extension of the direction Agent Kit set in April rather than a new one, and it targets the moment where a developer's agent, not the developer, picks the storage provider.

    View source ↗
  4. 26d ago

    The Most Expensive ClickHouse Query Is the Restore

    A positioning post arguing that ClickHouse backups and cold tiers on S3 pay $0.09/GB to read your own data back, and that pointing BACKUP TO and TTL tiering at Tigris removes it. Cost argument, not a product change.

    View source ↗
  5. 28d ago

    Presigned URLs are technically a security vuln

    An essay framing presigned URLs as deliberate replay attacks and walking through what one actually grants. Same pattern as the SigV4 post: explain the protocol's sharp edges publicly.

    View source ↗
  6. 1mo ago

    Migrate your data with the Tigris CLI

    The CLI gains one-command bucket migration from any S3-compatible provider, scanning every object and moving it. Migration tooling is the unglamorous requirement for the egress arguments the other posts make — the pitch only works if switching is cheap.

    View source ↗