Glossary¶
Canonical RG Platform terms and their one-line definitions. Each definition is self-contained and can be read on its own.
RG Platform — RemoteGenius's fleet-management platform for remote IP-enabled devices, reaching hardware behind CGNAT and firewalls via outbound-only reverse tunnels and managing mixed-vendor fleets under one device-shadow schema.
RG Bridge — the connectivity element that establishes a device's outbound tunnel; it has one of two form factors — agent (embedded on the device, tunneling the device's own management interface out) or appliance (a standalone small Linux device fronting one or more external devices over Ethernet).
RG Cluster — an autonomous regional execution plane, built from interchangeable nodes, that owns the devices, bridges, tunnels, adapters, operations, and audit for the fleet homed to it, and that continues operating if the cloud layer is lost.
Device shadow — the canonical, vendor-neutral representation of a device's settings and status — current settings, reported state, supported actions, firmware, and change history — that operators, RBAC, monitoring, and audit all interact with, regardless of the device's make.
Adapter — the component behind the device shadow that speaks a specific vendor, model, and firmware's native API, translating canonical settings into the device's native representation and back, and selected per device.
Native GUI access — operator interaction with a device's own web GUI, tunneled through the platform and access-controlled, used for control the device's API does not expose; every access is audited.
Form factor — a bridge's deployment shape, one of exactly two values: agent, embedded on the device itself, or appliance, a standalone Linux device fronting external hardware over Ethernet.
Attachment state — a device's relationship to a bridge, one of exactly three values: never_attached, attached, or detached, where attached implies a bridge is currently linked.
Outbound-only connectivity — RG's model in which the device initiates every connection outward to its cluster, so the platform needs zero inbound ports at the edge and works behind networks the operator does not administer.
Reverse tunnel — the long-lived, encrypted channel a device opens outward to its cluster node, through which the device's local services are reached at cluster-side endpoints without any inbound path to the device.
Port-allocation record — the mapping that ties a device's local service, reached through its reverse tunnel, to the endpoint allocated for it on the cluster node, and that is reclaimed when the channel goes stale.
Pairing — the onboarding flow that admits a device to a cluster with no pre-shared secret, combining a short-lived operator-visible code with a fresh device-generated key that becomes the device's permanent trust anchor.
Two-tier RBAC — RG's authorization model that combines an organization-scope role with an optional per-cluster role override, resolved per request against a resource-typed permission catalog.
Permission catalog — the resource-typed set of permissions that roles are built from, organized by the kind of resource each permission acts on, so custom roles compose predictably by resource type.
Tenant isolation — the enforcement, at the query, allocation, and audit layers, that an organization can only ever reach its own resources, with cross-tenant requests returning enumeration-resistant "not found" responses.
Air-gapped cluster — a cluster running with zero external connectivity as a first-class mode, holding local identity, RBAC, and audit, delivering full operation offline and reconciling safely if later reconnected.
Correlation identifier — the value carried on audit events that ties related events together across a single operation or session, so an investigation can follow one action end to end.
CGNAT — carrier-grade network address translation, a common ISP arrangement that denies devices a publicly reachable address; RG's outbound-only tunnels reach devices behind it without any inbound path.