Public evidence onlyLast checked 16 October 2026 with AI-assisted research. Editor: Akshay Dubey.MethodologyCorrections log

In short: Solo.io (independent; venture-backed; founded 2017) and Traefik Labs (independent; venture-backed; founded 2016) both publish documentation for 7 of the 21 NHI capabilities we track. The public evidence differs on 7: evidence for Solo.io only on NHI discovery, NHI inventory, attribution to humans, secrets management, API keys and OAuth apps and tokens; evidence for Traefik Labs only on certificate management. Records checked 16 October 2026. This is a reading of what each company has published, not a score or a recommendation.

This page puts two company records side by side. It shows what public evidence establishes for each, using the same labels as the profiles. It gives no score, no ranking and no recommendation. Read the full records for sources: Solo.io (agentgateway) and Traefik Labs.

Company facts

Scroll sideways to see all columns.

FactSolo.ioTraefik Labs
Record nameSolo.io (agentgateway)Traefik Labs
OwnershipIndependentIndependent
StageVenture-backedVenture-backed
Founded2017 (Publicly disclosed)2016, by Emile Vauge (Verified)
HeadquartersRemote-first; mailing address in Boston, Massachusetts, USA (company about page). TechCrunch reported Cambridge, Massachusetts in 2021 (Verified)Not publicly disclosed (company releases in 2024 and 2026 are mostly datelined San Francisco) (Not publicly disclosed)
Total funding$175M total per the company about page ($171.5M stated in the October 2021 release); $135M Series C at a $1B valuation led by Altimeter Capital (Verified)Just over $11M in total, as reported by TechCrunch in May 2023 (Publicly disclosed)
Categories in our directoryAI agent gateway, Service mesh, Open-source agent data planeAPI, AI and MCP gateway, Open-source cloud-native proxy
Record verified2026-10-162026-10-16

Why these two are compared

Each record lists the other as a direct competitor in our analysis of product scope.

  • The Solo.io record describes Traefik Labs as: gateway vendor extending to AI and MCP traffic.
  • The Traefik Labs record describes Solo.io as: gateway for agent and MCP traffic.

Capability evidence, side by side

Documented by vendor means the company's own documentation describes the capability. It is not independent verification and says nothing about depth. Not publicly verified means we did not find public documentation. It does not mean the product lacks the capability.

Scroll sideways to see all columns.

CapabilitySolo.ioTraefik Labs
NHI discovery Documented by vendor Not publicly verified
NHI inventory Documented by vendor Not publicly verified
Ownership assignment Not publicly verified Not publicly verified
Attribution to humans Documented by vendor Not publicly verified
Access analysis Not publicly verified Not publicly verified
Authorization policy Documented by vendor Documented by vendor
Least privilege Documented by vendor Documented by vendor
Lifecycle management Not publicly verified Not publicly verified
Credential rotation Not publicly verified Not publicly verified
Secrets management Documented by vendor Not publicly verified
Certificate management Not publicly verified Documented by vendor
Service accounts Not publicly verified Not publicly verified
API keys Documented by vendor Not publicly verified
OAuth apps and tokens Documented by vendor Not publicly verified
Workload identity Documented by vendor Documented by vendor
Cloud identity Not publicly verified Not publicly verified
AI agents Documented by vendor Documented by vendor
Agent governance Documented by vendor Documented by vendor
Monitoring and detection Documented by vendor Documented by vendor
Remediation Not publicly verified Not publicly verified
Audit evidence Documented by vendor Documented by vendor

Where the public evidence differs

  • Public evidence found for Solo.io and not for Traefik Labs: NHI discovery, NHI inventory, Attribution to humans, Secrets management, API keys, OAuth apps and tokens.
  • Public evidence found for Traefik Labs and not for Solo.io: Certificate management.
  • Public evidence found for both: Authorization policy, Least privilege, Workload identity, AI agents, Agent governance, Monitoring and detection, Audit evidence.
  • Not established for either from public sources: Ownership assignment, Access analysis, Lifecycle management, Credential rotation, Service accounts, Cloud identity, Remediation.

A difference in this list is a difference in what each company has published, as read by us on the verification dates above. It is not a count of features and should not be read as a score. Confirm any capability that matters to you with the vendor and in a proof of concept.

Recent developments

