{"slug": "remote-access-is-generally-available", "title": "Remote Access is generally available", "summary": "Foxglove announced that Remote Access is now generally available, enabling users to visualize and teleoperate robots remotely through the Foxglove platform, even behind firewalls or on unreliable networks. The feature uses WebRTC and a Foxglove-managed Selective Forwarding Unit to relay streams, and is available on Pro and Enterprise plans. A live demo is scheduled for September 2, 2026.", "body_md": "# Remote Access is generally available\n\nRemotely debug and teleoperate any robot in your fleet.\n\nAs your robotics operation scales out of the lab and into the field, you need a rock-solid debugging solution. Today, as part of our [agentic data platform](/blog/introducing-the-agentic-data-platform-for-physical-ai), we are announcing that Remote Access is generally available. This feature allows you to visualize and teleoperate remote devices through the Foxglove platform, even if they are behind a firewall, on a flaky LTE link, or on a network you have no control over.\n\n## Connecting live to remote robots\n\n### Setting up the robot for Remote Access\n\nThe robot needs to run a [remote access gateway](https://docs.foxglove.dev/docs/fleet/remote-access#setting-up-a-gateway). You can get it in one of two ways: the Foxglove SDK (for custom code running on the robot) or the Foxglove Bridge (for a ROS stack). The gateway initiates a lightweight connection to the Foxglove cloud platform, authenticated via [device tokens](https://docs.foxglove.dev/docs/fleet/device-tokens).\n\nWhen a user connects to a robot through the app, the platform gives each side a short-lived credential and wakes the gateway on the robot.\n\n### Connecting to the robot\n\nOnce the robot is configured for Remote Access, connecting to it from the app is similar to connecting to any other data source. Just open the connection dialog, or select the device on the devices page. After connecting, it behaves like any other live source. Topics stream into the same panels and layouts you use to visualize recorded data. You can also use the [Teleop](https://docs.foxglove.dev/docs/visualization/panels/teleop) and [Publish](https://docs.foxglove.dev/docs/visualization/panels/publish) panels to send commands back to the robot, provided it is set up to accept commands.\n\n### How Remote Access works\n\nAll streaming happens over [WebRTC](https://webrtc.org/). The Foxglove-managed Selective Forwarding Unit (SFU) acts as the relay between the robot and the people watching. The robot opens one connection to the SFU and uploads each stream once. Each viewer connects separately, and the SFU hands every one of them a copy. Each hop negotiates its own stream quality, so a viewer on bad Wi-Fi drops to a lower bitrate without slowing down the robot or anyone else.\n\n## Try Remote Access\n\nRemote Access is available today on Pro and Enterprise plans. See our [Remote Access guide](https://docs.foxglove.dev/docs/fleet/remote-access) for the exact steps to connect to your robots remotely.\n\nOur engineers will demo these features live on September 2, 2026. [Register now](https://luma.com/foxglove-agentic-workflows).", "url": "https://wpnews.pro/news/remote-access-is-generally-available", "canonical_source": "https://foxglove.dev/blog/remote-access-is-generally-available", "published_at": "2026-08-18 06:42:04.773856+00:00", "updated_at": "2026-08-18 06:42:06.645142+00:00", "lang": "en", "topics": ["robotics", "ai-infrastructure", "developer-tools"], "entities": ["Foxglove", "Foxglove SDK", "Foxglove Bridge", "WebRTC", "Selective Forwarding Unit"], "alternates": {"html": "https://wpnews.pro/news/remote-access-is-generally-available", "markdown": "https://wpnews.pro/news/remote-access-is-generally-available.md", "text": "https://wpnews.pro/news/remote-access-is-generally-available.txt", "jsonld": "https://wpnews.pro/news/remote-access-is-generally-available.jsonld"}}