C2-ready for every buyer —
without rebuilding for each deal.
Write one adapter. Reach every C2. Musubi is the neutral, open-source layer that turns your UAV, USV, UGV or AI-sensor's telemetry, tracks and AI outputs into mission-ready evidence — delivered in each C2's native form, and built to prove how your platform holds up under comms loss and GPS degradation. Open and neutral — so no single C2 vendor locks you in.
The integration tax: N platforms × M C2 systems
No C2-readiness, no deal
Interoperability with existing C2 is becoming a procurement gate. Platforms that aren't C2-ready get screened out — and every new market you export into adds another C2 to satisfy. Worse, makers have no objective way to prove how a platform holds up under comms loss and GPS degradation.
You build platforms, not C2
You want to sell your vehicle or sensor — not build a command system. But every buyer asks the same question: how does this connect to our existing C2?
Rebuilt every deal
Today that means hand-writing a new integration for each C2. N platforms times M C2 systems is a bespoke, rebuilt-every-PoC tax — and the deeper you go through proprietary APIs, the worse the lock-in.
Interoperability is the bottleneck — and defense budgets are surging.
Europe is mobilizing for defense at historic scale — the European Commission's ReArm Europe / Readiness 2030 plan targets up to €800 billion — and Japan has publicly stated it will grow defense spending. As budgets rise, the constraint shifts from buying platforms to making them work together. C2-readiness is becoming the gate, and the makers that clear it first win the deals.
ReArm Europe / Readiness 2030 — European Commission, 2025
Connect once. Normalize every mission.
Write one adapter against Musubi's canonical schema, and your platform is built to reach every supported downstream C2 through the same evidence-backed output — no per-C2 rework.
- 01
Connect once
One adapter from your platform into Musubi.
- 02
Musubi normalizes
Into read-only, evidence-backed claims — never commands back to your vehicle.
- 03
Every C2 receives it
Delivered to each C2 in its own native form.
- MAVLink · PX4 · ArduPilot
- ROS2 · DDS
- RTSP · ONVIF
- MQTT · REST
- Vendor SDKs · GCS logs
- DELTA
- NATO MIP
- TAK
- SHIELD
How you plug in — one adapter, delivered to every supported C2· roadmap
Enters thin — software, not a box
Musubi is software (a container) that rides on your existing companion computer, GCS or server. No dedicated hardware, no platform redesign.
One canonical model
One capability-based adapter set normalizes common stacks (MAVLink/PX4/ArduPilot, ROS2/DDS, RTSP/ONVIF, MQTT/REST, vendor SDKs, GCS logs) into a single object model — so a degraded asset still reports “comms degraded, sending event summary” instead of dropping off the map.
Read-only by design. Hostile inputs assumed by default.
- Read-only by design, deny-by-defaultREAD-ONLY
- Musubi cannot command your vehicle or sensor. Write and control permissions are denied unless explicitly declared, and any adapter requesting write or control access fails the default policy. Integrating Musubi adds no write or control surface to your platform.
- Untrusted by designUNTRUSTED
- Musubi assumes hostile, malformed and misleading inputs — spoofed telemetry, replay, stale data, prompt injection — and runs schema, signature, provenance and anomaly checks before anything becomes a Claim.
- Signed is not trustedVERIFY
- Origin signing proves where a message came from, not that it is true. Musubi adds replay, time-drift, impossible-movement and cross-sensor contradiction checks on top, and flags risk rather than asserting authenticity.
- AI outputs are claims, not commandsCLAIM-ONLY
- Your edge-AI detection is delivered as a confidence-tagged Claim with its model identity and known failure modes — attributable and consumable, never given authority and never presented as truth. Examples and demos use mock data only.
Musubi makes the Claim. Your C2 makes the call.
“I saw it / it looks like this / here is the evidence / here is the confidence / here is the risk.” Musubi states what it observed, with provenance and confidence — and stops there.
Adopt, hold, discard, approve, who-sees-what, which-mission — the judgement stays with your existing C2, or a planned downstream trust layer such as KECKU's own Raijin (roadmap). Musubi proposes; it never decides.
What Musubi is not
Read-only is why Musubi can sit in front of any C2 without becoming a rival to it — neutrality and the kill-chain boundary are the same property. Musubi proposes claims; your C2 decides.
Roadmap · On the roadmap: each Claim travels inside an open, portable, signed Evidence Envelope — source and adapter identity, confidence, provenance and risk flags — so your output stays auditable and a customer's exit is never a full rewrite. Where a downstream C2 can't carry the trust metadata, confidence and provenance are marked, never silently dropped.
Built for degraded links — and made provable
DDIL-native
Your data survives comms loss and intermittent links — store-and-forward, differential sync, dedup-on-resend and clock-skew detection keep original timestamps and provenance intact.
Failure is a first-class object
roadmapComms loss, GPS degradation, video latency and false detections are recorded, not silently dropped — so they become demonstrable, comparable data instead of unknowns.
Adversarial eval & replay
roadmapA planned eval/replay harness (roadmap) injects comms loss, GPS jumps, fake and replayed telemetry, video delay and metadata prompt-injection, then produces a comparable report — the objective harness makers otherwise rebuild deal by deal. Design partners help shape it and get first access.
Prove resilience once and reuse it across buyers — mission logs, evidence and degraded-comms behavior become selling points instead of unknowns. (Eval and AI-claim examples use mock data; no models are trained on real, operational or classified mission data.)
Your door to JapanReach every major C2 — including a documented door into Japan
Against the backdrop of Japan's publicly stated direction to grow defense spending, integration demand is rising. KECKU is your partner on the ground in Tokyo, and Musubi is your documented door to SHIELD — a Japanese C2 Musubi is built to deliver into — so your platform can arrive C2-ready and PoC-ready.
Neutral by structure: open-source governance and a conformance suite keep Musubi a shared standard, not a walled garden. DELTA, NATO MIP, TAK and SHIELD are destinations Musubi is designed to deliver into — partnering with us does not hand your roadmap to any one C2 vendor.
A team at the intersection of AI, finance and government technology — building the interoperability layer in the open.
MSc Banking & Finance, King's College London. Founded a fintech startup; has built AI pipelines for government agencies and ML-based financial optimization.
BSc Mathematical & Computing Science, Tokyo Institute of Technology. Led business development and M&A in financial IT at Finatext.
Be first in line
Get early access the moment Musubi opens, design-partner priority, and a direct line to the team. Tell us what you build and which C2 you're targeting — we'll prioritize your connectors first. No mission data, no connection secrets, no commitment.
- Your connectors built first
- Help shape the eval/replay harness — and get first access (roadmap)
- A C2 connector demo built for your stack