What If The Missing Tool Is Less Lethality?

When a drone carries something unknown, when a spill zone is unsafe, when a responder has to choose between waiting and walking into danger, the answer should not always be a bigger weapon or a braver human.

Wiewiorka Works builds robotic systems for the space between threat and responder.

Machines go first.
Humans stay in command.
Evidence is preserved.
Risk is contained.

The ecosystem combines ground robots, field controls, sensor platforms, passive detection, command software, and capture-focused aerial systems. Its purpose is not escalation. Its purpose is reach: to let trained operators and incident commander see, decide, contain, and recover before people enter the danger zone.

In a world racing to automate force, Wiewiorka Works is building tools for supervised restraint.

But all of this only matters if it can be built, repaired, trusted, and sustained in the field - even when resources are limited.

The Tools We Are Building

Ed-Remote

(Field controller and mission HUD) TRL 5-6

Ed-remote is a field controller and mission HUD designed for intuitive, safety-focused operation of heterogeneous robotic assets. It provides a unified control and monitoring environment for Kagura, YATO-Umbrella, Okita, and future systems.

The platform supports dual-mode interaction through a touchscreen HUD, low-latency nRF24 control links and long-range LoRa telemetry.

Hot-swappable batteries and modular enclosures enable extended operation and rapid field servicing.

Status: Operational - core system, actively used

Key characteristics:

Arduino Mega + Raspberry Pi architecture with a deterministic MCU safety layer
Processing-based HUD/UI with multiple video and operational modes
nRF24 low-latency control with LoRa E32 long-range telemetry
Structured NDJSON telemetry and role-separation logic
Jetson-based MJPEG streaming bridge for sensor video distribution
Map stack powered by MapTiler with multi-layer situational overlays
Five data overlay buttons: FIRES, RAD, AIRQ, DRONE, FLTS - four operational, one in development
Hardware and software DISARM logic with operator-side safety gating

Operational situational overlays:

NASA FIRMS (fire detection - VIIRS SNPP/NOAA-20/NOAA-21 satellites, API key required)
radmon.org (ionizing radiation - global citizen Geiger counter network, ~320 live stations, no key required)
OpenAQ (air quality - PM2.5, O₃, NO₂, SO₂, CO monitoring stations, API key required)
OpenSky Network (live ADS-B aircraft transponders with altitude/heading/squawk, no key required)

Not yet installed (design in progress / funding stage):

