# What is Oden?

Understand the main Oden products and the fleet connection model.

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 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. The same as OdenVR but with support for large scale dome rendering using multiple projectors. Contact Voysys for more information. |
| Bifrost | Voysys fleet management. It tracks online vehicles, authenticates operators and vehicles, manages teleoperation sessions, and relays network traffic using our global network when needed. |

In the docs, **Player** means OdenVR or Oden Dome Player.

## Fleet architecture

The Streamer and Player both connect to Bifrost. The operator selects a vehicle by fleet name. Bifrost creates the session and sends connection information (including per-session encryption keys) to the Player and Streamer.

When the connection is established, network traffic starts through a relay and then moves to peer-to-peer path if possible. Each network link carries video, audio, and data over the same connection.

Typical flow:

1.  The vehicle starts Oden Fleet Streamer and authenticates with Bifrost.
    
2.  The operator starts the Player and authenticates with Bifrost.
    
3.  The Player requests the online vehicle list.
    
4.  The operator selects a vehicle.
    
5.  Fleet Client configures the Player `Remote Streamer` entity with network links matching the Streamer project.
    
6.  The Streamer starts output and the Player receives video, audio, and data.
    

For the first connection steps, see [Oden Quickstart](quickstart.md) and [Connect Player and Streamer](connect-player-and-streamer.md).