Kibitek Revamps HATS Robot Control Software, Adds Standard, Pro and SDK

prtimes.jp reported on September 14, 2026, “Kibitek Revamps HATS Robot Control Software, Adds Standard, Pro and SDK.” We have not been able to verify the primary source, so please refer to the original for details.

Kibitek’s announcement points to a model in which robot deployments are offered not just as individual machines, but as a combination of integrated control software and a development platform. The Standard, Pro and SDK tiers the company announced reflect differing requirements for on-site operations, in-house development and systems integration projects. This means adopters must choose a control layer, not simply purchase a robot.

What is new in this announcement is that HATS is no longer being offered only as a standalone product: its three tiers—Standard, Pro and SDK—differentiate users by role. The basic concept of HATS remains unchanged: vendor-neutral integrated control of robots from different manufacturers. But with Pro’s fleet control and the addition of the SDK, the offering creates separate entry points for operators, developers and systems integrators. A related article from this newspaper, Kibitek Reportedly Equips AMRs With Remote Control System, described Kibitek’s use of remote control on individual robots. This announcement can be read as an extension of that effort, broadening the focus from individual AMRs to a product lineup that includes integrated control of equipment from different manufacturers and fleet control. However, the announcement alone does not clarify which HATS tier includes remote-control functions or how the technology differs from what was previously reported. The industry significance lies in the shift away from competition over robot performance toward how multiple devices at a site are coordinated. HATS is presented as a connection layer that includes links to WMS, WCS and equipment such as elevators, as well as AI integration. This suggests that bottlenecks in robot deployments are shifting from individual machines to integration with surrounding systems. The separation of scenario counts and fleet-control capacity between Standard and Pro appears intended to distinguish single-use deployments from those involving multiple robots. Unresolved questions include the price of each tier, the number of units deployed in actual operations, the range of supported robots, the development workload involved in using the SDK and actual demand for AWS HATS. The announcement also does not show how deployments will be divided between factories and logistics, and inspection and security.

With HATS emphasizing integrated control that includes WMS/WCS and links to equipment, the relative importance of integration with surrounding systems, systems integration and maintenance—areas often considered strengths in Japan’s robot deployments—could increase. Conversely, supplying robots alone may not be enough; companies will be judged on their ability to provide control software and operational design as well.