RESILIENT CONNECTIVITY EXTENSION

From the edge
to the person.

CrowdMesh extends existing connectivity with a trusted local communication layer. It helps deliver short, critical messages and receive reports from people in places where the standard channel is overloaded, unstable or simply does not reach the user.

CrowdMesh does not replace 5G, LTE or Wi-Fi. It adds the last local communication layer between the Gateway and people or devices in difficult environments.
CLOUD / CONTROL
GATEWAYRELAYRELAY
WAN / edgelocal meshpeople
Signed communicationauthorized messages
Multi-hop relaylocal range extension
Store-and-forwardcontinuity during uplink loss
SOS / MEDICALtwo-way assistance channel

THE CONNECTIVITY GAP

The network may be up.
The message may still not arrive.

The most difficult part is not always in the backbone. It appears between the last reachable network point and a specific person in a stadium, shelter, underground garage, metro, industrial plant or another demanding local environment.

CrowdMesh closes that gap. The Gateway uses the best available uplink, while the local communication layer carries the message further to phones, zones and people who need information or want to report a problem.

HOW IT WORKS

One platform. Two directions of communication.

Information from the control side reaches people through the Gateway. Reports from a person can travel through the same local layer in the opposite direction.

01

Control / operator

Creates an alert, warning or operational message for everyone, a selected sector or a zone.

02

CrowdMesh Gateway

Bridges IP/WAN with the local communication layer, maintains continuity and forwards messages to the right recipients.

03

Local mesh

Phones can act as Relay nodes, extending communication without requiring every device to connect directly to the Gateway.

04

Person

Receives a message relevant to their location or zone and can send an SOS/MEDICAL report with the context needed to handle the incident.

DOWNLINK

Control → people

  • alerts for everyone
  • sector and zone messages
  • operational warnings
  • local information when connectivity is limited

UPLINK

People → control

  • SOS and medical reports
  • incident context tied to location or zone
  • receipt acknowledgement
  • “help is on the way” status

THREE SCENARIOS

What happens to a message in practice.

Three simple diagrams show the core CrowdMesh ideas: local fan-out, continuity during WAN loss and the complementary roles of the local portal and mesh.

CONTROL / CLOUDGATEWAYABCALL / SECTOR ↓SOS ↑

Event: ALL, sector and SOS

The Gateway distributes official messages to everyone or selected zones. SOS/MEDICAL reports travel back in the opposite direction.

CLOUDWAN OFFGATEWAYLOCAL QUEUEREPORTsync after recovery

WAN OFF: local communication continues

If the uplink is lost, the Gateway can continue local communication and retain events. The queue synchronizes when WAN connectivity returns.

GATEWAYWI-FIBLELOCAL PORTALbrowserRELAYnear Gatewayextended local reach

Portal + mesh, not portal instead of mesh

The browser provides a simple path close to the Gateway. Relay extends local communication to devices beyond the direct range of one Wi-Fi access point.

THREE USE-CASE LINES

The same core. Different environments.

E

CrowdMesh Events

Stadiums, concerts, festivals and large gatherings. Alert and sector messaging plus MEDICAL reporting even when standard communication paths are overloaded.

event resilience
S

CrowdMesh Shelter

Shelters, temporary safe locations, metro areas, garages and underground facilities. A local Gateway, portal and mesh keep communication close to people.

offline local continuity
C

CrowdMesh Critical

Energy, industry, hospitals, transport and logistics. An additional resilience channel integrated with the customer or operator environment.

critical operations

APP + LOCAL PORTAL

Not every user needs the same access path.

The native app provides Participant and Relay functions. In a shelter or facility scenario, the Gateway can also expose a local browser portal. This allows simple messages and reports to be available to people who do not have the app.

The portal does not replace CrowdMesh. It is an additional channel close to the Gateway. The mesh remains the layer that extends communication beyond the range of a single Wi-Fi access point and provides an alternative path to mobile devices.

crowdmesh.local
LOCAL GATEWAY ONLINE

Messages for this zone

InformationExit B remains available.

FUNCTIONAL MVP

Core flows have been confirmed on real devices.

CrowdMesh is ready to enter a partner pilot. These are capabilities that can be demonstrated today without turning the public website into laboratory documentation.

iOS + Android

Message reception, sector logic, SOS/MEDICAL and Relay functionality.

Signed communication

Official messages are verified and separated from unauthorized messages.

Multi-hop mesh

Communication travels through multiple phones and a branched local topology.

ALL + sector

Messages can target everyone or a selected group or zone.

SOS / MEDICAL + ACK

The report reaches the Organizer and the response returns to the correct incident.

Store-and-forward

The Gateway retains a report while the uplink is unavailable and synchronizes after recovery.

Gateway + Control Panel

The Gateway operates independently and its state can be observed from a local browser panel.

Embedded failover path

An iPhone can operate as a local Embedded Gateway and maintain a two-way MEDICAL flow.

PARTNER READY

Ready for a joint pilot.

CrowdMesh is prepared for a technology partnership with an operator, integrator, facility owner or event organizer. The most valuable next step is a joint pilot in a real environment.

Example pilot

01

Gateway in a facility using the partner's available uplink

02

local device group with ALL / sector / SOS scenarios

03

controlled uplink degradation or loss

04

measurement of delivery, recovery and local coverage quality

CONTACT / PARTNERSHIP

Have an environment where CrowdMesh should be tested?

If you represent an operator, integrator, facility owner, event organizer or a team responsible for infrastructure resilience, we can discuss a concrete scenario.

Contactcontact@crowdmesh.eu

Tell us briefly what facility, event or operational environment you would like to cover with a pilot. We will respond with a practical next step.

Contact CrowdMeshThis address is for product and partnership discussions. It is not an emergency or medical channel.

CROWDMESH ASSISTANT

Ask about the solution.

The Assistant can discuss CrowdMesh use cases, Events/Shelter/Critical scenarios, the role of the Gateway, the difference between portal and mesh, and partner pilot models.

This is an information assistant, not an emergency or medical channel. In this version, the conversation runs locally in your browser and is not sent to a server.

CM
CrowdMesh AssistantProduct & partnership guide
Ask where CrowdMesh adds value, how it works with a Gateway and an existing network, or what a joint pilot could look like.

CROWDMESH.EU

Connectivity may end at the Gateway.
Communication does not have to.