Stella Ops Router
Stella Ops Router is an API gateway and microservice SDK for .NET. Your services connect out to the gateway and declare their endpoints in code. The gateway routes each HTTP request to the right service and handles claims-based authorization and rate limiting on the way.
Not released yet: no Router package has been published. This page describes the release that is being prepared.
Key features
- Routes come from your services
Each service declares its endpoints in code and announces them when it connects, so the gateway's routes follow your deployments without a proxy configuration to keep in step.
- A transport for every network
Services reach the gateway over TCP, TLS with client certificates or UDP, or exchange requests with it through RabbitMQ or Valkey queues.
- Token and claims checks in one place
The gateway validates JWT bearer tokens from your OpenID Connect provider and enforces the claims each endpoint requires. It removes identity headers a caller sends and, with a signing key configured, passes the caller to services in a signed identity envelope.
- Rate limits per environment, service and route
Limits per gateway instance and per environment, with rules for each service and route; environment-wide counts are shared in Valkey.
- Timeouts and cancellation
Each endpoint sets its own timeout, and when the timeout passes or the caller disconnects, the service handling the request is told to stop. Over Messaging queues this needs frame protection on both sides.
- One OpenAPI document for all services
The gateway publishes one API description covering every connected service, plus its own health, readiness and metrics endpoints.
- Existing ASP.NET Core APIs behind the gateway
An existing ASP.NET Core application joins the gateway with its handlers unchanged.
- Gateway and services in one process for tests
An in-memory harness runs the gateway and its services together, for tests and local development.
How it differs from well-known alternatives
| Product | How Stella Ops Router differs |
|---|---|
| YARP | Router services connect out to the gateway and announce their own endpoints; YARP, an ASP.NET Core proxy library, connects to backend addresses you configure. Source 1, Source 2, Details |
| Ocelot | Router endpoints are declared in service code; Ocelot routes are declared in its ocelot.json configuration file. Source, Details |
| Envoy, Kong Gateway | The Router takes routes and required claims from .NET service code; Envoy and Kong are language-neutral proxies configured by files or APIs. Source 1, Source 2, Details |
| Dapr service invocation | Router services need no sidecar and no listening port; Dapr service invocation runs a sidecar beside each service, and the service listens on a port. Source 1, Source 2, Details |
As of 2026-11-08. Each line links the public documentation it is based on. All products, the dimensions and the details: Full comparison.
Go deeper
The licence in plain words Licence and purchase options All components