Solo.io

  • 10 September 2026: Standalone mode announced for Solo Enterprise for agentgateway. The commercial distribution can run as one binary or container outside Kubernetes, with token exchange and tool access policy. [source]
  • 3 September 2026: agentdesktop announced as an open-source project. A desktop governance layer that discovers local agent tools, models and MCP servers and applies central policy. [source]
  • 4 June 2026: agentgateway becomes an Agentic AI Foundation hosted project. The foundation, part of the Linux Foundation, reported more than 300 active contributors from over 60 organisations. [source]

Traefik Labs

  • 15 September 2026: Sovereign Trust Plane announced for agent governance evidence. Traefik Hub gains delegated access based on the IETF ID-JAG draft, AuthZEN policy integration and decision records in a transparency log. General availability was scheduled for 30 September 2026. [source]
  • 30 July 2026: Distro Zero announced in early access. A single hardened binary with FIPS 140-3 validated cryptography, with gateway features unlocked by licence. [source]
  • 9 July 2026: Traefik passes 1,000 contributors. The founder also reported 3.5 billion pulls of the official Docker image. [source]

Positioning

Solo.io

What the company says: Solo.io describes agentgateway as a gateway built for AI agents that understands sessions, context and agent protocols, with agent identity, tool-level access control and audit trails built in. [source]

Our analysis: Solo.io addresses the runtime side of the NHI problem for agents. Its documented products authenticate agents and tools at a proxy, exchange tokens so that requests carry an identity instead of a shared key, apply per-tool policy and trace the calls. Ownership and lifecycle of those identities are not its documented focus.

Traefik Labs

What the company says: Traefik Labs says Traefik Hub governs API, AI model and MCP traffic in one runtime, which it calls the Triple Gate architecture. [source]

Our analysis: Traefik addresses runtime authorization for agents, not identity inventory. Its MCP Gateway decides whether an agent, identified by token claims, may call a tool for a given task and transaction. It records each decision. It depends on an external identity provider to issue the agent's identity.

Common questions

What is the difference between Solo.io and Traefik Labs?

Solo.io addresses the runtime side of the NHI problem for agents. Its documented products authenticate agents and tools at a proxy, exchange tokens so that requests carry an identity instead of a shared key, apply per-tool policy and trace the calls. Ownership and lifecycle of those identities are not its documented focus. Traefik addresses runtime authorization for agents, not identity inventory. Its MCP Gateway decides whether an agent, identified by token claims, may call a tool for a given task and transaction. It records each decision. It depends on an external identity provider to issue the agent's identity. In published documentation, public evidence was found for Solo.io and not for Traefik Labs on NHI discovery, NHI inventory, attribution to humans, secrets management, API keys and OAuth apps and tokens; for Traefik Labs and not for Solo.io on certificate management. That is a difference in what each company has published, not a feature count or a ranking.

Who owns Solo.io and Traefik Labs?

Solo.io: Independent. Traefik Labs: Independent. Ownership is taken from company announcements and filings and is dated on each record.

Do Solo.io and Traefik Labs support AI agents?

AI agents: Solo.io, documented by vendor; Traefik Labs, documented by vendor. Agent governance: Solo.io, documented by vendor; Traefik Labs, documented by vendor.

Which is better, Solo.io or Traefik Labs?

We do not rank or recommend either company, and no company pays for coverage. The better fit depends on which identity types you need covered, where your credentials live, and what evidence your auditors expect. Put the questions on this page to both vendors and confirm the capabilities that matter in a proof of concept.

What are the alternatives to Solo.io and Traefik Labs?

Other companies in the same categories of our directory, listed alphabetically and not ranked: Kong, MintMCP (now Mintive), Obot AI, Runlayer and TrueFoundry. Each has a sourced record on this site.

Questions to put to both

  • Which identity types are discovered without an agent or manual import, and which need configuration?
  • How is a named human owner assigned to each non-human identity, and what happens when that person leaves?
  • What evidence can be exported for an audit, and in what format?
  • Which capabilities are generally available today, and which are in preview?
  • Who owns the company today, and what has been said about the product roadmap since any change of ownership?

See the methodology for how records are researched, and the list of all comparisons.

Monthly change log

Know when the NHI landscape changes.

One email a month from this reference: new deals, standards status changes and corrections. No sponsored content. Unsubscribe from any email.

We first email you a link to confirm. Privacy policy.