What is Oden?

Last validated: 2026-05-19

Oden is the Voysys software stack for remote operation of vehicles and machines.

The vehicle side captures and encodes video, the operator side receives and displays it, and Bifrost coordinates fleet sessions when vehicles are managed through the Voysys cloud.

Products and roles

Part	Role
Oden Streamer	Runs on the vehicle computer. It captures camera/video inputs, renders the Streamer scene, encodes output video, sends audio, and manages the vehicle-side network links.
Oden Fleet Streamer	The same as Oden Streamer but includes the Fleet Client and Oden Control Pipeline plugins and includes a systemd service for headless operation.
OdenVR	Runs on the operator computer. It receives the Streamer output, renders the operator view, and embeds the webview operator UI.
Oden Dome Player	A Player variant for projection-dome installations. It uses the same core Player concepts, with dome rendering and calibration workflows.
Bifrost	Voysys fleet management. It tracks online vehicles, authenticates operators and vehicles, manages teleoperation sessions, and relays network traffic when needed.

Part

Role

Oden Streamer

Runs on the vehicle computer. It captures camera/video inputs, renders the Streamer scene, encodes output video, sends audio, and manages the vehicle-side network links.

Oden Fleet Streamer

The same as Oden Streamer but includes the Fleet Client and Oden Control Pipeline plugins and includes a systemd service for headless operation.

OdenVR

Runs on the operator computer. It receives the Streamer output, renders the operator view, and embeds the webview operator UI.

Oden Dome Player

A Player variant for projection-dome installations. It uses the same core Player concepts, with dome rendering and calibration workflows.

Bifrost

Voysys fleet management. It tracks online vehicles, authenticates operators and vehicles, manages teleoperation sessions, and relays network traffic when needed.

In the task pages, Player means OdenVR or Oden Dome Player.

Fleet architecture

In the fleet-managed path, the Streamer and Player both connect to Bifrost through the Fleet Client plugin. The operator selects a vehicle by fleet name. Bifrost creates the session and gives both sides enough information to configure the Remote Streamer and Streamer network links.

After the session is active, traffic may start through a relay and then move to a direct peer-to-peer path if both networks allow it. The same session can also carry Oden Control Pipeline data, webview messages, audio, and link feedback.

Typical data flow:

The vehicle starts Oden Fleet Streamer and authenticates with Bifrost.
The operator starts the Player and authenticates with Bifrost.
The Player requests the online vehicle list.
The operator selects a vehicle.
Fleet Client configures the Player Remote Streamer entity and matching Streamer network links.
The Streamer starts output and the Player receives video, audio, and feedback.

For the first connection steps, see Oden Quickstart and Connect Player and Streamer.

GUI layout

Oden Streamer and the Player share the same basic GUI structure. Streamer has vehicle-side tabs such as Output and Network. The Player has operator-side entities such as Remote Streamer, optional webview content, and display settings.

Top menu: Use File for opening and saving projects, Edit for scene/entity edits, Window for fullscreen behavior, and Help for license actions, changelog, manual, and application information.
Sidebar: Use Root Entity and Scenes for the scene graph, Plugins for plugin paths and global plugin instances, Com Channels for low-level communication channels, Statistics for runtime metrics, Project Settings for project-saved behavior, and Application Settings for local application behavior. Streamer adds Network and Output. The Player configures received Streamer network, audio, and video through each Remote Streamer entity.
3D viewport: The viewport shows the active scene. Hold the left mouse button and use W, A, S, and D to move; use Q and E to move down and up. Use the home icon or Ctrl+Q to return the viewport camera to the origin. Oden uses a right-handed coordinate system: -Z is forward, +Y is up, and +X is right.

Project model

Both Streamer and Player behavior is stored in .vproj project files.

Streamer project: Stores the vehicle scene, camera/video inputs, Streamer output settings, network settings, plugins, and startup behavior. For Fleet Streamer service deployments, the default production project path is /opt/oden-streamer/oden-vehicle-config.vproj.
Player project: Stores the operator scene, Remote Streamer entities, webview settings, native layout entities, plugins, and display behavior. In many fleet deployments, the visual layout and vehicle selection are driven by a webview instead of a hand-edited Player scene.
Application config: Stores local application settings such as window mode and hidden-GUI behavior. On Windows it is under %LOCALAPPDATA%\oden\oden.conf. On Linux it is under $HOME/.config/oden/oden.conf.

Use the Oden GUI for normal project editing. The .vproj files use libconfig syntax and can be edited by deployment tooling, but manual edits can break the project if field names or nested structures are wrong.

For deeper configuration, see Projects and Scenes.