Architecture & Integration

Two Routes to Full Control of Any Device Fleet.

One architecture for encoders, cameras, and IP devices. Whether you build the hardware or just field it.

One control plane for fleets stuck on networks you don't control — cellular, CGNAT, firewalled enterprise LANs, or environments with no connectivity at all.

  • Reach the device interfaces that already ship
  • Normalized APIs for programmatic control
  • One transport, security, and deployment model underneath
  • Both paths run at once, on the same device
Request a Demo
Native Access Engineers, vendor support
Unified Control NOC, automation
Secure Reverse Transport One connection per device
Two Management Models

Two control paths, one shared infrastructure underneath.

Two control paths, and they interoperate. Both ride the same secure reverse connectivity layer, so you get simultaneous access without standing up infrastructure twice.

Native Device Access
Unified Programmatic Control
Primary users
Engineers, vendor support
NOC, automation systems
Interface
Device GUI / native API
RemoteGenius API & dashboard
Vendor knowledge
Required
Abstracted away
Automation
Limited
Full end-to-end
Fleet consistency
None — per-vendor
Fully normalized

Same secure reverse connectivity layer for both. No infrastructure built twice.

Transport Layer

Secure connectivity, no network changes.

Every device talks out; nothing dials in. One reverse SSH tunnel per device, multiplexed across as many local services as you need.

Outbound-Only

No inbound ports, VPNs, or static IPs

  • The device opens a persistent reverse SSH tunnel
  • No firewall changes on your side
  • Runs behind any NAT or proxy
Any Network

Traverses CGNAT, cellular, and enterprise firewalls

  • Behind carrier-grade NAT on mobile networks
  • LTE and 5G modems with rotating IPs
  • Segmented enterprise LANs that lock down egress
Multiplexed

One connection → many services per device

  • HTTP / HTTPS for GUIs and REST APIs
  • WebSocket for live control and logs
  • MQTT, RTSP, ONVIF, and custom TCP
Supported protocols
HTTP / HTTPSWebSocketMQTTRTSPONVIFCustom TCP
Option 1 — Native Device Access

Direct access to device interfaces. No integration work.

Operators hit the device exactly as the manufacturer built it. Vendor UI, native APIs, debug tools, logs — nothing stripped, and nothing exposed on the public internet.

  1. 01 Pick the device in the dashboard
  2. 02 Open a secure session
  3. 03 Land in the device UI, proxied
Characteristics
  • No VPN client and no port forwarding
  • Device credentials stay hidden
  • Access controlled by RemoteGenius RBAC
  • Full feature parity with the native interface
Security model
  • Per-device SSH keys (ed25519)
  • Short-lived session tokens (JWT)
  • Centralized credential rotation
  • Revoke access instantly
When it is used
  • Debugging and field support
  • Vendor-specific configuration
  • Devices without formal integration
  • Firmware that is early or changing fast
https://console.remotegeni.us/session/…
DEVICE · vendor ui
Dashboard
Network
Streams
System
Logs
Option 2 — Unified Programmatic Control

One normalized control surface across multi-vendor fleets.

Every device — any vendor, any firmware — shows up behind one schema and one API. Operators work standardized fields, consistent actions, and unified telemetry. Not vendor-specific implementations.

Underlying components
Device Shadow

Server-side digital twin

  • Holds authoritative device state
  • Exposes a unified REST API
  • Decouples control logic from connectivity
Device Adapter

Modular translation layer

  • Converts generic commands to device-specific calls
  • Handles JSON, XML, query-param APIs
  • Encodes vendor-specific behavior
WS API Proxy

Local mediation bridge (optional)

  • For devices that restrict direct API access
  • Local API bridging and file interaction
  • Persistent outbound connection
Exposed to operators
  • Read the full configuration snapshot
  • Patch multiple settings in one request
  • Execute actions — reboot, reset, restart stream
  • Monitor real-time telemetry
  • Run firmware upgrades
  • Track the full audit history
Unified schema examples

