HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
foxglove
studio
Developer Tools2021–2024
foxglove / studio · Archived

studio

Robotics visualization and debugging

4Distinct people
12Mentions
0Explicit recommenders
93GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Robotics visualization and debugging

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2021-07-08 19:05:23 UTC to 2024-06-20 21:37:19 UTC.

02462021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

12 sources
When I contributed to Foxglove Studio, a robotics data visualization tool built in React and Electron, I found the codebase very easy to navigate. Without much prior JavaScript/TypeScript/React experience, I was able to prototype several new fairly sophisticated features. They've nicely decomposed the code into libraries, with just about the right level of abstraction to make it easy to extend. And given that it's built for visualizing streaming data, they've got performance figured out. Unfortunately they ceased developing it in the open, but there's a lot to learn from the v1 codebase, and other related projects that continue to be open source. https://github.com/foxglove/studio/tree/v1
In Ask HN: Well architected React and Node repos?
Congrats to the Open Robotics team and everyone who contributed to this release! Calling out a couple changes I'm excited about that we (Foxglove) helped contribute to: - MCAP is now the default logging format in Rosbag2[0]. This is a much more performant and configurable format than the previous default (SQLite-based). SQLite is still a fully supported alternative. - Message type definitions (schemas) can now be exchanged at runtime[1]. This means that tools such as rosbag2, or visualization tools such as Foxglove Studio[2] can now communicate with a ROS system over the network without needing a copy of the source code or complete ROS workspace. [0] https://github.com/ros2/rosbag2/pull/1160 [1] https://github.com/ros2/ros2/issues/1159 [2] https://github.com/foxglove/studio
In ROS 2 Iron Irwini Release
> Especially a tool like RViz is always missing. And in many many robotics video I see (of a moderately complex robot), there's ROS's RViz on some screen. I would love the future robotics development stack to be more modular, so that (for example) future middleware solutions don't need to also bundle their own visualization software. This was direct inspiration for creating Foxglove Studio[0] for visualization and MCAP[1] for logging - both work great with ROS, or equally well without it. [0] https://github.com/foxglove/studio [1] https://github.com/foxglove/mcap
In ROS 2 Iron Irwini Release
Foxglove | 100% Remote (North/South America/Australia/NZ time zones) | Full Time or Contract | https://foxglove.dev/ Open source web-based visualization & data stack for robotics and autonomous vehicle development. Join our small, highly experienced, and fast moving team. No robotics experience necessary! Try it here: https://studio.foxglove.dev/ Read our source code: https://github.com/foxglove/studio We're looking for engineers with at least 2 years full time work experience, and/or some impressive side projects. Our stack is primarily TypeScript, with React/Three.js/WebAssembly on the frontend. - Frontend Engineer - Full Stack Engineer - First DevOps/Site Reliability Engineer https://foxglove.dev/careers
In Ask HN: Who is hiring? (August 2022)
Foxglove | Frontend React/WebGL, Full Stack TypeScript | Remote (Americas/Australia/NZ timezone) | Full Time or Contract | https://foxglove.dev/ Robotics and autonomous vehicle developer tools. We're a small, highly experienced, and fast moving team of engineers building the next generation of web-based (browser and electron) robotics and self-driving development tools. Our first product (Foxglove Studio) is an open source visualization and debugging tool for analyzing live and recorded robotics data. We are looking for people who enjoy working across the stack - pushing browser technology to its limits using WASM, WebGL and Web Workers, diving into data serialization formats and binary protocols, or shipping end to end features for our hosted services. Prior experience working with robotics or WebGL isn't necessary, but you must be inter
Read the rest
ested and willing to learn fast. Market salary + meaningful equity. https://foxglove.dev/careers https://github.com/foxglove/studio
In Ask HN: Who is hiring? (November 2021)
Our team built Foxglove Studio (https://foxglove.dev) to integrate multiple visualization / debugging tools into one seamless experience, but until today it has been difficult for our users to share these workflows with their team members. Today we’re excited to announce that collaboration support (in the form of cloud-synced layouts) has arrived with Foxglove Studio v0.19 (https://github.com/foxglove/studio/releases/tag/v0.19.0). We all know that efficient collaboration is critical to robotics development, so we’re very excited about how much this feature can accelerate your team’s ability to iterate on your robots. We can’t wait to hear your feedback!
In Share your ROS data visualization setup across your robotics team
Foxglove | Frontend React/WebGL, Full Stack TypeScript | Remote (Americas/Australia/New Zealand timezone) | Full Time or Contract | https://foxglove.dev/ Robotics and autonomous vehicle developer tools. We're a small, highly experienced, and fast moving team of engineers building the next generation of web-based (browser and electron) robotics and self-driving development tools. Our first product (Foxglove Studio) is an open source visualization and debugging tool for analyzing live and recorded robotics data. We are looking for people who enjoy working across the stack - pushing browser technology to its limits using WASM, WebGL and Web Workers, diving into data serialization formats and binary protocols, or shipping end to end features for our hosted services. Prior experience working with robotics or WebGL isn't necessary, but you must
Read the rest
be interested and willing to learn fast. If you're a roboticist or ML engineer interested in learning frontend development, we're open to that too. Market salary + meaningful equity. https://foxglove.dev/careers https://github.com/foxglove/studio
In Ask HN: Who is hiring? (October 2021)
Thanks for checking it out, and please join our community at https://foxglove.dev/community ! For non-ROS systems, we are working on an Extensions API that will eventually allow writing code to ingest data from a custom source. Currently it's just focused on custom visualizations, not the data pipeline piece yet: https://foxglove.dev/blog/announcing-foxglove-studio-extensi... However, if that's a strong need you have, we can show you where to modify the existing code to add a custom data source (it's possible, just not cleanly exposed into the extensions API yet). For now, converting your other data to ROS bags first is your best bet. Please drop us a note here to discuss your needs in more detail: https://github.com/foxglove/studio/discussions/1268
In Show HN: Web-based visualization for robotics and autonomous vehicles
Hi HN! We are a team of engineers who previously built the infrastructure and developer tools for self-driving car development at Cruise. We recently launched Foxglove Studio [0] as a better way for roboticists to inspect, visualize and debug robotics data. At Cruise, we found existing visualization tools in the robotics space (rviz, rqt, etc) extremely lacking. They were typically desktop linux (QT) apps, and required the entire autonomous vehicle codebase to be checked out and built locally - meaning they were inaccessible to teams such as operations, QA, and PM/TPMs. In addition, robotics engineers found the workflow of downloading 50gb+ log files to their desktop just to triage an issue painful. As a result, we invested heavily in a web-based replacement - building a better, faster UI for our robotics engineers, while at the same time
Read the rest
opening data up to everyone in the organization, so that you can share a link to an event in a Slack thread or Jira ticket, and others can quickly see the exact same view on their own laptop or desktop. Cruise open-sourced part of this work, which some of you may be familiar with (Webviz) [1]. Earlier this year, we launched Foxglove Studio, which began as a fork of Webviz. Over the past 6 months, we have been extending Studio with many new visualization panels, first-class extension support, ROS 2 support, an optional desktop app, and internally a port from Flow to Typescript. While Studio began as a fork of Webviz, we see it as a separate product - we're focused on building an extensible, community-first project, and we are taking it in a different direction than Webviz (which is tightly coupled to many internal Cruise systems, and as such is difficult for the community to contribute to). In the future, we're planning to introduce some paid features around team collaboration, data & view sharing, and private extensions. However, the core of Foxglove Studio will always remain free and open source for the robotics community to use. Feel free to check out our GitHub [2] and Changelog [3] for more details on what we've been up to. Happy to answer any questions! [0] https://foxglove.dev/ [1] https://webviz.io/ [3] https://github.com/foxglove/studio [4] https://github.com/foxglove/studio/releases
In Show HN: Web-based visualization for robotics and autonomous vehicles
Hi HN! We are a team of engineers who previously worked on self-driving cars and robotics tooling at Cruise and other companies. We recently launched Foxglove Studio as a better way for roboticists to inspect, visualize and debug robotics data. Foxglove Studio began about 6 months ago as a fork of Webviz - software that our team worked on and open sourced at Cruise. Studio expands on Webviz with a port to Typescript, many new panels, extension support, and an Electron-based desktop option (see our github [0] and release notes [1] for more details on what has changed). Happy to answer any questions! [0] https://github.com/foxglove/studio [1] https://github.com/foxglove/studio/releases
In Show HN: Web-based visualization for robotics and autonomous vehicles

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.