Elasticsearch vs Tigris
Side-by-side trajectory, velocity, and editorial themes.
Elastic ships a coordinated wave of Kibana CVE patches alongside steady Rally tooling work.
Elastic's recent feed is dominated by a single-day cluster of Kibana security advisories (ESA-2026-32 through 40): SSRF, denial-of-service, privilege-escalation, and stored-injection fixes spanning the 8.19, 9.2, 9.3, and 9.4 branches. The only feature-bearing release is Rally 2.13.0, the benchmarking harness.
This is security-hardening mode. A large, synchronized advisory drop points to an internal audit or coordinated-disclosure cycle rather than feature momentum. Rally aside, the product surface is being patched, not expanded.
Expect follow-on point releases (9.4.x, 8.19.x) consolidating these fixes and a return to feature changelogs once the advisory backlog clears. Watch whether more ESA numbers in this sequence surface.
Tigris is building the storage layer for AI agents — forks, snapshots, sandboxes, now a provider-agnostic SDK.
Tigris has assembled a coherent stack for agent-shaped object storage. The latest release, storagesdk.dev, is a provider-agnostic Node.js SDK exposing Tigris's snapshot and fork primitives across S3, R2, Azure, GCS, and Tigris itself. Kefka is a Go userspace shell sandbox built on copy-on-write Tigris bucket forks. Lifecycle policies now support multiple rules per bucket with prefix filters. Embedded agent-shell on the homepage and case studies (Basic Memory, the Immutable Agent reference) tell the story end-to-end.
Tigris is staking its product position on a single thesis: AI agents need storage with forks, snapshots, and disposable workspaces, not just a bigger S3. The provider-agnostic SDK signals confidence — rather than lock customers in, they're offering an abstraction that runs against the competition while making their differentiated primitives the path of least resistance. Everything else (Kefka, agent-shell, Agent Kit) is execution against the same thesis in different languages.
Expect more agent-storage primitives — likely persistent agent-memory APIs, multi-agent coordination, and additional language SDKs filling in around Kefka and agent-shell. Tigris looks set to lean into ecosystem and education rather than head-on AWS competition on raw storage.
See more alternatives to Elasticsearch →
See more alternatives to Tigris →