RWT Robotics is an independent publication covering the robotics industry, with one job above all others: separating real progress from hype. We follow humanoid robots, physical AI, industrial and service machines, the companies building them, and the software that makes them work.
What We Cover
Robotics news moves fast, and much of it arrives as polished demo videos and funding announcements. We focus on what those announcements mean, what is actually shipping, and what is still a lab prototype.
Our main beats:
- Humanoid robots and physical AI. General-purpose humanoids, the foundation models being trained to control them, and the gap between staged demos and real-world deployment.
- Industrial and service robots. Robot arms, mobile robots in warehouses and factories, cleaning and delivery robots, and the less glamorous machines that already do useful work at scale.
- Robotics companies. Who is building what, how they are funded, which partnerships are pilots and which are contracts, and how product claims hold up over time.
- ROS 2 and robot software. The Robot Operating System ecosystem, middleware, simulation, perception and planning stacks, and the tools developers actually use.
- Autonomy. How robots perceive, decide and act without constant human input, and where human teleoperation still fills the gaps.
- Careers. Skills, roles and paths into robotics engineering, research and operations, written for people trying to break in or move up.
The Humanoid Robot Tracker
The tracker is our running record of humanoid robot programs. It lists companies and models along with what each one has publicly shown, claimed or delivered.
Every entry is backed by cited sources. We separate three things that press coverage often blurs together:
| Status | What it means |
|---|---|
| Announced | The company has described the robot or a plan, but has not shown it working in public. |
| Demonstrated | The robot has been shown performing tasks, in person or on video, with the conditions noted where known. |
| Deployed | The robot is doing work for a customer or in a real operating environment, as confirmed by the company, the customer or credible reporting. |
When a claim cannot be verified, we say so. When a company updates its plans or a deployment turns out smaller than first reported, we update the entry.
How We Separate Progress From Hype
Skepticism here is a working method, applied to every story. In practice that means:
- We go to primary sources first. Company filings, technical papers, official documentation and on-the-record statements carry more weight than social posts and recycled headlines.
- We grade our sources. Official announcements, proven reporters, community findings and anonymous claims are not equal, and we phrase each claim to match the strength of the evidence behind it.
- We ask what a demo leaves out. Was the robot teleoperated? Was the video sped up? How many attempts did it take? What happens outside the controlled environment? If those answers are unknown, we point that out.
- We distinguish pilots from production. A single robot in a customer facility is a test. A fleet doing paid work is a business. Both are worth covering, and both deserve accurate labels.
- We correct mistakes openly. If we get something wrong, we fix it and note the change.
Who This Site Is For
We write for engineers, students, investors, journalists, operators and curious readers who want an accurate picture of where robotics stands today. You do not need a robotics degree to follow our coverage. We explain technical terms when they come up and skip the jargon when plain language works better.
Independence
RWT Robotics is a new, independent publication. Coverage decisions are editorial. No company pays to appear in the tracker or to shape how we report on it.
Not Affiliated With the Robot Web Tools Project
RWT Robotics operates at robotwebtools.org, but we are not affiliated with the open-source Robot Web Tools project. That project maintains roslibjs and related libraries for connecting web applications to ROS, and its official home is on GitHub.
We have no connection to its maintainers or contributors, and we do not speak for that project. If you are looking for roslibjs documentation, source code, issue tracking or releases, go to the project’s official GitHub organization.
We do cover ROS 2 and the wider robot software ecosystem as journalists, which can include open-source tools like these. When we write about them, we write as an outside publication.