Skip to content
TrustList
Funding news

QibiTech raises about ¥600 million Series B for HATS, software that makes different makers’ robots work together

Editorial

By TrustList Editorial

Tokyo company QibiTech announced a Series B of about ¥600 million in late September 2026 for HATS, vendor-neutral software that controls robots from different makers and links them to warehouse and factory systems.

About QibiTech raises about ¥600 million Series B for HATS, software that makes different makers’ robots work together

QibiTech raises about ¥600 million Series B for HATS, software that makes different makers’ robots work together

30 September 2026 — QibiTech, a company based in Shinagawa, Tokyo, announced a Series B round of approximately ¥600 million (約6億円) through a third-party allotment of shares, according to its own release on PR TIMES. The Bridge reported the round on 1 October 2026.

The round

  • Amount and stage: about ¥600 million, Series B.
  • Investors named by the company: JIC Venture Growth Fund No. 2, an existing shareholder investing again, and SVP Open Innovation Fund No. 1, run by Sumisho Venture Partners.
  • Use of the money: to strengthen development of its HATS product and its sales organisation, including hiring.

What the company does

Warehouses and factories increasingly run robots from several manufacturers, such as autonomous mobile robots, robot arms and automated storage, each with its own controller. QibiTech's HATS is vendor-neutral control software that integrates these robots and connects them to the warehouse management system (WMS) or manufacturing execution system (MES), so that tasks can be assigned across a mixed fleet. It is offered in Standard, Pro and SDK editions.

Why it matters for buyers

Logistics operators in Japan face labour shortages, and the 2024 limits on truck drivers' overtime put further pressure on warehouse productivity. Many sites want to add robots step by step, from different vendors, without being locked into one maker's ecosystem. Integration software that sits between robots and the WMS is meant to make that possible.

What to check

  • Logistics and plant engineers should ask which robot makers and models HATS already supports, how new ones are added, and who is responsible when a robot and the software disagree.
  • IT should check the interface to their specific WMS or MES and the on-site or cloud deployment options.
  • Procurement should compare the licence and integration cost against single-vendor fleet managers.

Sources

Categories & features