Vercel vs Tigris
Side-by-side trajectory, velocity, and editorial themes.
Vercel trials flat-rate CDN pricing and lines up its sandbox as the runtime for managed AI agents.
Vercel opened a Limited Beta of Flat Rate CDN for Pro teams — fixed monthly fee instead of usage-based bandwidth — and shipped a Claude Managed Agents integration for Vercel Sandbox in the same week. AI Gateway gained Gemini 3.5 Flash and provider sorting by cost, latency, or throughput. Around that, Firewall-mitigated traffic became free, monorepos got consolidated GitHub commit statuses, and Trusted Sources brought OIDC to deployment protection.
Two strategic moves are visible: a hedge against the usage-pricing backlash (Flat Rate CDN, free firewall-mitigated traffic) and a serious bid to host AI agent workloads (Sandbox + Claude Managed Agents, AI Gateway provider routing controls). Developer-experience polish continues underneath — natural-language WAF rules, native curl in CLI, protected source maps.
Expect Flat Rate to widen from CDN to compute and ISR cache once the beta closes, and Vercel Sandbox to gain integrations with at least one more major agent runtime beyond Claude.
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 Vercel →
See more alternatives to Tigris →