FlytBase (drone fleet tracking - API key reserved, UI stub present)
NASA Black Marble nighttime lights (via GIBS and Earthdata analytics)
Dedicated Incident Commander interface (architecture present, UI under active development

Kagura

(Unmanned Ground Vehicle Platform) TRL 5-6

Kagura is a heavy-duty unmanned ground vehicle developed for logistics, sensing and containment tasks.

Its skid-steer architecture supports high payload capacity across uneven terrain.

A modular chassis exposes standardized Ethernet, HDMI, and USB interfaces for rapid sensor and payload integration, including gas panels, imaging systems, and environmental instruments.

Power modules are hot-swappable to support extended missions and rapid turnaround.

Kagura currently operates in manual and supervised modes, with autonomous functions planned.

Status: Operational prototype, expanding capabilities

Key characteristics:

Modular skid-steer UGV with hot-swappable power
Deterministic safety MCU layer
Actively driven and field-tested
Intended logistics, carrier, and containment roles
Jetson companion computer
Designed for shielded transport and enclosure workflows
Mechanical and electrical architecture in place
360-degree camera system
LiDAR
Dedicated onboard Jetson compute

Not yet installed (design in progress / funding stage):

Geiger counters, multi-channel gas sensing, PM monitoring
Long-range or satellite backhaul
SLAM and navigation autonomy stack

YATO-Umbrella

(Sensor, Actuation and Turret Platform) TRL 5-6

YATO-Umbrella is an articulated, safety-focused turret and sensor platform intended for persistent observation, stabilized actuation and close-range intervention tasks.

Stepper-driven axes with slip rings allow continuous multi-axis motion.

The system integrates RGB and thermal sensing, AI-assisted detection gates and independent hardware inhibit paths.

Design emphasis is placed on mechanical restraint, misuse resistance and predictable failure behavior.

Planned sensor suites include radiation, gas and particulate monitoring, supporting continuous observation of sensitive or high-risk environments.

Status: Operational prototype, safety-focused configuration

Key characteristics:

Multi-axis turret with stepper and servo actuation
Jetson companion computer
RGB and thermal video streaming
Non-contact human vital-sign radar research mode
EMI-aware behavior (motor inhibit during radar scans)
Independent hardware and software DISARM pathways
Mechanical safety and misuse-resistance design

Not yet installed (design in progress / funding stage):

Radiation, gas and particulate sensor arrays

Intentionally absent:

Electronic countermeasures without appropriate licensing
Any lethal hardware

MAGI + SIBYL

(Incident Commander Interface and Mission Coordination Dashboard) TRL 3-4

MAGI + SIBYL is a command-layer software interface for supervised multi-asset robotics, incident coordination and mission planning.

It provides an Incident Commander view above direct operator control, combining robotic assets, detected tracks, operators, planned routes, environmental overlays and event logs inside one 3D/2D map-based dashboard.

The system is designed for human-confirmed workflows: detection, assignment, route planning, recovery coordination, environmental risk review and high-consequence action authorization.

Design emphasis is placed on situational awareness, mission traceability, conservative decision support and clear separation between advisory analysis and human command.

Status: Functional software prototype, simulation and integration stage

Key characteristics:

3D/2D mission map with robotic assets, operators, tracks and assignment lines
Incident Commander view separated from direct operator control
Detection, tracking, intercept and recovery workflow visualization
Kagura waypoint planning for recovery, inspection and containment tasks
Route generation for ground assets using road or walking-path geometry
Public-data overlays for environmental and airspace context
Event log and visible mission-state traceability
Human authorization workflow for high-consequence actions
Advisory analysis layer for decision support, not autonomous command
Designed for simulation, evaluation and future supervised field integration

Implemented / supported APIs and services:

MapLibre / MapTiler - 3D map and operational map display
OpenRouteService - mission route generation for ground assets
NASA FIRMS / VIIRS - fire and thermal-event detections
OpenAQ v3 - air-quality station readings
Windy Point Forecast - wind and weather samples
Windy Webcams v3 - public webcam reference feeds
Radmon-compatible feeds - radiation monitoring layer
OpenSky Network - nearby aircraft / airspace awareness
ACLED - conflict and incident-event layer
GDELT - geolocated media and event-signal layer
Supabase - optional shared threat / collaborative data layer
DeepSeek, OpenAI, xAI/Grok and Anthropic APIs - optional multi-agent advisory analysis pipeline

Not yet installed / integration in progress:

Production-grade live robot telemetry bridge
Full field integration with Kagura, YATO-Umbrella, Okita and Shinpachi hardware
Direct hardware execution of all waypoint actions
Air-unit route planning beyond direct-line mission geometry
Hardened multi-user command authorization and audit system
Field-tested CBRN sensor fusion with robotic telemetry
Deployment-ready incident-command server infrastructure

Intentionally absent:

Autonomous lethal decision-making
Unsupervised high-consequence action execution
Electronic countermeasure control without appropriate licensing
Automatic engagement logic without human authorization
Any design path that removes human responsibility from command decisions

Okita

(Interceptor UAV) TRL 3

Okita is a modular, hybrid UAV platform designed for non-destructive interception of unauthorized drones, with a focus on safe capture and recovery.

It combines electric ducted fan propulsion for agile flight with a brief rocket boost capability for rapid response.

The system incorporates net deployment and redundant parachute mechanisms to enable controlled descents, prioritizing containment of potentially sensitive or hazardous payloads while minimizing risks during retrieval.

Status: Under active development

Key characteristics:

Non-lethal capture approach using net and parachute systems
Emphasis on safe recovery, evidence preservation and managed descent profiles
Hybrid propulsion for enhanced speed and maneuverability in interception scenarios
Modular, reusable architecture supporting field maintenance, quick resets and integration with supporting systems like Ed-Remote for command and Kagura for ground handling
Built with accessible civilian components to ensure compliance and repairability
Advanced multi-sensor suite (RGB + thermal cameras, IMU, GPS, precision altimetry, airspeed, environmental monitoring) enabling real-time navigation, targeting accuracy and situational awareness

Shinpachi

(Passive Detection Arrays) TRL 2-3

Shinpachi is an early-stage distributed sensing concept focused on long-range early warning and triangulation.

It combines passive RF monitoring and acoustic array principles to detect drone activity, spoofed control signals and anomalous aerial behavior.

Telemetry is designed to feed directly into Ed-Remote, enabling layered situational awareness and cueing of active platforms.

Status: Concept / early design stage

Key characteristics:

Passive RF array architecture
Acoustic detection arrays
Designed for long-range, low-cost distributed deployment
Target early-detection range: 5–10 km

Design / Standards

Built for Distributed Maker Sustainment

Wiewiorka Works platforms are designed to be manufactured, maintained, repaired, and scaled using tools and skills already present across Europe’s maker, robotics, drone, and small-batch fabrication communities.

Europe already has a broad technical base: more than two million registered drone operators, a rapidly expanding entry-level 3D-printer market, CNC hobbyists and small-batch fabricators, university engineering teams, and technical volunteer communities. Wiewiorka Works is designed to convert that existing capability into a practical sustainment advantage.

The platforms use printable structures, CNC-friendly parts, common fasteners, accessible electronics, shared power modules, reusable firmware patterns, and documented repair procedures. The goal is not improvised mass production by untrained users, but maintainability: trained local teams should be able to fabricate, inspect, replace, and repair selected components close to the point of need.

This follows a lesson visible in both historical distributed defense infrastructure and Ukraine’s drone and UGV development since 2022: readiness depends on local sustainment. Systems remain useful when trained people, spare parts, test equipment, repair routines, and fabrication capacity exist near the field environment.

Modular Architecture and Cross-Platform Reuse

Wiewiorka Works platforms are designed around modular, field-replaceable subsystems to simplify repair, reduce downtime, and reuse parts across the suite. Core modules - power distribution, compute, sensors, communications, and actuator I/O - can be replaced without board-level soldering or major reconfiguration.

Several components are shared across platforms. Arduino Mega 2560 boards currently provide the low-level safety and I/O layer on Ed-Remote, Kagura, and YATO-Umbrella. nRF24L01+ modules handle short-range command links, while LoRa E32 modules provide long-range telemetry where local spectrum rules allow. GPS, compass, IMU, and Jetson-class compute modules are reused where suitable, reducing the size and complexity of the spares inventory.

This shared architecture allows selected components to be reassigned between systems after configuration and functional checks. For example, if YATO-Umbrella’s compute module fails, a compatible module from Kagura can be moved to restore vision or sensor-processing functions, while Kagura continues in manual standalone mode using its low-level controller.

All platforms use common command payloads, telemetry formats, USB NDJSON data exchange, and a shared firmware structure. This lets technicians reuse diagnostic, firmware, and repair workflows across the suite instead of learning a separate maintenance process for each robot.

Okita is optimized separately for aerial size, weight, and power constraints, using lighter avionics and a higher-performance microcontroller while retaining compatible radio and telemetry formats. Ground systems keep the Arduino-based safety layer to prioritize accessibility, repairability, and separation between safety-critical control and higher-level compute.

Standards & Traceability

Wiewiorka Works maps selected design elements to relevant NATO STANAG concepts for prototype guidance, gap analysis, and future interoperability planning. These mappings are conceptual only. They do not imply certification, compliance, NATO affiliation, operational approval, or military endorsement.

Legend:

Aligned - Addressed by SOP design or architecture
Partial - Conceptually addressed; further work required
Planned - Not implemented; architecture prepared
Out of Scope - Intentionally excluded at this stage

STANAG 4586 - Standard Interfaces for UAV Control Systems

C2 system modularity: Aligned (via abstraction layer and middleware)
Standardized vehicle state reporting: Partial
Payload control abstraction: Aligned
Multi-vehicle control: Partial
External GCS interoperability: Planned
Operator role separation: Aligned (Operator vs. Incident Commander)

STANAG 4703 - Light UAS Airworthiness

Defined operational envelope: Aligned
Hazard identification & classification: Aligned (integrated with CBRN playbooks)
Fail-safe / fail-passive behaviour: Partial
Configuration control: Partial
Continued airworthiness monitoring: Planned

STANAG 4671 - UAV Airworthiness Requirements

Structured safety case: Partial
System redundancy philosophy: Partial
Verification & validation planning: Planned

STANAG 4811 - Sense-and-Avoid

Cooperative traffic detection: Partial
Non-cooperative detection: Partial
Collision risk assessment: Planned
Degraded mode declaration: Aligned
Airspace restriction enforcement: Aligned

STANAG 7023 / 4545 / 4609 - Imagery Formats

Standard imagery/motion packaging: Planned
Metadata and integrity: Partial / Aligned (hash-chained storage)

STANAG 4559 - ISR Library Interface

Indexing and retrieval: Planned
Product discovery: Planned
External interop: Out of Scope

STANAG 4774 / 4778 - Information Confidentiality Labeling

Labels and binding: Planned
Policy linkage: Out of Scope

STANAG 2290 - Unique Identification

UID for assets/modules: Planned
Lifecycle traceability: Partial

STANAG 7074 - DIGEST (Geospatial)

Geospatial exchange: Out of Scope
Consistent georeferencing: Partial

STANAG 2352 - CBRN Defense Equipment

Hazard terminology: Aligned
Source-term control: Partial (via SLF/PFE)
Certification: Out of Scope

STANAG 4370 - Environmental Testing (AECTP)

Mission profiles & tailoring: Partial / Planned
Climatic/mechanical tests: Planned
Combined environments: Planned

STANAG 5068 - SCIP (Secure Communications Interoperability Protocol)

Secure voice/data: Partial (custom AES-256-GCM transport)
Cryptographic mechanisms: Partial (extends to post-quantum)
Interoperability with NATO: Planned

STANAG 4406 - Military Messaging

Secure messaging: Partial (in-channel auth aligned)

STANAG 4787 - NINE (Network Information Exchange)

Secure IP transfer: Partial
Data protection: Aligned (Ed25519 key pinning)

Post-Quantum Cryptography Considerations

Protection against future cryptanalytic quantum attacks: Aligned (custom research implementation)

The suite incorporates forward-looking post-quantum key encapsulation based on ML-KEM-768 (Kyber family) using Bouncy Castle 1.82. This provides quantum-resistant key agreement combined with Ed25519 identity verification and key pinning to mitigate man-in-the-middle risk. Transport encryption uses AES-256-GCM with replay protection, custom framing and in-channel authentication.

YATO-Umbrella: Shared Compute and Control Architecture

YATO-Umbrella uses the same modular design philosophy found across the wider suite.

Its internal electronics combine higher-level companion computing with a deterministic microcontroller safety layer, reusing the same NVIDIA Jetson Nano class compute approach also used in Kagura, while maintaining shared control architecture with Arduino-based systems across the platform family.

This makes upgrades, troubleshooting and component replacement much easier as the suite evolves.

Kagura: Modular Chassis with Reused Core Electronics

Kagura reuses the same core engineering logic as YATO-Umbrella rather than introducing a completely separate architecture.

The platform is designed around interchangeable electronics blocks, including shared compute concepts, control hardware and sensor integration methods.

In practice, this means systems such as the Jetson Nano companion layer, Arduino Mega safety-control approach and common communications modules can be maintained using the same technical baseline across both platforms.

Ed-Remote: Same Control Backbone, Different Role

Ed-Remote serves as the handheld control and mission interface, but it is built on the same architectural principles as the robotic platforms it manages.

It shares the Arduino Mega 2560 control backbone, the same nRF24 command-link structure, the same LoRa telemetry logic and the same data-format philosophy used across Kagura and YATO-Umbrella.

This allows one operator ecosystem, one maintenance logic and one firmware style to support the full suite.

Shared Battery Modules and Cross-Platform Reuse

Kagura, YATO-Umbrella and Ed-Remote are designed to share the same battery modules and broader hardware philosophy wherever practical.

This reduces spare-part complexity, simplifies field logistics and supports rapid substitution between platforms.

Instead of treating each machine as a separate prototype, the suite is built as one modular ecosystem with common power modules, reused electronics and cross-compatible subsystems.

Cross-Platform Shared Design

Okita shares the same ecosystem-level design logic as Ed-Remote, Kagura and YATO-Umbrella.

While Okita is optimized for aerial size, weight, and performance, it still follows the same cross-platform philosophy of maintainability, interoperability, and component reuse wherever possible.

Easy Repair and Fast Reset

Okita uses a sectional internal layout that makes inspection, repair, and replacement of key modules much easier during testing and development.

Major assemblies are intended to be serviced individually rather than forcing a rebuild of the whole airframe, reducing downtime and supporting faster iteration.

Why These Names?

Wiewiorka Works uses memorable anime and pop-culture inspired codenames as an alternative to the usual “god-weapon” language common in defense technology.

Wiewiorka Works is not presenting its systems as divine, unstoppable or destructive.

Ed-Remote controls. Kagura carries. YATO-Umbrella acts. Shinpachi observes. Okita captures. MAGI+SIBYL coordinates. Safety governs.

Code, documentation, CAD files, electronic schematics and prototype test videos can be provided on request, including firmware, HUD software, system governance material, SOP documentation and technical architecture notes.

Page updated

Report abuse