> This page is for NeMo Fabric, version dev.
> For other versions, use one of these documentation indexes:
> - Latest (v0.7.0) (default): https://docs.nvidia.com/nemo/fabric/latest/llms.txt
> - dev: https://docs.nvidia.com/nemo/fabric/dev/llms.txt
> - v0.7.0: https://docs.nvidia.com/nemo/fabric/v0.7.0/llms.txt
> - v0.6.1: https://docs.nvidia.com/nemo/fabric/v0.6.1/llms.txt
> - v0.6.0: https://docs.nvidia.com/nemo/fabric/v0.6.0/llms.txt
> - v0.5.0: https://docs.nvidia.com/nemo/fabric/v0.5.0/llms.txt
> - v0.4.0: https://docs.nvidia.com/nemo/fabric/v0.4.0/llms.txt
> - v0.3.0: https://docs.nvidia.com/nemo/fabric/v0.3.0/llms.txt
> - v0.2.0: https://docs.nvidia.com/nemo/fabric/v0.2.0/llms.txt
> - v0.1.1: https://docs.nvidia.com/nemo/fabric/v0.1.1/llms.txt
> - v0.1.0: https://docs.nvidia.com/nemo/fabric/v0.1.0/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/fabric/llms.txt.

# Architecture Overview for NVIDIA NeMo Fabric

> Understand the components and execution flow that connect applications to agent harnesses through NeMo Fabric.

NVIDIA NeMo Fabric uses a Python SDK backed by a Rust core to validate configuration and coordinate execution through harness adapters and environment providers. Applications supply tasks and use the results; each harness retains its own agent logic and tools.

The following diagram shows how applications, evaluation systems, and rollout platforms use NeMo Fabric to run harnesses and receive execution evidence.

![Applications, evaluation systems, and rollout platforms send FabricConfig through the Python SDK to the Rust core, which normalizes configuration, runs harness adapters, and returns RunResult; optional NeMo Relay captures telemetry.](/nemo/fabric/_fern-files/nvidia-nemo-fabric.docs.buildwithfern.com/7adaa91e527369f5ff4d06125271560010c192caa68ca7eb03e5ef9b5e0da307/assets/fabric-hero-docs.svg)

## Components

The components divide responsibility as follows:

| Component                | Role in a Run                                                                                                                                                                                |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Application or evaluator | Defines the task, chooses the harness, submits requests, and uses the results. Owns scheduling, concurrency limits, retries, scoring, and recovery.                                          |
| NeMo Fabric              | Validates configuration and coordinates execution through the harness adapter and environment provider. Returns normalized results and execution evidence.                                   |
| Environment provider     | Creates or connects to the environment where the harness runs. Providers such as OpenShell supply sandbox isolation and policy enforcement.                                                  |
| Harness adapter          | Implements the NeMo Fabric adapter contract for a specific harness. Translates NeMo Fabric configuration and execution requests into native harness operations, then normalizes the results. |
| Harness or custom agent  | Performs the task using its own agent logic, tools, and execution behavior.                                                                                                                  |
| NeMo Relay, when enabled | Instruments supported harness execution and routes telemetry to configured destinations.                                                                                                     |

## Data Flow

For example, an application asks an agent to review a code change:

1. Your application submits the task by sending the review request with its selected harness, model, and workspace settings.
2. NeMo Fabric validates the settings and starts the harness through its adapter.
3. The harness performs the review using its own agent logic and tools.
4. The adapter maps the outcome into a normalized result.
5. NeMo Fabric returns the review output or failure details, plus available artifact and telemetry references.

For a single-request run, NeMo Fabric also attempts runtime cleanup before returning.

## Related Topics

Use these guides to explore configuration, runtime ownership, and integration contracts:

* [Key Features](/nemo/fabric/dev/about-nemo-fabric/key-features)
* [Execution Model](/nemo/fabric/dev/sdk/execution-model)
* [Environments and Shared Services](/nemo/fabric/dev/sdk/environments-and-shared-services)
* [Adapter Contract](/nemo/fabric/dev/adapter-contract/overview)