Every device setting maps to a canonical key. Adapters take care of type conversion, conditional fields, dependency chains, and which changes force a reboot.

  • net.lan.ip LAN IPv4 address
  • net.wifi.ssid Wi-Fi network name
  • stream.bitrate Encoder output bitrate

Operators never touch a vendor-specific API.

ReGen Bridge device
ReGen Bridge

Pull legacy and non-integrated devices under control.

When direct integration isn't possible, a ReGen Bridge sits in as a local intermediary. It connects securely out to RemoteGenius servers and talks to nearby devices over LAN. That covers closed systems, legacy hardware, and devices with no remote capability of their own.

  • Secure outbound link to the RemoteGenius cluster
  • Talks to local devices over Ethernet or serial
  • Runs adapters for closed or legacy hardware
  • No changes required to device firmware or topology
Deployment scenarios
Device exposes API only
Bridge + Adapter
No remote access at all
Bridge device required
Full integration possible
No bridge needed
Deployment Models

Deploy across cloud and on-prem.

Same APIs whatever the mode. A Cloud Gateway abstraction lets clusters run connected, disconnected, or in hybrid failover.

Cloud

Fully managed

  • Multi-tenant or dedicated clusters
  • Auto-scaling infrastructure
  • Centralized control plane
On-Premise

Isolated and air-gapped

  • Local authentication and control
  • Operates with no external connectivity
  • Manual sync of global data
Hybrid

Cloud + on-prem combined

  • Failover between modes
  • Redundant clusters across sites
  • Switches online / offline without dropping control
Multi-Tenant Architecture

Fits small fleets and global deployments the same.

The same platform runs a two-device pilot and a thousand-node rollout. Logical isolation is enforced at every layer.

Capabilities
  • Multi-tenant shared infrastructure
  • Dedicated single-tenant clusters
  • Virtual servers per customer
  • Logical isolation across all layers
Enforcement layers
  • API-level tenant isolation
  • Database scoping per org
  • Token-based device authentication
  • Cluster-wide whitelisting
Result

Small customers get zero-setup infrastructure. Enterprises get full control and isolation.

Security Model

Security end to end.

Security isn't bolted on top. It is the transport. Every tunnel, every API call, every device — authenticated and auditable.

Transport

SSH-encrypted tunnels

  • Device ↔ platform end-to-end encryption
  • Per-device ed25519 key pairs
  • No shared secrets across the fleet
Identity

JWT & token-based auth

  • Short-lived session tokens
  • Token rotation and expiry
  • Centralized credential management
Governance

RBAC and audit

  • Role-based access across users and devices
  • Audit logging of all actions
  • Scoped API access per tenant
For Hardware Vendors

Turn your devices into a managed platform.

Adoption doesn't mean redesigning firmware. Integration can deepen over time — from zero-code bridge access up to full native API integration.

Immediate Gains

Cloud control without the build

  • Skip building remote infrastructure
  • Ship enterprise features on existing hardware
  • Meet US and EU managed-device expectations
Integration Levels

Pick your depth

  • Native API integration via Device Adapter
  • Proxy-based integration via WS API Proxy
  • No integration — bridge-only access
Enterprise Requirements

Reach regulated buyers

  • Remote management and support
  • Full auditability of access and changes
  • Automation APIs for NOC integration

No firmware redesign to adopt. Integration can deepen later.

Operational Model

How customers actually run it.

In production the two paths don't get equal use. Automation runs the day-to-day. Native access stays in reserve for the long tail of edge cases.

90–95%
Unified API

Automation for scale — NOCs, dashboards, and scripted operations

5–10%
Native UI fallback

Reserved for debugging, vendor tooling, and new firmware

Takeaways

One platform. Two paths. Every device.

One connectivity model, two control paths, and deployment that scales from a single tenant to a global fleet.

  • One connectivity model supports all devices
  • Two control paths for different operational needs
  • Bridge devices extend coverage to any hardware
  • Adapters normalize vendor diversity
  • Deployment works in cloud, on-prem, or hybrid
  • Security and auditability are built in
Request a Demo
Talk to Engineering