Liberaware: indoor inspection aircraft and industrial data services

Liberaware sells access to places that conventional infrastructure inspections struggle to observe, then helps customers turn the resulting imagery into maintenance information. Its commercial proposition combines small indoor aircraft, operated inspection services and data processing. The useful buyer question is whether a project needs an aircraft, an inspection team or a persistent record that several engineering departments can use.

The business is based in Chiba, Japan, where Liberaware was established in August 2016. Its corporate profile lists 128 people at 31 January 2026, including temporary and dispatched workers and excluding part-time directors. This is a dated company workforce measure, not a current count of permanent engineers. Its investor stock information identifies the listed issuer as Tokyo Stock Exchange Growth code 218A, with an August-to-July financial year.

Financial scale and the mix behind the aircraft

Liberaware’s FY2025 annual securities report records consolidated revenue of ¥1.407 billion for the year ended 31 July 2025. The underlying reported amount is ¥1,406,949,000. Consolidated net profit attributable to owners was approximately ¥46 million. The report is the company’s first year of consolidated financial statements, which matters when comparing older standalone figures with the group.

The third-quarter FY2026 results show a different financial position: ¥1.217 billion of consolidated revenue and a ¥1.970 billion operating loss for the nine months ended 30 April 2026. Those are interim actuals, not a completed financial year. The revenue table separates aircraft-related products and inspections from data processing, digital-twin platforms and solution development. Product sales represented approximately ¥448 million, while commissioned solution development contributed approximately ¥306 million.

That mix changes the partnership discussion. A distributor of finished aircraft and an engineering company commissioning development can contribute to different revenue streams, with different delivery obligations. A supplier evaluating a long integration project should therefore identify the relevant business team and funding arrangement. The latest published interim loss also makes payment milestones, support continuity and ownership of completed deliverables more consequential than a simple comparison of annual sales totals.

IBIS2 Chainage moves attention towards the inspection record

Liberaware’s 24 July 2026 IBIS2 Chainage launch illustrates the direction of product development. The sewer-inspection model, also called IBIS2-C, adds functions for recording distance and estimating defect dimensions from captured footage, alongside inspection-report output.

The release draws a specific upgrade boundary. Distance and measurement functions depend on footage captured with IBIS2-C; the reporting-software update is also available to existing IBIS users. An installed customer seeking easier report preparation therefore faces a different purchasing decision from one requiring the new measurement capability. The latter should establish which aircraft and capture process are included in the proposed package.

For a hypothetical sewer-maintenance contractor, a good demonstration would follow one observed defect from video to its location reference, measurement and exported report. An impressive flight through a pipe would leave the central commercial question unanswered if the maintenance team still had to reconstruct those relationships manually. Conversely, a reliable report workflow could be valuable even on projects where the customer needs only limited new measurement functionality.

The output also needs a defined recipient. A contractor may deliver an inspection record to a municipality, another engineering consultant or its own repair-planning team. Each arrangement changes who specifies the report fields and resolves uncertain observations. The aircraft’s ability to enter a space does not itself decide whether the resulting evidence is sufficient for that customer’s maintenance decision.

Buying a service and developing an internal operation

The published implementation plans offer an operated inspection service with equipment, a pilot approved by Liberaware and video delivery. Orthophotos, three-dimensional models and point-cloud outputs are optional services priced for the project. The company also presents purchase and rental routes, supported by training and equipment support.

This creates a meaningful choice between recurring access to a service and building an internal inspection capability. Consider an infrastructure owner with one unusual, difficult-to-access structure and another with repeated inspections across similar facilities. The first may find that a defined service deliverable is the practical starting point. The second can evaluate whether its own staff can maintain proficiency and whether the equipment will be used often enough to justify managing it internally.

A comparison should keep the data deliverable constant. Comparing the price of an aircraft with the price of a fully processed inspection package obscures the work that remains with the purchaser. A useful quotation separates capture, interpretation, processing, reporting and subsequent access to the results. Liberaware’s published options provide a basis for that conversation without implying that every project includes every data product.

JR Central shows why the customer’s staff matter

A JR Central case study describes the Kansai branch’s use of IBIS2 since 2024 to inspect viaduct structures concealed above station ceilings on the Tokaido Shinkansen. The customer combines captured footage with CalTa’s TRANCITY platform. Trained railway employees operate the aircraft, allowing people with knowledge of the structures to direct the inspection and assess what they observe.

The case describes three-dimensional information helping departments understand the relationships between structures, pipes, cables and other equipment. It also reports reduced exposure to difficult access work. These are customer-specific observations presented in Liberaware’s case study; they are more informative than assuming the same savings for every facility.

There are two distinct relationships here. Liberaware’s corporate history identifies CalTa as a venture established with JR East group companies. JR Central is the customer in this particular inspection account. Conflating those railway groups would obscure both the ownership relationship behind the software and the separate evidence of customer use.

For an integration partner, the notable feature is the handover between professions. The pilot’s recording becomes something a structural specialist and an electrical or building-services colleague can discuss together. A proposed add-on should improve that exchange: for example, preserving the connection between an observation and the corresponding location in the shared model. Selling an additional sensor without specifying its contribution to that workflow would offer a less complete proposition.

Chiba provides a recent example of commissioned work

Liberaware’s 1 September 2026 account of a Chiba drainage survey says the city commissioned the company to inspect approximately 750 metres of covered drainage channel on 27 August. The work followed heavy rain earlier that month and used IBIS2 Chainage. The company explicitly identifies it as commissioned work; the announcement does not disclose a contract value.

A practical acceptance conversation could therefore use a sample channel segment: can the city locate each observation, understand the survey’s coverage and pass the record to the team responsible for remedial work? That is a concrete service outcome to specify before expanding the survey.

This is a different demand pattern from scheduled railway inspections. A storm-related survey requires a prompt view of a specific asset, while a repeat inspection programme must preserve useful comparisons across visits. Both can use indoor aerial capture, but the purchasing organisation’s immediate decision differs. For the city, the practical value lies in evidence that helps determine the condition and next treatment of the affected drainage route.

Readers comparing ACSL’s industrial aircraft business and Skydio’s inspection-oriented autonomous systems can place Liberaware around this particularly focused combination of confined-space access and infrastructure records. A useful shortlist should begin with the asset, the people who will inspect it and the information they must deliver. Liberaware’s strongest public examples connect those three elements through a specific customer workflow.