# Supervise Many Vehicles

Keep Oden vehicles, operators, sessions, and diagnostics understandable as a deployment grows.

Last validated: 2026-05-05

Use this section when the first vehicle stream works and the next problem is operational: more vehicles, more operators, more links, and more evidence when something behaves badly.

Many-vehicle supervision is usually delivered as a managed enterprise setup. The public self-serve flow is intentionally optimized for getting one vehicle and one operator running quickly. If you are building dispatch, monitoring, authorization, or custom operator handoff for a fleet, talk to Voysys early so the portal model, licenses, and Oden project structure fit the deployment.

## Supervision tasks

-   [Multiple vehicles](multiple-vehicles.md) explains how Oden represents several connected vehicles and how a web operator UI selects the active control target.
    
-   [Fleet management](fleet-management.md) covers the Bifrost/Fleet Client flow that connects vehicles and operators by name.
    
-   [Performance monitoring](performance-monitoring.md) points to the portal and in-application places to check online state, active sessions, and runtime health.
    
-   [Diagnostics and recording](diagnostics-and-recording.md) covers the evidence to collect during acceptance testing and support cases.
    
-   [Troubleshooting](troubleshooting.md) gives first-response checks for connection, video, audio, control, and service issues.
    

## Network configuration

Network setup deserves its own pass once the basic stream is stable. Oden can use multiple links so a vehicle can combine cellular, satellite, Wi-Fi, and local network paths when they are available.

Start with [Network Configuration](network-configuration.md), then use [Network](../configure/network.md) for the lower-level link fields in Oden.