Linkerd vs Tigris
Side-by-side trajectory, velocity, and editorial themes.
Linkerd coasts on its 2.19 post-quantum release while filling the gap with technical blog content.
Linkerd's stable cadence has slowed: the last named release is 2.19 from October 2025, which made post-quantum key exchange the default TLS mode. Since then, the team has leaned on edge-release roundups and community blog posts — deep dives into linkerd-destination, protocol detection, certificate rotation, and how Kubernetes native sidecars interact with mesh shutdown semantics — rather than feature-stamped stable releases.
The project is in mature-maintenance posture. Edge releases keep code moving, but the messaging is shifting toward operational guidance (cert rotation, native sidecars, OTel integration) rather than new mesh capabilities. The next strategic question is whether 2.20 lands a directional feature or whether Linkerd keeps positioning as the lightweight, predictable alternative to Istio's growing surface area.
Expect the next named release to formalize Kubernetes native sidecar support as the recommended deployment mode, and OpenTelemetry-based metrics to graduate from edge into stable.
Tigris turns its object store into agent infrastructure with Agent Kit, agent-shell, and durable global streams.
Tigris's release stream is a sustained product-marketing push around AI-agent storage primitives. Agent Kit landed as a TypeScript SDK exposing bucket forks, workspaces, checkpoints, and event coordination. agent-shell put a virtual bash environment with persistent storage in front of those primitives. Durable global streams via S2 Lite extended the object store into a streaming substrate suitable for per-agent reasoning traces. Around the launches, case studies and tutorials (Basic Memory, the $10 self-updating knowledge base) make the pitch concrete.
Tigris is staking a position that the right substrate for AI agents is not a database, vector store, or queue — it is a globally-distributed, fork-able object store. Each blog and SDK in this batch reinforces that thesis from a different angle: storage as message queue, fork-per-agent sandboxing, storage-protected agent containment, streams for reasoning traces. The competitive map being drawn includes R2, S3 Express, Backblaze, and the agent-runtime vendors (Modal, E2B), not other databases.
Expect a managed Vector or Lance-index surface on top of buckets to compete more directly with Turbopuffer and Pinecone, and a Python counterpart to the @tigrisdata/agent-shell TypeScript runtime to widen the agent-developer surface area.
See more alternatives to Linkerd →
See more alternatives to Tigris →