Manages who can do what
- Organizations, users, roles, permissions
- Cluster lifecycle and configuration
- Fleet-wide audit
Platform Architecture
A Distributed Control Plane for Device Fleets.
RemoteGenius splits global coordination from regional execution. Device operations keep running whether the cloud is reachable, degraded, or gone.
Identity, access, cluster structure — the Cloud Gateway owns those. Clusters run every device operation. No device ever holds a direct connection to the Cloud Gateway.
- Cloud Gateway: identity, RBAC, audit
- Clusters own provisioning, telemetry, execution
- Runs across cloud, on-prem, and hybrid
- Clusters keep running when the cloud drops
Cloud Gateway Identity · RBAC · Audit
pull config
Cluster Execution plane
local control
Devices Encoders · Cameras · Bridges
Core Architectural Principle
Clusters are the only layer that touches devices.
The split between control and execution is deliberate — the one invariant every other platform property rests on.
The Cloud Gateway never talks to your devices. Clusters are the only layer that does.
The Cloud Gateway does not proxy, relay, or tunnel device communication.
Execute what actually happens
- Direct communication with every device
- Runtime services, telemetry, automation
- Local execution — no cloud dependency
Cloud Gateway
The global control layer — not a device control plane.
The Cloud Gateway coordinates identity, access, and cluster structure. Nothing wider.
Cluster Lifecycle Management
Provisioning, configuration, and maintenance of every cluster the organization operates.
Identity & Organization
Multi-tenant organizations, user accounts, authentication, and federation into clusters.
Authorization (RBAC)
Role definitions, permission assignments, and cluster-level access control across the fleet.
Audit & Visibility
Centralized audit logs, organization-level activity tracking, and cross-cluster reporting.
Control Model
Pull, not push.
Cloud-connected clusters pull user and org identity plus policy updates from the Gateway, and periodically push cluster inventory and usage data back. Maintenance work — software upgrades and the like — starts when an org admin triggers it through the Gateway, which relays the instruction to the cluster to run locally. Device management never touches the Gateway. Operators work the Cluster API and Dashboard directly.
01 Operator API + Dashboard
02 Cluster Pulls + executes
03 Device Local control path
Clusters
Where the real work happens.
A cluster is a self-contained regional service plane. It provisions devices, configures them, collects telemetry, and runs every operational workflow — cloud, on-premise, or hybrid.
Device Provisioning
Onboarding, registration, token-based authentication, and assignment to organization and cluster.
State & Telemetry
Real-time metrics, telemetry streams, event logs, and device shadow state — all stored locally within the cluster.
Execution Layer
Device management APIs, configuration workflows, automation, scheduling, and streaming services.
Local Autonomy
Clusters do not depend on the Cloud Gateway to manage devices — they keep running when disconnected.
Clusters run more than one configuration path at once, so a mixed fleet stays under one plane.
Native Device GUI
Direct interaction with the device’s own web or local UI. Useful for vendor support, commissioning, and one-off work.
API-Based Control
Standardized management through RemoteGenius APIs — abstracted, normalized, and automation-ready across vendors.
Device Integration
One control plane across heterogeneous hardware.
RemoteGenius supports three integration classes — from fully native devices to third-party APIs to legacy hardware retrofitted through a bridge.
Native Devices
Fully integrated with platform APIs. Direct control through cluster services with first-class feature parity.
Third-Party Devices
Controlled via exposed vendor APIs. Integrated through Device Adapters that translate commands on the cluster side.
Bridge-Based (ReGen Bridge)
For devices without remote capabilities. A local bridge device connects to the target and relays control to the cluster.
Two building blocks decouple the control surface from physical device specifics:
Device Shadow
A digital representation of device state. Provides a consistent control interface regardless of vendor or protocol.
Device Adapters
Translate platform commands into device-specific actions — handling protocol differences and vendor config formats.
Deployment Models
Cloud, on-premise, or hybrid — same control plane.
The separation of control and execution makes every deployment shape a configuration detail, not an architectural rewrite.
Cloud-Managed
Fully hosted clusters. Minimal infrastructure responsibility on the customer side, with automatic scaling.
- Hosted execution plane
- Managed upgrades and scaling
- Ideal for greenfield fleets
On-Premise (Isolated)
Fully self-contained clusters. No external connectivity required; manual or offline synchronization.
- Air-gapped deployments
- Full local autonomy
- Regulated or classified environments
Hybrid
Combination of cloud and on-prem clusters. Central visibility with local execution where it matters.
- Centralized identity + audit
- Local execution per site
- Enterprise and broadcast fleets
Reliability & Plane Separation
Two independent planes, one platform.
The Cloud Gateway and clusters fail independently. A cloud outage never stops device control. Clusters keep running alone.
- Identity and organization accounts
- Role definitions and access policies
- Governance, audit, and reporting
- Cluster lifecycle coordination
- Direct device communication
- Configuration and runtime workflows
- Real-time telemetry and state
- Local automation and scheduling
A Cloud Gateway failure does not affect device control
A cluster operates independently and continuously
Customers retain full control over where execution happens
Air-gapped, on-prem, and hybrid shapes are first-class
Summary
RemoteGenius is not a centralized device proxy.
It is a distributed control system. The Cloud Gateway manages access and structure; clusters perform every device operation. Devices never connect directly to the Cloud Gateway.
- Secure multi-tenant management at fleet scale
- Support for heterogeneous hardware via adapters
- Operates in cloud, hybrid, or fully isolated environments
- Reliable control of device fleets at any size