# ROS Robotics Companies Directory: Vendor Discovery and Data Cautions > vmayoral/ros-robotics-companies is a public directory of organizations known to use ROS or ROS 2, organized by company and selected technical application areas. It helps engineers find possible vendors and integration partners, but individual entries need verification before use in technical or procurement decisions. **vmayoral/ros-robotics-companies** — A list of robotics companies using the Robot Operating System (ROS and ROS 2). - Repository: https://github.com/vmayoral/ros-robotics-companies - Stars: 1,893 · Forks: 235 - Language: Shell - License: not declared - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/vmayoral-ros-robotics-companies ## What vmayoral/ros-robotics-companies Actually Provides vmayoral/ros-robotics-companies addresses a discovery problem: identifying organizations connected to the Robot Operating System ecosystem. The README says the list covers companies known to use ROS or ROS 2, or related tools, in product development, service delivery, or shipped products. It is aimed at engineers and other readers who need names to investigate, potential technology partners, and companies with robotics software experience. The project is not a ROS distribution, runtime, package registry, or application framework. Its main reader-facing artifact is a table in `README.md`, containing company names, descriptions, founding years, and links to outside pages or repositories. The README separates active companies from organizations described as acquired, closed, or inactive. It also provides sections for navigation, manipulation, and perception. That distinction matters when evaluating the directory. A listing can identify a company worth researching, but the row alone does not establish that a product remains supported, which ROS distribution it targets, whether an integration is production-ready, or whether a driver works with the intended platform. Company descriptions often link to driver repositories, product pages, job advertisements, or technical case studies. Those linked sources carry more specific information, but the directory does not apply a uniform evidence or compatibility schema to every entry. ## How the Company Table and Technical Indexes Work The visible repository layout places the directory content in `README.md`, with supporting entries under `.devcontainer/`, `.github/`, and `scripts/`. The README acts as the discovery interface. It presents companies alphabetically and provides navigation anchors for active organizations, inactive or acquired organizations, contribution instructions, and selected ROS application areas. Rows combine several forms of evidence. ACEINNA is linked to `aceinna_openrtk_ros_driver`. Accerion is linked to `accerion-ros-node`, described as a ROS driver for its Triton positioning sensor. ADLATUS Robotics is linked to `adlatusrobotics`, identified as a source for ROS 2 drivers. ADLINK Technology is associated with a visual SLAM navigation solution and `Adlink-ROS/navigation2`. These are useful entry points because they connect a company name to a specific technical artifact. Other entries describe broader capabilities. Acceleration Robotics, for example, is presented as providing hardware acceleration solutions for robots using ROS 2, including FPGA and GPU tools and ROS 2 API-compatible intellectual property. ADINKRA is described as having built a real-time perception system for object tracking with drones on ROS 2. The table therefore supports both product-oriented research and ecosystem mapping. The navigation, manipulation, and perception indexes are discovery filters rather than technical certifications. An appearance in one category does not specify a ROS release, target operating system, sensor model, control-loop latency, or production deployment status. The README does not provide a structured compatibility matrix for those attributes. ## What Company Entries Prove About ROS Usage An entry can establish that the maintainers associated a company with ROS or ROS 2. It cannot automatically establish the depth of that relationship. Some descriptions concern a public driver, while others refer to internal use, consulting, navigation hardware, deployment work, or recruitment. Those situations carry different implications for an engineer. A public driver link offers the clearest starting point for technical inspection. The `aceinna_openrtk_ros_driver` repository, for example, can be checked for package metadata, ROS interfaces, dependencies, and compatibility documentation. The same approach applies to `accerion-ros-node` and the ADLATUS Robotics repositories. The directory itself does not reproduce those technical details, so any assessment depends on the current content of the linked repository. A product page is useful for determining whether ROS support is part of the shipped product or only an internal development tool. A job advertisement may suggest that a company recruits engineers with ROS experience, but it does not identify a supported package or customer-facing interface. A technical case study can describe a deployed ROS 2 system, but its scope may apply to one customer project rather than the company's complete product range. Engineers should ask four separate questions. Does the organization use ROS internally, or does it expose ROS in a product? Does the claim concern ROS, ROS 2, or an unspecified related tool? Is the named driver or product still available? Is there enough public documentation to reproduce the integration? The README can answer different parts of those questions for different entries, so treating every row as equivalent would overstate its value. ## Starting Research from README.md Without Installation The README does not document an installation or setup process for vmayoral/ros-robotics-companies. This is consistent with the repository's role as a list rather than an executable ROS tool. There is no documented command for installing the directory as a package or generating the company table. The first real use begins with `README.md`. If the task concerns a particular technical domain, use the navigation, manipulation, or perception anchor to narrow the company table. For broader vendor discovery, scan the alphabetical active-companies section. Read the description for the company's claimed ROS relationship, then follow its linked company page, driver repository, or technical project. After opening a technical link, inspect its package manifests, supported platforms, ROS dependencies, build instructions, and recent maintenance state. For a company-only entry, verify whether ROS support belongs to a current product and whether the linked statement is still present. Those checks must happen outside this directory because it does not define a common metadata format for package versions or deployment compatibility. The repository contains `scripts/`, `.github/`, and `.devcontainer/`, indicating that the project has supporting automation or development configuration. However, the README does not document commands that operate on those directories, so there is no verified command-line workflow to include. Readers seeking package-level instructions should move from this company index to the driver's own repository. ## Limits of the Directory for Compatibility and Procurement The central limitation is the difference between ecosystem association and procurement-grade evidence. Inclusion means the maintainers list an organization as known to use ROS, ROS 2, or related tooling. It does not state the supported ROS 2 distribution, target operating system, sensor compatibility, real-time behavior, license, test coverage, or support period. Entries also depend on outside links. A company page can change, a repository can be archived or renamed, and a driver can evolve after its directory entry is written. The repository has no GitHub releases, so it offers no documented release channel through which readers can correlate directory changes. The current state of each company claim needs direct verification. The directory is the wrong tool for selecting an individual ROS package by version or capability. It does not document dependency resolution, package maturity, supported hardware, or deployment conditions. A team choosing a driver should use the driver's repository and documentation. This project works earlier in the process by mapping organizations and their technical entry points. There is also a licensing boundary. The repository's license is listed as unknown, and the README does not state a license identifier. Reading or linking to the directory does not answer whether its table text can be copied, transformed, or redistributed. Check the repository's license files directly before reusing substantial content. This is a repository-license question, not a legal conclusion about linked company projects. ## Maintenance, Alternatives, and Appropriate Use The repository is not archived, and its last push was on 2026-09-02. That date indicates recent activity for the directory itself, but it does not establish the maintenance state of every listed driver, company, or product. There are no GitHub releases, and the README does not document a versioned upgrade policy for the directory. A real alternative is the official ROS package ecosystem combined with each component's own repository. A package repository is the better source when the decision concerns build instructions, dependency declarations, ROS interfaces, supported platforms, releases, or license text. vmayoral/ros-robotics-companies is better for the earlier question of which organizations use ROS or ROS 2 and what related technical resources they publish. One approach organizes evaluation by company; the other organizes it around a specific software component. The two sources should not be treated as substitutes. A company row can reveal a driver, while the driver repository can establish the technical facts needed for adoption. Conversely, a package repository may exist without a clear indication that its maintainer sells products or provides commercial integration. Use the directory for ecosystem discovery, then use component sources for compatibility and maintenance checks. ## Conclusion Adopt this directory when you need a broad map of organizations associated with ROS or ROS 2, especially for vendor discovery across navigation, manipulation, perception, drivers, and hardware. Do not use it as the sole basis for selecting a package, assuming current compatibility, or confirming that a vendor supports a product. Verify the entry's linked source first, then check the ROS generation, supported platforms, license, and maintenance status there. The directory's last push was on 2026-09-02, but that date does not certify the freshness of every linked organization or driver. ## FAQ ### What is vmayoral/ros-robotics-companies used for? It is a public directory of companies known to use ROS or ROS 2, or related tools, for products, services, or development. It helps readers discover organizations and technical resources connected to the ROS ecosystem. ### Does vmayoral/ros-robotics-companies install ROS? No. The repository is a company list, not a ROS distribution or runtime. The README directs readers to company entries and their linked sources rather than documenting installation of this repository as software. ### Can vmayoral/ros-robotics-companies determine ROS 2 compatibility? Not by itself. The directory associates companies with ROS or ROS 2, but its table does not provide a complete compatibility matrix for distributions, operating systems, sensors, or deployment environments. Check the linked company or repository documentation for those details. ### Is vmayoral/ros-robotics-companies actively updated? The repository is not archived, and its last push was on 2026-09-02. That does not confirm that every company entry or linked driver is current. ### Can I reuse the contents of vmayoral/ros-robotics-companies? The repository's license is listed as unknown, and the README does not provide a license identifier. Check the repository's license files before copying or redistributing substantial directory content. ## Sources - [Issues](https://github.com/vmayoral/ros-robotics-companies/issues) - [README](https://github.com/vmayoral/ros-robotics-companies/blob/main/README.md) - [vmayoral/ros-robotics-companies on GitHub](https://github.com/vmayoral/ros-robotics-companies) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/vmayoral-ros-robotics-companies