> This page is for NeMo Relay, version v0.11.0.
> For other versions, use one of these documentation indexes:
> - Latest (v0.10.4) (default): https://docs.nvidia.com/nemo/relay/latest/llms.txt
> - dev: https://docs.nvidia.com/nemo/relay/dev/llms.txt
> - v0.11.0: https://docs.nvidia.com/nemo/relay/v0.11.0/llms.txt
> - v0.10.4: https://docs.nvidia.com/nemo/relay/v0.10.4/llms.txt
> - v0.9.4: https://docs.nvidia.com/nemo/relay/v0.9.4/llms.txt
> - v0.8.4: https://docs.nvidia.com/nemo/relay/v0.8.4/llms.txt
> - v0.7.3: https://docs.nvidia.com/nemo/relay/v0.7.3/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/relay/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo/relay/_mcp/server.

# Use Plugins

> Configure plugin settings, manage installed plugins, and initialize plugins through the language SDKs.

Use this section to configure and run built-in and separately installed NeMo
Relay plugins. Choose a guide based on how you use plugins:

| Goal                                                                            | Start here                                                 |
| ------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Set plugin options in files or with `nemo-relay plugins edit`                   | [Configure](/nemo/relay/v0.11.0/configure-plugins/plugin-configuration-files) |
| Install, inspect, enable, disable, or remove a discoverable plugin with the CLI | [Manage](/nemo/relay/v0.11.0/configure-plugins/discoverable-plugins)          |
| Validate, activate, and close a plugin host through a language SDK              | [Initialize](/nemo/relay/v0.11.0/configure-plugins/initialize-plugins)        |
| Create a reusable plugin                                                        | [Build Plugins](/nemo/relay/v0.11.0/build-plugins/about)                      |

## Built-in Plugins

Relay includes these built-in components. Configure them as `[[components]]`
entries in `plugins.toml`.

* [Observability](/nemo/relay/v0.11.0/configure-plugins/observability/about) exports ATOF, ATIF,
  or typed OpenTelemetry data.
* [Adaptive](/nemo/relay/v0.11.0/configure-plugins/adaptive/about) configures adaptive runtime
  behavior.
* [NeMo Guardrails (Deprecated)](/nemo/relay/v0.11.0/configure-plugins/nemo-guardrails/about)
  installs Guardrails-backed policy checks. The built-in plugin is scheduled
  for removal in NeMo Relay 0.9 and should not be used for new deployments.
* [PII Redaction](/nemo/relay/v0.11.0/configure-plugins/pii-redaction/about) sanitizes sensitive
  data in observability payloads.
* [Model Pricing](/nemo/relay/v0.11.0/configure-plugins/model-pricing) configures catalog sources
  for cost estimates on managed or manually observed LLM responses.
* [Resource Metrics](/nemo/relay/v0.11.0/configure-plugins/resource-metrics) explains optional
  polling marks and on-demand snapshots for CPU, memory, processes, disk,
  network, and GPUs.

## First Party Plugins

First-party plugins are published separately by NVIDIA. Install and manage them
with the Relay CLI for a user account or a system-wide deployment.

* [NeMo Switchyard](/nemo/relay/v0.11.0/configure-plugins/switchyard) routes model requests across
  models and providers. The guide covers installation, configuration, a routed
  request, and removal.

Use [Build Plugins](/nemo/relay/v0.11.0/build-plugins/about) only when you are authoring the
plugin itself. It covers generic plugin components, manifests, native ABI
plugins, Python workers, and the `grpc-v1` protocol.

## Embedded Diagnostics Service

For language-hosted Relay, add a root `[diagnostics]` section to `plugins.toml`.
Initialization uses it to select a service owned by the process. The service
remains available after individual plugins close. Refer to
[Embedded Diagnostics](/nemo/relay/v0.11.0/reference/diagnostics/bindings#embedded-language-runtimes)
for configuration precedence, startup limits, and optional readers.