What NVIDIA Holoscan does
NVIDIA Holoscan is a set of software and hardware for processing streaming sensor data with AI in real time, close to where the data is produced. A Holoscan application takes a continuous feed, such as video from an endoscope, frames from an inspection camera or echoes from an ultrasound probe, and runs it through capture, pre-processing, AI inference and display or control with as little delay as possible.
It began as Clara Holoscan, aimed at medical devices, and NVIDIA has since widened it to robotics, industrial inspection, scientific instruments and broadcast. The common thread is latency. In a surgical display or a reject gate on a production line, a result that arrives a few frames late is not useful, so Holoscan is designed to keep data on the GPU and move it between processing stages without unnecessary copies.
Holoscan is not a camera or a single product. It is a development framework plus reference hardware, and an application written with it can run on several classes of NVIDIA system.
The parts of the Holoscan platform
NVIDIA uses the Holoscan name for several related pieces. Most projects use the SDK; the Sensor Bridge and IGX hardware are added when the system needs them.
-
//
Holoscan SDK. An open-source framework, released under the Apache 2.0 license, for building streaming pipelines in C++ or Python. Applications are graphs of operators, with schedulers that run them in parallel and tools to measure latency at each stage.
-
//
Holoscan Sensor Bridge. An FPGA-based board design that packetises camera or sensor data and sends it over Ethernet, using RDMA to write it straight into GPU memory. It suits sensors spread around a machine or too fast for local capture.
-
//
HoloHub. NVIDIA’s public collection of reference applications and reusable operators, from endoscopy tool tracking to ultrasound segmentation and video streaming.
-
//
Reference hardware. NVIDIA IGX, an industrial and medical system with functional safety features and long-term support, plus Jetson AGX Orin, Jetson Thor and x86 workstations or servers with RTX or data centre GPUs.
-
//
Holoscan for Media. A separate, related product for live broadcast production over IP networks, built on the same idea of software-defined, GPU-accelerated processing.
How a Holoscan pipeline works
A Holoscan application is built from operators, each doing one job, connected into a graph. A typical vision pipeline has a source operator that receives frames, a format converter that resizes and normalises them, an inference operator that runs a TensorRT or ONNX model, a post-processing step that turns the output into boxes, masks or measurements, and a visualiser or output operator that draws an overlay or sends a result to a controller.
The SDK handles the plumbing between them. Data stays in GPU memory as tensors where possible, operators run in parallel on a multi-threaded or event-based scheduler, and a large application can be split into fragments running on more than one computer. Built-in data-flow tracking reports the latency of every path, which is often the figure a medical or safety review asks for.
Ways to bring sensor data into Holoscan
Holoscan works with ordinary capture paths as well as its own Sensor Bridge. The right choice depends on how far the sensors are from the computer and how much latency the application can tolerate.
| Ingest path | How data arrives | Typical distance | CPU involvement | Typical sources |
|---|---|---|---|---|
| USB or standard Linux video device | Frames read through the operating system | A few meters | CPU copies each frame | USB cameras, test setups |
| MIPI CSI-2 or GMSL camera | Direct into a Jetson module’s camera inputs | Around 30 cm (CSI-2) to 15 m (GMSL) | Low; the ISP handles raw data | Robot and vehicle cameras |
| PCIe capture card | SDI or HDMI into a card, then GPUDirect where supported | Card in the computer; SDI cable runs of around 100 m | Low with GPUDirect | Endoscopes, broadcast, medical imaging |
| Holoscan Sensor Bridge | Sensor data over 10GbE or faster, by RDMA into GPU memory | Tens of meters on copper, further on fiber | Lowest | Distributed cameras, ultrasound, radar, instruments |
Our Holoscan Sensor Bridges take HDMI 2.0, 12G-SDI or GMSL2 camera sources and send them over SFP+ fiber to the processing system, so the computer can sit in a rack well away from the cameras. For local capture, SDI capture cards remain a common input, and our guide to SDI capture for edge AI covers how they feed an inference pipeline.
Where Holoscan is used
Medical imaging is still the largest use. Endoscopy, surgical video, ultrasound and robotic surgery all need AI overlays with very low delay, along with the traceability and long-term support that medical device makers require, which is why IGX was designed with them in mind. Our case study on AI medical carts with endoscopy video capture shows the hardware side of that kind of pipeline.
Outside medicine, Holoscan suits industrial inspection with several high-speed cameras, robotics that fuse cameras with lidar or radar, and scientific instruments such as radio telescopes and particle detectors. On the hardware side, Jetson AGX Orin and Jetson Thor computers suit compact and mobile systems, while industrial GPU computers, including IGX Thor systems with an optional RTX PRO 6000 Blackwell card, handle the heaviest multi-stream pipelines.
Quick answers on NVIDIA Holoscan
NVIDIA Holoscan: common questions
Is NVIDIA Holoscan free?
The SDK is. The Holoscan SDK is open source under the Apache 2.0 license. Production support, and some IGX software, come through NVIDIA’s enterprise software subscriptions.
Does Holoscan run only on Jetson?
No. It runs on Jetson AGX Orin and Thor, on NVIDIA IGX systems and on x86 computers with supported NVIDIA GPUs, so a pipeline can be developed on a workstation and deployed at the edge.
What is the difference between the Holoscan SDK and the Sensor Bridge?
Software versus ingest hardware. The SDK builds and runs the processing pipeline. The Sensor Bridge is the hardware that streams sensor data over Ethernet into the GPU, and it is optional.
Is Holoscan only for medical devices?
No. It started in medical imaging, but the same SDK is used for robotics, industrial inspection, scientific instruments and live video.
Which programming languages does Holoscan support?
C++ and Python. Operators can be written in either and mixed in one application. Python suits development, while C++ is often used for the most latency-critical stages.
We supply our Jetson, IGX and GPU computers with the capture hardware, drivers and NVIDIA software stack fitted and validated as standard, ready for your Holoscan application.