Is this page helpful?

Platform Components#

The DSX Blueprint consists of two integrated systems that work together to deliver streaming 3D experiences:

Component

Description

Omniverse Kit Application

GPU-accelerated 3D rendering engine built on the Kit SDK

Web Portal

React frontend for user interaction and session management

How the Platform Works#

  1. The Web Portal authenticates you and manages session lifecycle.

  2. The Kit Application renders 3D USD scenes with GPU acceleration and streams video via WebRTC.

  3. You interact through your browser, with commands sent in real-time to the Kit application.

  4. The Kit application processes commands and updates the scene in real-time.

Kit Application#

Location: source/apps/

The Kit application handles GPU-accelerated 3D rendering and video streaming.

Aspect

Details

Technology

Kit SDK, RTX renderer, WebRTC

Deployment

Locally built application or packaged as containers

Purpose

Real-time 3D visualization and streaming

Web Portal Backend#

Location: backend/

The backend manages user sessions and orchestrates NVCF container lifecycle.

Aspect

Details

Technology

FastAPI, Tortoise ORM, WebSocket proxy

Deployment

Standard compute (CPU only)

Purpose

Session management, authentication, NVCF orchestration

Web Portal Frontend#

Location: web/

The frontend provides the user interface and streaming client.

Aspect

Details

Technology

React, TypeScript, NVIDIA WebRTC Streaming Library

Deployment

Static hosting (Nginx/CDN)

Purpose

User interface and video stream display

Communication Flow#

  1. User requests a session through the web portal.

  2. Backend calls the NVCF API to launch a Kit container on a GPU.

  3. Backend proxies WebSocket traffic for WebRTC signaling.

  4. Browser establishes a direct WebRTC connection to the Kit application.

  5. Video streams to the browser while commands flow through the data channel.

  6. The Kit application processes commands and updates the scene.

Key Architecture Points#

  • Separate builds: The Kit application and web portal have different build systems and deployment targets.

  • Serverless GPU: NVCF automatically scales containers based on demand.

  • Low-latency streaming: WebRTC provides bi-directional communication with minimal delay.

  • Backend proxy: Handles authentication, session lifecycle, and WebSocket forwarding.

Repository Structure#

After cloning the repository, you find the following directory structure:

Directory

Purpose

source/

Kit applications and extensions source code

web/

React frontend for the web portal

helm/

Kubernetes Helm charts for deployment

tools/

Repository-specific tooling and settings

readme-assets/

Images and documentation assets

.vscode/

VS Code configuration and helper tasks

File

Purpose

premake5.lua

Build configuration for Kit applications

repo.sh / repo.bat

Repository tool entry points (Linux/Windows)

repo.toml

Top-level configuration for repository tools

ARCHITECTURE.md

Detailed system architecture documentation

Learn More: Embedded Web Viewer#

DSX uses the Embedded Web Viewer pattern to stream the Kit application to the browser. For details on building custom streaming clients, see the resources below:

Resource

Description

Embedded Web Viewer Guide

Official documentation covering streaming, messaging, and containerization

Web Viewer Sample

Reference implementation showing front-end client streaming and custom messaging