Prefer env vars at build time (GOOGLE_SITE_VERIFICATION, BING_SITE_VERIFICATION, YANDEX_VERIFICATION, BAIDU_SITE_VERIFICATION, NAVER_SITE_VERIFICATION). Optionally paste meta tags below this comment for a one-off deploy. DNS TXT alternatives: see docs/indexing-playbook.md --> Device connection architecture | Robomap Docs

Robomap Docs

Device connection architecture

Robomap architecture for connecting PLCs, RTUs, industrial sites, edge gateways, and cloud applications.

Secure, scalable connectivity from industrial devices to dashboards, APIs, analytics, and third-party systems.

How the connection works

  1. Connect PLCs, RTUs, robots, or industrial equipment to an edge gateway on the OT network.
  2. Normalize device protocols and buffer data locally when connectivity is interrupted.
  3. Send encrypted telemetry to Robomap using MQTT or HTTPS over TLS 1.2+.
  4. Use the Robomap platform for ingestion, storage, analytics, alerts, dashboards, APIs, and exports.
  • Segment OT and IT networks and expose only the gateway outbound path.
  • Use encrypted transport, credential rotation, and least-privilege API credentials.
  • Monitor gateway health, ingestion status, and alert delivery from the cloud platform.

Key benefits

  • Rapid deployment — no-code oriented setup for many device types
  • Secure end-to-end — TLS in transit and least-privilege credentials
  • Scalable — from a single site edge gateway to multi-site cloud
  • Real-time visibility — dashboards, alerts, and exports for decisions