Traefik Mesh
Traefik Mesh (formerly Maesh) is a lightweight, non-invasive service mesh built on top of Traefik Proxy for Kubernetes. It provides automatic traffic management, observability, and security for microservices without requiring sidecar containers. Traefik Mesh is compliant with the Service Mesh Interface (SMI) specification and supports HTTP, TCP, and UDP traffic modes, traffic splitting, access control via TrafficTarget, rate limiting, circuit breaking, and retries. The project is effectively dormant: the last released version is v1.4.8 (2022-08-19), and commit activity since then has been limited to CI and documentation maintenance. The GitHub repository is not formally archived as of this profile date and there is no official deprecation banner on the project's README or documentation site, but the lack of feature releases for nearly four years and the absence of an SMI-compatible successor inside Traefik Labs' product line (Traefik Hub is positioned as Kubernetes-native API management, not a service mesh) make this an unmaintained project for practical purposes.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Traefik Mesh the way a machine reads it — 28 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Traefik Mesh scores 47.3/100 (developing), with a separate agent-readiness read of 32/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Traefik Mesh
Each block below is one kind of artifact we hold for Traefik Mesh. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Traefik Mesh Configuration API
Endpoints for retrieving the current dynamic Traefik configuration generated by the Traefik Mesh controller.
Traefik Mesh Status API
Endpoints for checking the readiness and status of the Traefik Mesh controller and proxy nodes.
Traefik Mesh Topology API
Endpoints for inspecting the mesh topology as seen by the controller.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Traefik Mesh Controller API
OPEN COLLECTIONFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Non-Invasive Service Mesh
No sidecar containers required; uses per-node Traefik Proxy instances.
SMI Compliance
Full support for Service Mesh Interface (SMI) specification including TrafficSplit, TrafficTarget, HTTPRouteGroup, and TCPRoute.
HTTP Traffic Management
Retry, circuit breaking, rate limiting, and traffic splitting for HTTP services.
TCP and UDP Support
Transparent proxy support for TCP and UDP traffic in addition to HTTP.
Access Control List (ACL) Mode
All traffic forbidden by default unless explicitly allowed via SMI TrafficTarget resources.
Traffic Splitting
Route traffic subsets to different service versions using SMI TrafficSplit.
Kubernetes Annotations
Configure mesh behavior per service via Kubernetes annotations.
Helm Installation
Easy deployment and configuration via official Helm chart.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Traefik Mesh Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Traefik Mesh API Rules
SPECTRALTraefik Mesh API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Traefik Mesh Pod Info
JSON SCHEMATraefik Mesh Service Entry
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Traefik Mesh Pod Info Structure
JSON STRUCTUREExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Canary Deployments
Gradually shift traffic to new service versions using SMI TrafficSplit.
Service-to-Service Access Control
Enforce zero-trust networking with SMI TrafficTarget ACL mode.
Observability
Inspect live mesh configuration, topology, and node readiness via controller API.
Microservices Traffic Management
Apply retries, circuit breakers, and rate limits without changing application code.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Traefik Proxy
Uses Traefik Proxy as the data plane proxy on each Kubernetes node.
Kubernetes
Native Kubernetes integration via Custom Resource Definitions and annotations.
SMI Spec
Implements Service Mesh Interface specification for interoperability.
Resources
Every other property we hold for Traefik Mesh — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/traefik-mesh · machine-readable index on apis.io