| Resource | URL |
|---|---|
| Switchyard repository | https://github.com/NVIDIA-NeMo/Switchyard |
| Getting started | https://github.com/NVIDIA-NeMo/Switchyard/blob/main/docs/getting_started.md |
| Core concepts | https://github.com/NVIDIA-NeMo/Switchyard/blob/main/docs/core_concepts.md |
| Routing overview | https://github.com/NVIDIA-NeMo/Switchyard/blob/main/docs/routing_algorithms/overview.md |
| Architecture | https://github.com/NVIDIA-NeMo/Switchyard/blob/main/docs/architecture.md |
| Issues | https://github.com/NVIDIA-NeMo/Switchyard/issues |
| Resource | Notes |
|---|---|
| VentureBeat coverage of Switchyard + Nemotron 3.5 Lightning | Multi-model routing, partner integrations, cost claims |
| NVIDIA NeMo Relay Switchyard plugin docs | Historical Decision API integration (deprecated path for Relay 0.8+) |
Vendor-reported numbers (e.g. ~⅓ cost vs frontier-only) are tracked in data/claims.json. Always re-measure on your workloads before external marketing.
Educational Python routers approximate upstream strategies for learning. Behavior and config field names should be verified against the pinned Switchyard version you deploy — pre-alpha APIs move.