Tigera has made Lynx generally available, positioning it as a Kubernetes-native control plane for discovering, identifying, authorizing, governing, and auditing AI agents without requiring changes to agent code.
Tigera launched Lynx as a generally available control plane for Kubernetes-native AI agents, according to a company announcement distributed by Newswire.ca.
Tigera describes Lynx as a unified control plane intended to help AI, platform, security, and compliance teams discover, authenticate, authorize, govern, and audit AI agents running in Kubernetes environments. The Newswire.ca release says Lynx is designed to do this without requiring changes to existing agent code.
The company’s Lynx product page similarly presents the product as a control plane for AI agent discovery, identity, authorization, and runtime enforcement. Tigera’s materials focus on agents that interact with other agents, Model Context Protocol tools, external tools, and large language models.
In a Lynx one-pager published by Tigera, the company describes a “Lynx Gateway” that sits in the path of traffic between AI agents and the systems they use. The one-pager says this includes agent-to-agent, agent-to-MCP/tool, and agent-to-LLM traffic.
According to Tigera’s product page, Lynx is intended to provide identity-aware control and runtime enforcement for these interactions. Tigera says the product can help teams understand which agents exist, what they are allowed to access, and how they behave while operating in Kubernetes-based environments.
The Newswire.ca announcement frames Lynx as a product for multiple internal teams rather than only security teams. Tigera names AI, platform, security, and compliance groups as target users, reflecting the operational and governance concerns that can arise when agentic applications begin calling tools, services, and models autonomously.
The launch comes as organizations experiment with AI agents that can take actions across software systems, retrieve context from tools, and coordinate with other agents. Tigera’s source documents do not make broad market claims, but they do emphasize a specific operational challenge: teams need visibility and control over agent activity once those agents are deployed in Kubernetes.
Tigera’s announcement says Lynx is now generally available. Its published materials position the product around several related functions: discovery, authentication, authorization, governance, auditing, and runtime enforcement. Together, those features suggest Tigera is targeting enterprises that want to apply policy and observability to AI agent traffic without rebuilding the agents themselves.
The company’s public materials describe Lynx at a product and architecture level, but they do not provide independent performance benchmarks or customer deployment details in the cited sources. Buyers evaluating the product will likely need to assess how Lynx integrates with their existing Kubernetes networking, identity, policy, and monitoring practices.
For now, the core news is straightforward: Tigera has moved Lynx to general availability and is marketing it as a Kubernetes-native control plane for governing AI agents and their runtime interactions.
Tigera launched Lynx as a generally available control plane for Kubernetes native AI agents, according to a company announcement distributed by Newswire.ca.
The Newswire.ca release says Lynx is designed to do this without requiring changes to existing agent code.
The company’s Lynx product page similarly presents the product as a control plane for AI agent discovery, identity, authorization, and runtime enforcement.
Continue reading
