# Remote Access is generally available

> Source: <https://foxglove.dev/blog/remote-access-is-generally-available>
> Published: 2026-08-18 06:42:04.773856+00:00

# Remote Access is generally available

Remotely debug and teleoperate any robot in your fleet.

As 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.

## Connecting live to remote robots

### Setting up the robot for Remote Access

The 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).

When 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.

### Connecting to the robot

Once 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.

### How Remote Access works

All 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.

## Try Remote Access

Remote 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.

Our engineers will demo these features live on September 2, 2026. [Register now](https://luma.com/foxglove-agentic-workflows).
