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

# Concepts

Use these pages to understand the NeMo Relay runtime model before applying it
in a use-case workflow.

NeMo Relay's shared runtime model has five parts:

* **Scopes** decide where work belongs and which scope-local behavior is visible.
* **Middleware** decides what can block, rewrite, sanitize, or wrap managed
  execution.
* **Plugins** install reusable runtime behavior from configuration.
* **Events** record what happened in the canonical lifecycle stream.
* **Subscribers and exporters** consume that stream in process, write raw ATOF
  events, or project events into downstream formats.

Managed tool and LLM helpers are the application-owned API path through scopes,
middleware, events, and subscribers. Codecs are boundary translators that
normalize typed application values or provider-native payloads when runtime
behavior needs stable data shapes.

Use the concepts pages for runtime semantics such as ownership, ordering,
cleanup, and support boundaries. Use the generated [API Reference](/reference/api) for symbol lookup after you already know which
runtime concept or integration boundary you need.

#### [Scopes](/about-nemo-relay/concepts/scopes)

Ownership boundaries for agent runs, requests, workflows, tools, LLM calls, and nested runtime work.

#### [Middleware](/about-nemo-relay/concepts/middleware)

Guardrails and intercepts that sanitize, transform, block, or wrap tool and LLM execution.

#### [Plugins](/about-nemo-relay/concepts/plugins)

Configuration-driven bundles that install reusable middleware, subscribers, and adaptive behavior.

#### [Events](/about-nemo-relay/concepts/events)

Canonical lifecycle records for scopes, tool calls, LLM calls, marks, subscribers, and exporters.

#### [Subscribers](/about-nemo-relay/concepts/subscribers)

Consumers for lifecycle events, including logs, traces, trajectories, analytics, and diagnostics.

#### [Framework Integrations](/about-nemo-relay/concepts/framework-integrations)

Integration patterns for frameworks that own invocation boundaries, scheduling, retries, or provider payloads.

#### [Codecs](/about-nemo-relay/concepts/codecs)

Normalization boundaries for typed application values, provider payloads, middleware, and exporters.

## Docs

- [Scopes](https://docs.nvidia.com/nemo/relay/v0.5.0/about-nemo-relay/concepts/scopes.md): 
- [Middleware](https://docs.nvidia.com/nemo/relay/v0.5.0/about-nemo-relay/concepts/middleware.md): 
- [Plugins](https://docs.nvidia.com/nemo/relay/v0.5.0/about-nemo-relay/concepts/plugins.md): Understand NeMo Relay plugin configuration, lifecycle, ownership, and built-in components.
- [Events](https://docs.nvidia.com/nemo/relay/v0.5.0/about-nemo-relay/concepts/events.md): 
- [Subscribers](https://docs.nvidia.com/nemo/relay/v0.5.0/about-nemo-relay/concepts/subscribers.md): Understand NeMo Relay subscribers, delivery behavior, scope visibility, and exporter roles.
- [Framework Integrations](https://docs.nvidia.com/nemo/relay/v0.5.0/about-nemo-relay/concepts/framework-integrations.md): 
- [Codecs](https://docs.nvidia.com/nemo/relay/v0.5.0/about-nemo-relay/concepts/codecs.md):