Nexigon Architecture

Nexigon separates fleet coordination from the software that runs on each device. This lets you use its remote access and management features with your own operating system, updater, and applications.

Nexigon Hub and Connected Tools

Nexigon Hub is the central service. It authenticates devices, manages fleet resources, stores device properties and events, and coordinates operations. Nexigon Cloud runs this service for you. A self-hosted installation runs its own Nexigon Hub instance.

Nexigon Agent runs on each device and connects to Nexigon Hub. Applications and scripts on the device use Nexigon Agent to read configuration, report state, emit events, and request software downloads. Optional features expose local services, a remote terminal, and device commands.

Nexigon CLI connects a workstation or automation job to Nexigon Hub. It manages resources and forwards ports from connected devices. Applications can also call the Actions API directly or through an SDK.

Ownership and Isolation

An organization contains projects, software repositories, and members. A project contains devices. Separate projects can isolate testing and production fleets.

Repositories hold versioned software and other files. They are independent of projects: several projects can use one repository, and devices in one project can use several repositories. See Organizations and Projects and Repositories for the resource model.

Desired State and Reported State

Device properties store named JSON values. A protected property lets an operator specify configuration that a device can read but cannot change. An unprotected property lets a device report its state.

A device-side service reads desired configuration, applies it, and reports the result. Nexigon stores and distributes those values; the service decides how to apply them. The device configuration guide shows this pattern with a sensor service.

Device events record what happened over time, such as an update failure. Device commands request an immediate action and return its result.

Software Delivery and Fleet Coordination

A system update integration combines these interfaces: repositories hold update bundles, properties select a release and report progress, and events record changes. The device’s updater installs and verifies the software.

An operation coordinates that work across a fleet. It selects devices, runs ordered steps, and controls stage advancement using reported results. Device-side integrations remain responsible for applying configuration and installing software.