Skip to content
JelinaJelina DocumentationTechnical documentation
Back to website

Jelinvisor device agent

Jelinvisor is the management component running on every JelinaOS device and the bridge to the JelinaCloud platform. It enables devices to connect to the cloud upon registration, stay online during updates, and support remote maintenance.

What it does

Section titled “What it does”
Responsibility Description
Device onboarding Automatically registers a device with the cloud after its first boot and maintains online status
Status reporting Continuously reports operating status, including system version, network addresses, resource usage, temperature, and application status
Update execution Receives and executes cloud-delivered system, kernel, application, and incremental updates; handles confirmation and rollback
Application management Manages the full lifecycle of containerized and non-containerized applications (ProgramSet): start, stop, restart, and upgrade
Local interfaces Provides local management interfaces for on-site status queries, service operations, and device control
Remote channel Relays management requests through secure channels when the cloud cannot connect directly to a device, maintaining remote reachability

Four operating modes

Section titled “Four operating modes”

Jelinvisor supports several modes for different network and management conditions:

Mode Use case Behavior
Cloud-managed Standard JelinaCloud deployment Full registration, reporting, and cloud command reception
Locally managed Private or isolated networks without a cloud Deliver and manage applications through local interfaces
Offline Temporary network disconnection Retains cloud configuration, suspends network activity, and reconnects automatically when connectivity returns
Standalone Deployments entirely without cloud connectivity Local device self-management without any cloud component dependencies

In every mode, local device capabilities—application execution, system management, and watchdog protection—remain fully available.

How it works with the cloud

Section titled “How it works with the cloud”
┌────────────────┐     ① Registration / status reports      ┌────────────────┐
│  Edge device   │ ───────────────────────────────────────▶ │                │
│ ┌────────────┐ │                                         │  JelinaCloud   │
│ │ Jelinvisor │ │ ◀─────────────────────────────────────── │ Cloud platform │
│ └────────────┘ │     ② Updates / configuration / commands │                │
│  JelinaOS      │                                         │                │
└────────────────┘     ③ Secure remote operations channel  └────────────────┘
  1. Upstream: Device status, logs, and alerts are continuously reported for real-time cloud visibility.
  2. Downstream: System updates, application releases, and runtime policies are centrally orchestrated and delivered.
  3. Bidirectional: Remote SSH, remote desktop, and service operations reach devices through secure channels.

Designed for field safety and security

Section titled “Designed for field safety and security”
  • Local update confirmation: Critical updates can wait for on-site confirmation before installation, leaving the final decision with on-site personnel.
  • Access authentication: Local interfaces use key-based authentication, reject unauthorized requests, and support key regeneration.
  • Production mode: Devices accept access only through the cloud; direct access is unavailable even on the same LAN, minimizing the attack surface.
  • Automatic reconnection: Connections are reestablished automatically when network connectivity returns, without manual intervention.

Local interfaces

Section titled “Local interfaces”

The device agent exposes local management interfaces for on-site operations and script integration:

  • Local address: localhost:48484; the port is configurable.
  • Common interfaces: process readiness checks, version queries, update status queries, target state prechecks, and update confirmation.
  • Prefer device-side commands such as jelina-local-ota for routine operations, as they handle configuration and sensitive information automatically. If direct API calls are necessary, use the local loopback address.

Health checks

Section titled “Health checks”
Terminal window
jelina-info --get jelinvisor --json        # Device agent status and version
systemctl status jelina-jelinvisor          # Service status
journalctl -u jelina-jelinvisor -n 100      # Agent logs

Updating itself and the system

Section titled “Updating itself and the system”

Jelinvisor itself supports online updates, centrally orchestrated by the cloud alongside system, kernel, and application updates. Keeping the device agent current supports device security and continued feature development.

Technical foundation

Section titled “Technical foundation”

Jelinvisor is built on mature industry device management architecture and incorporates years of large-scale device fleet management practice, providing a proven foundation for industrial deployments at scale.

Section titled “Related documentation”