What is RG Platform¶
RG Platform is a fleet-management system for remote IP-enabled devices: any hardware that exposes a web management dashboard, an internal API, or neither. It reaches those devices behind CGNAT and firewalls using outbound-only reverse tunnels, represents each one under a single vendor-neutral device shadow, and runs the whole fleet on regionally distributed clusters that stay operational without the cloud.
RemoteGenius (RG Platform) is a fleet-management platform for remote IP-enabled devices — anything with a web management dashboard or an internal API, from network appliances and industrial controllers to cameras and sensors — that reaches hardware behind CGNAT and strict firewalls using outbound-only reverse tunnels, unifies mixed-vendor fleets under one device-shadow schema, and runs on a regionally distributed, air-gap-capable cluster architecture.
What counts as a manageable device¶
A manageable device is any IP-enabled endpoint in one of three integration states. A device with an internal API is fully integrated: an adapter speaks that API and maps its settings into the device shadow. A device with only a web GUI is partially integrated: an adapter handles what the API exposes, and operators reach the rest through native GUI access tunneled by the platform. A device with neither — a closed or legacy endpoint — is represented through an RG Bridge in appliance form factor that fronts it over Ethernet. There is no "unsupported" tier: every IP device fits one of these states. The device's own management interface (HTTP, typically bound to 127.0.0.1 on the device) is what the platform tunnels; its API is what an adapter normalizes.
Problem: networks you cannot reach inbound¶
Most remote devices sit behind CGNAT, cellular links, or firewalls the operator does not administer, so no inbound connection can reach them. RG's mechanism is outbound-only connectivity: the device initiates a single encrypted connection outward to its cluster and holds it open. The platform never listens for an inbound connection at the edge, needs no port forwarding, no public IP, and no VPN. The outcome is that a device appears in the dashboard after pairing regardless of the network it lives on, and the site owner exposes nothing.
Problem: mixed-vendor fleets without per-SKU integrations¶
Fleets accumulate hardware from many vendors, models, and firmware revisions, and building a bespoke integration per SKU does not scale. RG's mechanism is the device shadow plus adapters: one canonical schema describes settings, reported state, supported actions, and firmware for every device, while a per-device adapter translates that schema to and from each device's native representation. The outcome is that bulk changes, drift detection, and parity reporting run uniformly across unrelated hardware, and adding a model means adding one adapter, not a new control surface.
Problem: surviving cloud outages¶
A fleet whose control plane depends on continuous cloud reachability stops working the moment the cloud does. RG's mechanism is the autonomous RG Cluster: each regional cluster owns its devices, pairing, tunnels, adapters, telemetry, RBAC, and audit locally, and continues to operate when the cloud layer is unreachable or absent. The cloud is a global control plane for accounts and cluster registry, not a runtime dependency on the device data path. The outcome is local-first operation: pairing, control, and audit keep working through a cloud outage or a permanent air gap.
Problem: tenant isolation and compliance¶
Shared infrastructure and regulated environments both require that one tenant can never observe or reach another, and that every consequential action is provable. RG's mechanism is tenant isolation enforced at the query, allocation, and audit layers — not the UI — combined with an investigation-grade audit trail written transactionally with each action. Cross-tenant lookups return enumeration-resistant "not found". The outcome is that managed-service providers can host many customers on one cluster, and regulated operators can run a private or air-gapped cluster with a complete local record.