ThreeMammals/Ocelot

Health v2 · maintenance only

Adoption not part of the score

8716 stars · 1684 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Ocelot is a .NET API gateway built as a series of ASP.NET Core middlewares, providing a unified entry point for microservices architectures. It routes HTTP(S) requests to downstream services and supports features like authentication, caching, aggregation, and service discovery on any platform ASP.NET Core supports.

Use cases

• set up an api gateway for .net microservices
• unify multiple microservices behind a single entry point
• reverse proxy http requests to downstream services in asp.net core
• aggregate responses from multiple services into one endpoint
• add authentication and jwt bearer token handling at the gateway
• route and rewrite requests with configuration-based rules
• integrate service discovery with consul or service fabric

When to choose

• you have a .NET/ASP.NET Core microservices system needing a unified gateway
• you want configuration-driven routing, aggregation, and middleware in C#
• you need IdentityServer/JWT integration at the gateway level
• you want a lightweight alternative to Kong or Traefik within the .NET ecosystem

When to avoid

• your stack is not .NET and you don't want to host ASP.NET Core
• you need a standalone gateway appliance with a full admin UI out of the box
• you need non-HTTP protocols like gRPC or TCP passthrough

Facets

library · maturity active

api-gateway proxy routing middleware http-server caching auth rate-limiting load-testing microservices apis backend web-development dotnet cross-platform cloud api-gateway reverse-proxy aspnetcore microservices service-mesh nuget request-aggregation service-discovery devops web-server docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="ThreeMammals/Ocelot")