Musubi
Data you connect once keeps working elsewhere.
What your drones and sensors capture should reach farm management, inspection reporting and disaster-response picture alike — the same observation, delivered without rebuilding the path every time a system changes. Musubi is the interoperability core for that. For agriculture, inspection, logistics, disaster response and industry — and it never commands your platform. Coming soon.
You can also ask for a walkthrough, or to join as a design partner — same form.
Problem
Every connection starts from scratch
The number of devices in the field keeps growing, but what comes off them still is not in a shape the systems above can use. Add one more platform, add one more destination, and you write the integration from scratch again — and that repetition is what stops the data you already captured from being used.
Connecting is not the end of it either. You can translate a protocol and still hand over something unusable, because units, frames, time and missingness were never aligned — and that loss raises no error at all. You find out after a decision has gone wrong.
Design principle
N × M → N + M + E + F
With N kinds of platform and M kinds of destination, the straightforward path leaves you maintaining N×M integrations. Musubi moves that toward N adapters and M adapters maintained independently, plus pair-specific exceptions E and shared fixed cost F.
Approach
Move N×M toward N+M
Maintain N adapters on the source side and M on the consumer side, independently. With pair-specific exceptions as E and shared fixed cost as F, the design goal is to move the total from N×M toward N+M+E+F.
E must not swell as the pairings multiply. That is what decides whether this design holds.
One adapter, many consumers — adding a consumer does not change the source side
Write one adapter from your platform or sensor into Musubi, and add consumers from there. Musubi normalises the meaning — units, frames, time, missingness and confidence become explicit, and what was lost stays visible as lost. The same observation then reaches farm management, GIS, maintenance, inspection reporting and generic data platforms, so adding a consumer never sends you back to the source side.
Who it's for
What changes depends on where you sit
If you build the platforms — UAVs, USVs, UGVs or components — the adapter you rewrite for every buyer becomes one adapter you maintain on your own side. If you integrate other vendors' equipment, the reconciliation that eats your schedule shrinks, because meaning arrives with units, frames, time and missingness already explicit. And if you fly and operate in the field, the data you've been re-keying or carrying on a USB stick arrives in a shape your existing farm management, GIS or maintenance system can take.
In every case, Musubi never commands your platform. It handles information only.
Capabilities
From connected to actually usable
Musubi connects over MAVLink / ArduPilot, ROS 2 / DDS, video, MQTT / REST, vendor SDKs and logs, then normalises per-model differences into a shared schema. Anything that fails schema validation, or whose confidence cannot be established, does not pass downstream unmarked.
What does pass carries its provenance and transform history with it, and fans out into each consumer's own format. It is built for connectivity that drops, so you can tell when something was lost — which matters here as much as not losing it.
By design, we don't
What a system refuses to do matters more than what it can do
Musubi is an information-plane interoperability core. These constraints are fixed at the requirements level and are not broken at any layer of the implementation.
It does not originate, carry or execute commands or tasking
Control and approval stay with your existing C2 or GCS.
AI output carries no authority
What a model produces is a candidate, not an instruction and not the truth. It is isolated and kept with its provenance.
It does not replace your C2, flight controller or GCS
Observe, wrap and integrate come first.
It stays out of the control loop
Information plane only.
A signature is not proof of truth
Where data came from and whether it is correct are treated as separate questions.
Status
Where it stands, on the way to release
Musubi is coming soon. It runs today on simulation and recorded data, and we are working through real connections with design partners.
The generic core will be released under an OSI-approved licence. The condition for that release is that a third party can build, test and maintain adapters from public artefacts alone. For defence use the same core is provided under a controlled profile; the public product's centre of gravity is civil and industrial.
Get in touch
Start with the announcement. Talk to us any time
We'll send word when it's available. We're glad to walk you through it sooner, and we're looking for design partners to test it against a real integration. Pick whichever applies below.
Yusuke Arai reads every message personally. We won't use this for sales outreach.