Router documentation
The Stella Ops Router is a gateway and a microservice SDK for .NET. Your services connect out to the gateway over TCP, TLS, RabbitMQ or a message queue, so they need no inbound port, load balancer entry or service discovery. Each service declares its endpoints in code and gets routing, claims-based authorization, rate limiting, request schema validation, and one OpenAPI document for all services.
Who it is for: .NET teams that run many services, often on hosts without Kubernetes, and want one authenticated HTTP entry point without opening ports on every service host.
How it differs
- From YARP and Ocelot: those are ASP.NET Core proxies that connect to backend addresses you configure; Router services connect to the gateway and announce their own endpoints.
- From Envoy and Kong: those are proxies configured by files or APIs; the Router is built for .NET services and takes its routes and claims from their code.
- From Dapr service invocation: Dapr runs a sidecar next to each service, which listens on a port; the Router needs no sidecar and no listening port on the service.
The comparison, dated and sourced, covers YARP, Ocelot, Envoy, Kong Gateway, Dapr, gRPC with Istio, MassTransit and NServiceBus.
These guides are for teams that install the Router packages from NuGet and build their own gateway and services. Every C# code block on these pages is part of a sample project that is compiled and run end to end before each release.
Reading paths
| Goal | Read in this order |
|---|---|
| A first service, on one machine | Add Router to your project, Getting started, Microservice SDK |
| Production | Router overview, Transports, Security, Router gateway host, Deployment, Configuration reference |
| Moving an existing ASP.NET Core API behind the gateway | ASP.NET Core bridge, Scenario: an existing API, Security |
Concepts and first steps
- Router overview: the gateway, microservices, transports and their two halves, endpoints and claims, instances, regions and weights, request and response bodies, timeouts, cancellation and heartbeats.
- Getting started: a gateway and a service from the NuGet feed, run and called in about fifteen minutes.
- Add Router to your project: the feed, the packages for each project, one pinned version for the line, a lock file, a signature check and the offline archive.
- Router packages: which package each project needs, by role, and its licence.
- Router features: routing, versions, instances and health, timeouts, rate limits, claims, TLS, size limits, schema and OpenAPI, telemetry, deployment and testing, each with an example, its configuration, cases and pitfalls.
- Unique features: what works differently from a reverse proxy, such as services that connect out, endpoints declared in code and the identity envelope.
- Comparison: the Router next to YARP, Ocelot, Envoy, Kong Gateway, Dapr, gRPC with Istio, MassTransit and NServiceBus, as of 2026-11-08.
Building services
- Microservice SDK: typed, input-free and raw endpoints, registration options,
microservice.yaml, endpoint claims, timeouts, and the source generator with its diagnosticsSTELLA001toSTELLA006. - ASP.NET Core bridge: publish the endpoints of an existing ASP.NET Core application, and what such an endpoint sees of the caller.
- Schema validation and OpenAPI: request validation with JSON Schema, and the gateway’s OpenAPI document.
- Rate limiting: limits at the gateway and inside an endpoint.
Running the gateway
- Router gateway host: the .NET tool and a custom host, authentication and the licence monitor.
- Gateway HTTP API: health, metrics, the OpenAPI document, and the instance, Endpoint, routing-weight and resync requests, with their answers.
- Transports: choosing and configuring TCP, TLS with mTLS and pinning, UDP, RabbitMQ, Messaging over Valkey and InMemory.
- Security: tokens, claims, transport security, the insecure-transport switch, the caller’s identity in a service, and a hardening checklist.
- Configuration reference: every gateway, transport and service option, with defaults, in JSON, YAML and environment-variable form.
- Deployment: the .NET tool, systemd, a Windows service, a container, health and metrics.
Scenarios
Each scenario is a complete worked example with a sample:
- Several instances and regions
- File uploads and downloads
- Long requests and cancellation
- An existing ASP.NET Core API behind the gateway
- Testing with the in-memory harness
- Running behind a reverse proxy
When something goes wrong
- Troubleshooting: symptoms, causes and fixes, by start-up, connection, request and diagnostic id.
- Upgrading: moving a solution to a new Router release.
.NET API reference
- Router .NET API reference: the public types and members of every Router package, with their C# signatures and descriptions.
Licence
- Router licence: what is free, what counts as an Endpoint, the notice level, the licence monitor, and a plain-terms FAQ.
