MESHOPS

Resilient Communication Beyond Infrastructure

VOICE · MESSAGING · TELEMETRY · MESH

Secure communication when cellular networks, internet and cloud infrastructure are unavailable.

MeshOps is an independent system with its own firmware, protocol stack, mesh architecture, routing, voice communication, Android operator interface and dispatch component.

Voice · Messaging · Telemetry

One communication environment for spoken coordination, written orders and operational data — carried by the MeshOps mesh.

• Voice — Push-to-talk voice communication over the mesh.
• Messaging — Direct and group text communication.
• Telemetry — Transport of operational and sensor data.
• Mesh networking — Communication without cellular infrastructure.

No fixed protocol hop limit for messaging and telemetry. Practical network size and path length depend on topology, RF conditions, traffic load and deployment parameters.

One system. Three operational layers.

Operator, mesh and dispatch are parts of the same system — developed together, operated together.

• MeshOps Operator — Field communication: Mobile voice, messaging and operational status.
• MeshOps Node — Transport layer: Independent transport for voice, messaging and telemetry.
• MeshOps Dispatch — Coordination and network view: Network overview, coordination and operational management.

Product distinction: MeshOps does not run on Meshtastic or MeshCore and does not claim protocol compatibility with them.

MeshOps Operator

The mobile MeshOps interface for field personnel — an operations-oriented surface for voice, messaging and status, designed for rugged Android Enterprise handhelds.

• Push-to-talk
• Active channel
• Current speaker
• Messages
• Node / network status
• Telemetry
• Alerts
• Battery / device status
• Connection status

Rugged Android handhelds are shown as a typical device class. No partnership or endorsement by any device manufacturer is implied.

MeshOps Dispatch

Dispatch is the command and management component of the MeshOps system — not the system itself. It gives coordinators a consolidated view of the network and its traffic.

• Network overview — Consolidated view of the deployed mesh.
• Node status — State and last contact of connected nodes.
• Operational messaging — Send and receive text traffic with field units.
• Telemetry — Operational and sensor data from the network.
• Alerts — Alert messages raised within the deployment.
• Network topology — Structure and paths of the active network.
• Communication management — Channel, group and traffic administration.

Field Validation

Documented field validation

MeshOps is developed through a milestone-based validation process with repeatable runtime tests, regression gates and documented field validation.

• 1,500 m — Field test
• Multi-client — Concurrent operation
• Voice — Validated in the field
• Messaging — Validated in the field
• Telemetry — Validated in the field
• Mesh — Operation validated

Field test figures describe the specific conditions of the documented test run. They are not a general range specification. Detailed technical validation documentation is available to qualified evaluation partners.

ENGINEERING ASSURANCE

Engineered with evidence. Released through verification.

MeshOps is developed through documented engineering milestones. Released system states are linked to defined acceptance criteria, reproducible checks, runtime validation and versioned evidence artifacts.

• Defined acceptance criteria per system state
• Reproducible checks
• Runtime validation
• Versioned evidence artifacts

Encrypted communication, operated by you

MeshOps is designed to run entirely inside your own operational environment.

• AES-256 encryption — AES-256 encryption is available as a function of the system.
• No cloud dependency — Operation does not require an external cloud service.
• Own infrastructure — Dispatch and network are operated by the deploying organisation.
• Data minimisation — Operational data stays within the deployed environment.

We describe implemented functions only. MeshOps makes no claim of certification, accreditation or unconditional security.

Field evaluation

MeshOps Field Evaluation

Evaluate first. Procure second. Organisations can test MeshOps under realistic conditions before any procurement decision.

• Evaluation hardware
• Operator devices
• Mesh nodes
• Dispatch environment
• Defined evaluation scenario
• Technical support
• Structured field testing
• Evaluation results

Evaluate MeshOps under real operating conditions. A structured evaluation environment including operator devices, mesh nodes, dispatch access, technical support and documented results.