Most of my Jetson work happens with no monitor attached. The Orin Nano sits on a bench, or it is already inside the thing it will ship in, and the only way in is ssh. At some point I always need to actually see what the camera sees, e.g. to adjust the lighting or exposure time, or to see if the lens is focused correctly, or to align it to something. On a desktop that is trivial. On a headless Jetson this can be annoying.
The common approaches all have a catch.
The first thing everyone tries is ssh -X and a gst pipeline with an Argus display sink. It does not work the way you hope. Argus and the NVIDIA display path want an EGL surface, and a headless machine has no X buffer to give them. You get an EGL or X11 error instead of an image. Forwarding the GL context over the network is not what X forwarding is for anyway.
The second approach is x11vnc. Now you are running a real or virtual X session just so something can mirror it, editing xorg.conf with a fake Modeline so the GPU pretends a monitor exists, and redoing it after the next JetPack update changes something. That is a lot of moving parts to check on a camera.
The third approach is to spin up an RTSP server. Write the pipeline, run the server, point a player at it. It works, but now camera evaluation depends on a streaming stack you also have to keep alive, and you have added latency exactly when you are trying to judge focus and exposure by eye.
None of these are camera problems. They are display problems that only exist because the tooling assumes a screen.
When I built Videre I did not want a display path at all. There is no desktop environment, no X, no EGL surface to find. The backend does capture and processing on the Jetson, and the browser on whatever machine you are sitting at is the display. The picture travels over the network, not the GL context.
The workflow I use is to ssh into the Orin, run Videre with --no-browser --bind 0.0.0.0 --port 8080, then open the URL from your laptop. You get the live image, the histogram, ROI analysis, the overlays, and the control panel. It does not matter whether the camera is a UVC device on the V4L2 path or a CSI sensor going through libargus. Same single binary, same browser UI, no screen on the Jetson at any point.