# ThreeMammals/Ocelot

.NET API Gateway

Repository: https://github.com/ThreeMammals/Ocelot
Canonical: https://ross.abutalabs.com/products/ocelot
Homepage: https://ocelot.readthedocs.io
Language: C#
License: MIT
License Family: permissive
Topics: ocelot, dotnet, aspnetcore, gateway, microservices, reverse-proxy, api-gateway
Last push: 2026-08-26T16:50:53+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 95, longevity 100
- inputs: {"age_days": 3717, "days_push": 7, "days_rel": 35, "gap_med": 23.0, "n_releases_24m": 17}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 8716, forks 1684 (observed 2026-08-28T04:10:24.397726+00:00)

## What it is
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
- artifact type: library
- maturity: active
- function: api-gateway, proxy, routing, middleware, http-server, caching, auth, rate-limiting, load-testing
- domain: microservices, apis, backend, web-development
- platform: dotnet, cross-platform, cloud
- tags: api-gateway, reverse-proxy, aspnetcore, microservices, service-mesh, nuget, request-aggregation, service-discovery, devops, web-server, docker

## Member repositories
- ThreeMammals/Ocelot (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:24.397726+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:25:21.047402+00:00, confidence not recorded.
  - readme: https://github.com/ThreeMammals/Ocelot (fetched 2026-08-28T04:10:24.397726+00:00, sha 7f0b0166f6af)
  - homepage: https://ocelot.readthedocs.io (fetched 2026-08-29T08:25:42.366027+00:00, sha 552cb8e5f431)
- Data as of 2026-08-30T08:39:29.467469+00:00.