Foxglove Alternative: Open, Browser-Based ROS 2 Visualization (2026)
If you're searching for a Foxglove alternative, you probably already know why. Foxglove — the ROS 2 visualization app a lot of robotics teams standardized on — is no longer the free, open desktop tool it started as. Foxglove 2.0 moved to a closed-source, per-seat model, and the on-premise deployment that self-hosted and air-gapped teams relied on is now an Enterprise-tier feature. If your budget, your procurement process, or your disconnected robot lab can't absorb that, you're in the market for something else.
This post is an honest map of the alternatives — RViz2, Rerun, and browser-based ROS 2 visualization (the lane Yugma sits in) — including where each one genuinely beats the others, and where Foxglove is still the right tool despite the price.
# What changed with Foxglove 2.0
Foxglove Studio began life as an open-source (MPL-2.0) desktop app. That's a big part of why it spread: you could install it, self-host the data platform, and never think about seats. Foxglove 2.0 changed the deal:
- The app went closed-source. The old open-source Studio repository was deprecated.
- Pricing is per-seat — published at around $42/user per month — plus a per-device fee (roughly $20/device) once you're ingesting fleet data at scale. Pricing moves, so verify the current numbers on their site.
- Self-hosted / on-prem is Enterprise-only now, which matters a lot for defense, medical, and any team that can't ship robot data to a vendor cloud.
- The community responded with forks. The most active is Bosch's Lichtblick, a maintained open-source continuation of the last MPL-licensed Studio.
None of this makes Foxglove a bad tool. It's still excellent. It's just no longer free-and-open, which quietly breaks an assumption a lot of teams built their entire tooling stack around.
# What to look for in a Foxglove alternative
Before you pick a replacement, get specific about what you actually used Foxglove for. A good Foxglove alternative for a live-robotics team usually needs:
- A live ROS 2 connection over rosbridge and/or the Foxglove WebSocket protocol — not just offline log files.
- The core panels: URDF, TF tree, PointCloud2, OccupancyGrid, and camera/image streams.
- Zero-install viewing, so a teammate, a manager, or a customer can open a view without standing up a ROS environment.
- Shareable output — a link beats a screen-share, and a screen-share beats "come sit at my Linux box."
- Honesty about cost and licensing — open-source, proprietary, or somewhere in between.
- Bonus: a robot model library, so you're not hand-authoring a URDF for every arm before you can see anything.
# Foxglove alternatives compared
| Tool | License | Install | Share a view | Live ROS 2 | Robot catalog | Cost |
|---|---|---|---|---|---|---|
| Foxglove 2.0 | Proprietary | Web + desktop | Cloud (paid) | WS + MCAP | No | ~$42/seat + device |
| RViz2 | Open (BSD) | ROS desktop | X11 / VPN only | Native | No | Free |
| Rerun | Open (Apache/MIT) | Desktop + SDK | .rrd file | Via SDK logging | No | Free |
| Yugma | Proprietary | Any browser | Link | rosbridge + WS | 1,315 models | Free / €19 / €99 |
A note on the word "open." If open means open-source, your picks are RViz2 (BSD, ships with ROS 2) and Bosch's Lichtblick fork — start there, and Rerun if you're logging from code. If open means open in any browser, no install, shareable by link, that's the browser-viz lane. Yugma is honest about being proprietary; it's not an open-source project. Different meanings of the same word, and worth being clear about before you choose.
# Where browser-based ROS 2 visualization fits
The browser lane exists to kill one specific pain: getting a live robot view in front of someone who does not have — and will not install — a ROS environment.
Yugma connects to whatever you already run to expose ROS 2 over WebSocket:
# rosbridge — JSON over WebSocket, port 9090
ros2 launch rosbridge_server rosbridge_websocket_launch.xml
# Foxglove WebSocket bridge — efficient CDR, port 8765
ros2 launch foxglove_bridge foxglove_bridge_launch.xml
Point a browser tab at the bridge and the URDF, TF tree, PointCloud2 (REP-103 Z-up handled correctly), OccupancyGrid, and camera feeds render — with no local ROS install on the viewing machine. From there you also get teleop (cmd_vel and Nav2 goals), MCAP record and replay, and WebXR teleop with a hardware-style safety stop.
Two things a pure viewer doesn't give you that matter here. First, a 1,315-model industrial catalog — each entry packs kinematics, physical specs, and meshes — so you can stand up a robot to visualize before the hardware arrives. For scale: a recent arXiv survey found the entire public URDF corpus is roughly 195 unique robot models; Yugma's catalog carries 1,315. Second, in-browser forward kinematics with joint sliders plus Rapier physics, so the model isn't just a static mesh — you can pose it and watch it move.
The feature that actually replaces Foxglove for the "show someone" job is sharing: send a URL, and the other person opens the live view — or an MCAP replay — in their browser. No seats to provision, no X11, no VPN. If your ROS work is mostly viewing a URDF robot in the browser and getting it in front of stakeholders, this is the lower-friction path.
# Where Foxglove still wins
Be honest with yourself before you switch. Foxglove earns its price on real strengths a browser viewer does not match yet:
- Deep rosbag / MCAP scrubbing — frame-by-frame, multi-panel, synchronized across topics. This is best-in-class.
- Time-series plots — Yugma does not have a mature plotting panel. If you correlate twenty numeric series to chase a bug, that's Foxglove's home turf.
- Raw message inspection, diagnostics, and years of debugging polish — the boring-but-critical maturity that only ships time.
- Layout persistence and a large panel ecosystem.
Yugma records and replays MCAP, but it is not a plotting-and-forensics debugger, and pretending otherwise would waste your time. If your day is spent scrubbing bags and reading raw message tables, keep Foxglove — or the Lichtblick fork — for that, and use a browser viewer for the live, shareable jobs. For the full three-way breakdown, see RViz vs Foxglove vs browser ROS 2 viz.
# FAQ
Is there a free, open-source Foxglove alternative?
Yes — two solid ones. RViz2 ships with ROS 2 and is BSD-licensed, best on desktop Linux. Lichtblick, Bosch's actively maintained fork of the last MPL-era Foxglove Studio, keeps the familiar Foxglove UX open-source. Rerun is open-source too, but it's a logging viewer rather than a live ROS graph tool. If open-source is a hard requirement, start with those.
Can I use a Foxglove alternative without installing ROS?
For viewing, yes. A browser viewer like Yugma connects to a machine that runs rosbridge or the Foxglove WebSocket bridge; anyone with the link then opens the visualization in a plain browser with no ROS install. ROS 2 still has to run somewhere to publish the topics — the browser just consumes the stream.
Does Yugma replace Foxglove?
No, and it's worth saying plainly. Yugma covers live browser visualization, teleop, a large robot catalog, and MCAP replay. Foxglove still wins deep rosbag forensics and time-series plotting. Many teams will use a browser viewer for shareable live views and keep Foxglove or a fork for heavy debugging — the two are complementary more than competitive.