TacticalMesh

Open-Source Tactical Edge Networking Platform

---

One-Line Summary

TacticalMesh is an open-source, decentralized mesh networking platform that enables resilient command-and-control communications between edge nodes in contested or infrastructure-denied environments.

The Simple Explanation (Analogy)

Think of it like Waze for military radios:

• Waze finds the fastest driving route by checking traffic.
• TacticalMesh finds the fastest communication path by checking which soldiers can reach headquarters.

If one road is blocked (radio is jammed), Waze finds another route. Same with TacticalMesh—if one path fails, it automatically finds another soldier to relay through.

---

Problem Statement

The Operational Reality

Modern defense operations, disaster response scenarios, and civil resilience efforts face a common challenge: communications in contested environments.

Consider these operational realities:

• Contested Spectrum: Adversary jamming and interference degrade traditional radio links
• Destroyed Infrastructure: After natural disasters or in conflict zones, cell towers and network infrastructure may be non-functional
• Mobility Requirements: Vehicles, dismounted units, sensors, and UAS must maintain connectivity while moving
• Coalition Operations: Allied forces must interoperate, often with incompatible proprietary systems
• Disconnected Operations: Forward units may be cut off from headquarters for extended periods

Why Current Systems Fall Short

Existing tactical networking solutions suffer from critical limitations:

| Challenge | Impact | | --------------------- | ---------------------------------------------------------------------------------------------------------- | | Vendor Lock-in | Proprietary systems create single-vendor dependencies with long procurement cycles and limited flexibility | | Cost | Military-grade mesh radios cost $10,000–$50,000+ per unit, limiting widespread deployment | | Interoperability | Different systems cannot communicate, hindering coalition operations | | Adaptability | Closed systems cannot be rapidly modified to address emerging threats | | Supply Chain Risk | Proprietary hardware creates supply chain vulnerabilities |

---

Competitor and Landscape Analysis

Categories of Existing Solutions

1. Proprietary Military Mesh Systems

Traditional defense contractors offer specialized tactical radio systems with integrated mesh networking:

• Strengths: Proven in military environments, designed for specific frequency bands
• Weaknesses: Extremely high cost, vendor lock-in, slow innovation cycles, limited customization

2. Commercial Mesh Networking

Commercial mesh solutions designed for IoT and enterprise applications:

• Strengths: Lower cost, widely available
• Weaknesses: Not designed for contested environments, lack tactical features, no disconnected operation support

3. Open RAN Initiatives

Telecom-focused efforts to open radio access network interfaces:

• Strengths: Open standards, multi-vendor support
• Weaknesses: Infrastructure-centric, not designed for tactical edge, assumes reliable backhaul

The Gaps TacticalMesh Addresses

| Gap | TacticalMesh Approach | | ------------------------ | ---------------------------------------------------- | | Vendor Lock-in | Fully open-source with Apache 2.0 license | | High Cost | Runs on commodity hardware (Raspberry Pi, x86 boxes) | | Closed Code | Transparent, auditable source code | | Slow Innovation | Community-driven development with rapid iteration | | Interoperability | OpenAPI-first design for easy integration | | Single Points of Failure | Decentralized architecture with graceful degradation |

---

What TacticalMesh Provides

Core Benefits

✅ Resilient Edge Networking — Nodes continue operating when disconnected from the central controller, with automatic reconnection and state synchronization

✅ Open-Source Transparency — Full source code visibility enables security audits, customization, and elimination of supply chain black boxes

✅ Commodity Hardware — Deploy on Raspberry Pi, NVIDIA Jetson, commercial edge servers, or any Linux platform

✅ OpenAPI Integration — Standard REST APIs enable integration with existing C2 systems, sensor networks, and enterprise applications

✅ Role-Based Access Control — Granular permissions for administrators, operators, and observers with complete audit logging

✅ Dual-Use Design — Applicable to defense, disaster response, remote industrial operations, and civil resilience

Target Deployment Scenarios

• Military Edge Networks: Connecting vehicles, dismounted units, sensors, and small UAS in tactical environments
• Disaster Response: Rapidly deployable communications for first responders when infrastructure is destroyed
• Remote Operations: Industrial sites, research stations, and maritime vessels with intermittent connectivity
• Coalition Operations: Interoperable command and control for allied forces with different native systems

Representative Use Cases

1. Platoon‑Level Edge Network in Contested Spectrum - In a high‑threat environment, a platoon operating beyond the range of fixed infrastructure needs resilient local communications between vehicles, dismounted soldiers, and unattended sensors. TacticalMesh is deployed on small edge computers (e.g., ruggedized Raspberry Pi‑class devices) mounted in vehicles and carried in rucksacks. Each node runs the agent, registering with a nearby controller when available and continuing to exchange health and status information when disconnected. Operators use the web console to see which squads and sensors are online, issue simple commands (e.g., reconfigure reporting intervals, enable/disable a sensor), and review audit logs showing who changed what and when. This enables commanders to maintain situational awareness even when satellite and cellular links are degraded or denied.

2. Coalition / Joint Exercise Lab Environment - During a joint or coalition training exercise, multiple nations want to experiment with different radio stacks, edge devices, and command‑and‑control systems without locking into a single vendor. TacticalMesh is deployed in a lab environment as the common “control‑plane” fabric: each participating nation connects its own radios and edge nodes via the TacticalMesh agent and integrates its national C2 prototypes via the OpenAPI interface. The open, Apache‑licensed controller provides shared visibility of node status and command delivery while allowing each partner to keep its own radio hardware and national applications. This supports experimentation with coalition interoperability while maintaining clean separation of sensitive national capabilities.

3. Rapid Response / Disaster Relief Network (Dual‑Use) - After a major natural disaster, civil authorities and military support units need to stand up a local communications fabric quickly in an area with damaged infrastructure. TacticalMesh is deployed on commercial off‑the‑shelf edge devices placed at command posts, field hospitals, and logistics hubs. The agent software forms a local control‑plane mesh, reporting basic health and location information back to a central controller when power and connectivity are available. The operations console gives incident commanders a single view of which sites are reachable, which edge nodes are overloaded, and where to direct scarce resources. This dual‑use scenario allows organizations to evaluate the platform in peacetime humanitarian missions while using the same codebase that can later be hardened for military operations.

4. Vendor‑Neutral Integration Testbed - A defense program office or integrator wants to test multiple radios, routers, and edge compute platforms from different vendors without relying on any one vendor’s proprietary management stack. TacticalMesh is used as a neutral integration layer: each device hosts a small agent that normalizes status and telemetry into a common schema. The program office connects their existing monitoring tools and prototypes to the controller’s OpenAPI endpoints to evaluate performance, resilience, and behavior under fault conditions. Because TacticalMesh is Apache‑licensed and open, the testbed can be shared with contractors, FFRDCs, and allied labs without complex licensing agreements, while still leaving final export‑control decisions to each organization.

---

🚀 Live Demo

New! You can now run the demo directly from the Web Console:

1. Log in (admin / admin123).
2. Go to Settings.
3. Toggle Demo Mode to start the simulation.

Alternatively, you can run the CLI simulation script:

./demo/start.sh

This spins up the full stack and simulates a tactical network with vehicles, drones, and soldiers moving in real-time. See the Demo Guide for more details.

Key Features (v0.1)

Node Management

• Registration & Discovery: Automatic node registration with the central controller
• Heartbeat Monitoring: Real-time health st