The standalone distribution of NVIDIA Omniverse's omni.ui UI framework, extracted to run independently outside of Kit. It provides a declarative, Python-first API for building hardware-accelerated desktop interfaces backed by ImGui.
52
stars
3
commits
Python
primary language
Sep 3, 2026
updated
ovui is a standalone Python UI toolkit for building native scene, viewport, and data applications, exposing the Omniverse UI framework through the familiar omni.ui (windows, layout, value models, widgets) and omni.ui_scene (SceneView, gestures, manipulators) Python APIs over a native C++ core. It loads and edits OpenUSD stages, presents rendered viewports from an external renderer such as ovrtx, runs headlessly for automation, and can be inspected by AI agents through a screenshot-first loop. Its defining trait is that it runs standalone — no Omniverse Kit installation required.
ovui is a disaggregated piece of the Omniverse platform: the omni.ui UI framework decoupled from the Kit extension system and shipped as an independently installable library, available as a peer to the other ov libraries (ovrtx, ovgraph, ovphysx, and more). It pairs the native runtime with ovui-widgets (production-shaped scene widgets) and ovui-data-adapters (a backend boundary for OpenUSD and custom data sources), keeping the UI layer cleanly separate from the data layer so teams can build tools against their own backends.
ovui is pre-release software and is not enterprise-supported.
What you can do with it:
omni.ui.omni.ui_scene.SelectionBus, UndoManager, Settings, and recent-files services from ovui-widgets.StageAdapter, PropertyAdapter, TransformAdapter, RendererAdapter) to wire widgets to OpenUSD or your own data source; OpenUSD + ovrtx implementations are included.AGENTS.md and task-level skills (atomic UI APIs, widget composition, styling, screenshot-first inspection) so agents work from real patterns instead of inventing UI code.ovui, ovui-widgets-*, ovui-data-adapters-*) that share one version, so you take only what you need.Who benefits:
omni.ui / omni.ui_scene APIs you already know, now available standalone.build-essential on Linux; Vulkan headers + loader for the optional Vulkan backendpxr) Python bindings — from its standalone extra or the environment — while the native OVStage provider uses the external native OVStage runtime and needs no OpenUSD bindingsTHIRD_PARTY_NOTICES.md) before use.Note: ovui is pre-release Early Access software and is not enterprise-supported. APIs may change before the 1.0 release. The rendered viewport requires a separate ovrtx renderer install; the UI framework, widgets, and headless paths work without it.
ovui · standalone distribution of Omniverse's omni.ui UI framework · Copyright (c) 2025 NVIDIA Corporation.
2 commits
1 commits
Python
78.5%
C++
18.0%
C
2.9%
The standalone distribution of NVIDIA Omniverse's omni.ui UI framework, extracted to run independently outside of Kit. It provides a declarative, Python-first API for building hardware-accelerated desktop interfaces backed by ImGui.
52
stars
3
commits
Python
primary language
Sep 3, 2026
updated
ovui is a standalone Python UI toolkit for building native scene, viewport, and data applications, exposing the Omniverse UI framework through the familiar omni.ui (windows, layout, value models, widgets) and omni.ui_scene (SceneView, gestures, manipulators) Python APIs over a native C++ core. It loads and edits OpenUSD stages, presents rendered viewports from an external renderer such as ovrtx, runs headlessly for automation, and can be inspected by AI agents through a screenshot-first loop. Its defining trait is that it runs standalone — no Omniverse Kit installation required.
ovui is a disaggregated piece of the Omniverse platform: the omni.ui UI framework decoupled from the Kit extension system and shipped as an independently installable library, available as a peer to the other ov libraries (ovrtx, ovgraph, ovphysx, and more). It pairs the native runtime with ovui-widgets (production-shaped scene widgets) and ovui-data-adapters (a backend boundary for OpenUSD and custom data sources), keeping the UI layer cleanly separate from the data layer so teams can build tools against their own backends.
ovui is pre-release software and is not enterprise-supported.
What you can do with it:
omni.ui.omni.ui_scene.SelectionBus, UndoManager, Settings, and recent-files services from ovui-widgets.StageAdapter, PropertyAdapter, TransformAdapter, RendererAdapter) to wire widgets to OpenUSD or your own data source; OpenUSD + ovrtx implementations are included.AGENTS.md and task-level skills (atomic UI APIs, widget composition, styling, screenshot-first inspection) so agents work from real patterns instead of inventing UI code.ovui, ovui-widgets-*, ovui-data-adapters-*) that share one version, so you take only what you need.Who benefits:
omni.ui / omni.ui_scene APIs you already know, now available standalone.build-essential on Linux; Vulkan headers + loader for the optional Vulkan backendpxr) Python bindings — from its standalone extra or the environment — while the native OVStage provider uses the external native OVStage runtime and needs no OpenUSD bindingsTHIRD_PARTY_NOTICES.md) before use.Note: ovui is pre-release Early Access software and is not enterprise-supported. APIs may change before the 1.0 release. The rendered viewport requires a separate ovrtx renderer install; the UI framework, widgets, and headless paths work without it.
ovui · standalone distribution of Omniverse's omni.ui UI framework · Copyright (c) 2025 NVIDIA Corporation.
2 commits
1 commits
Python
78.5%
C++
18.0%
C
2.9%