Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Ocelot

github.com

  • Free plan
  • API
  • Self-hosted
6.6 Club score Visit github.com

What Ocelot is

Ocelot is a free, MIT-licensed .NET API gateway for microservices that need a shared entry point. It handles HTTP and HTTPS services supported by ASP.NET Core and also supports WebSocket and secure WebSocket connections. Developers install it as a NuGet package in an ASP.NET Core project, configure static or dynamic routes, and deploy the result as a self-hosted application. Gateway capabilities include caching, request aggregation, authentication, load balancing, rate limiting, logging, and request or response transformations. Service discovery providers documented for Ocelot include Consul, Kubernetes, Eureka, and Azure Service Fabric. Routes can use registered ASP.NET Core authentication schemes, including JWT bearer tokens, and restrict access by scope. Documentation includes Auth0, Okta, and IdentityServer bearer-token examples. Ocelot targets .NET 8, .NET 9, and .NET 10. It does not directly support GraphQL and points developers to GraphQL for .NET for integration. The repository reports no SECURITY.md file and no published security advisories.

Who it suits

Ocelot suits developers building self-hosted ASP.NET Core gateways for microservices. It is useful when routing, authentication, discovery, rate limiting, and protocol support are needed in one gateway.

Good to know, and what to watch

  • Free MIT-licensed open source
  • Static and dynamic routing
  • Multiple service discovery providers
  • JWT and ASP.NET authentication schemes
  • Supports WebSocket and secure WebSocket
  • No direct GraphQL support
  • Self-hosted deployment required
  • Repository has no SECURITY.md file
  • No published security advisories

Ocelot

Free

Open source

The verdict

Ocelot provides a broad gateway feature set for ASP.NET Core microservices, including routing, discovery, authentication, and traffic controls. Teams needing GraphQL must add another integration, and deployment remains self-managed.

What the maker publishes

Authentication
Routes can use registered authentication schemes, including JWT bearer schemes, and can restrict access by scopes. source
Deployment
Ocelot is configured and deployed as an ASP.NET Core application, and the documentation includes multiple-instance, Consul, and Service Fabric configurations. source
Gateway features
Listed features include caching, request aggregation, authentication, load balancing, rate limiting, logging, and request and response transformations. source
GraphQL limit
The project says it does not directly support GraphQL and points developers to the GraphQL for .NET library for integration. source
HTTP support
It works with HTTP(S) services on platforms supported by ASP.NET Core. source
Integrations
The authentication documentation includes examples for Auth0 and Okta, and describes using IdentityServer bearer tokens. source
License
The GitHub repository identifies the project license as MIT. source
Purpose
Ocelot is a .NET API gateway for microservices architectures that need a unified point of entry. source
Routing
Its primary features include configuration and routing, with support for static and dynamic routes. source
Runtime
Ocelot targets .NET 8, .NET 9, and .NET 10 and is installed as a NuGet package in an ASP.NET Core project. source
Security policy
The GitHub repository reports that it has not set up a SECURITY.md file and has no published security advisories. source
Service discovery
Documented service discovery providers include Consul, Kubernetes, Eureka, and Azure Service Fabric. source
WebSockets
The documentation lists WebSockets, including secure WebSockets, as supported features. source

Checked against the maker's pages on 9 Oct 2026.