CrowdMesh

RESILIENT CONNECTIVITY EXTENSION

From the edge
to the person.

CrowdMesh extends existing connectivity with a local, managed resilient communication layer. It connects phones, controlled Relay, an Edge Gateway and central systems to deliver critical messages and receive SOS/MEDICAL reports during overload, partial failure or WAN loss.

See how it worksDiscuss a pilot
CrowdMesh does not replace LTE, 5G, Wi-Fi or Cell Broadcast. It adds a managed local path for low-volume, high-importance traffic.
CLOUD / CONTROLoperator · organizer · systemsEDGE GATEWAYWAN · queue · portal · meshRELAYRELAYRELAYPERSONPERSONPERSONPERSONPERSONALERT / WARNING ↓SOS / MEDICAL ↑
CONTROLLED TOPOLOGYbranching / forest
WAN OFF CONTINUITYlocal data plane
TRUSTED TRAFFICsigned source
10 / 10CORE CAPABILITIES IMPLEMENTED
PILOT-READYadvanced functional platform
iOS + ANDROIDreal-device core flows
WAN OFFlocal continuity + queue

THE CONNECTIVITY GAP

Working infrastructure does not always mean user access.

The most vulnerable segment may be between the last reachable network point and a specific person. CrowdMesh creates a second local path for operationally important messages.

ALERTWARNINGEVACUATIONSOSMEDICALACK
Standard path
Phone
→
LTE / 5G / Wi-Fi
→
Cloud / central system
CrowdMesh resilient path
Phone + Relay
→
Controlled Relay
→
Gateway → existing infrastructure

ONE PLATFORM

One platform. Multiple products. Multiple deployment environments.

A shared Core and Gateway software connect the user layer, Edge and central systems. Business profiles are mainly configuration, UI and policy, not protocol forks.

1 · User ExperienceUSER LAYER
ParticipantiOS · Android
Relay Capabilitycontrolled local extension
Organizeralerts · coordination · MEDICAL
2 · Edge / GatewayEDGE RUNTIME
Gateway RuntimeWAN ↔ local mesh
Control Panelstatus · queue · diagnostics
Gateway ApplianceEvent · Shelter · Critical
3 · Shared Core PlatformSHARED CORE
Event Identitynamespace
Trustsigned source
Admissionpolicy
Dedupemessage ID
Hop Limitpropagation
TargetingALL · zone
Topologybranching
Store & Forwardpersistent queue
4 · Central / IntegrationOPERATOR & CLOUD
Cloud / Fleetcontrol plane
Operator integrationLTE · 5G · private 5G
Infrastructure edgefiber · LAN · systems
Product principle: radio transport is an adapter. CrowdMesh value is controlled topology, trust, propagation, routing, local edge, store-and-forward and management.

COMPLETED CORE CAPABILITIES

10 core capabilities. One platform.

The full functional scope defined for the platform has been implemented. The next step is real-world validation, scale parameters and the operating model.

10/10implementedfunctional platform · pilot-ready
✓ COMPLETED
Trusted Organizer Communication

signed Organizer → Participant

✓ COMPLETED
Audience & Location Targeting

ALL · sector · zone · seat

✓ COMPLETED
SOS / MEDICAL Uplink

incident + location context

✓ COMPLETED
Incident-bound ACK

response to the correct report

✓ COMPLETED
Controlled Multi-hop Relay

branching / forest · relay without display

✓ COMPLETED
Gateway / Edge Runtime

runtime · portal · API · panel

✓ COMPLETED
WAN OFF Local Continuity

local data plane remains operational

✓ COMPLETED
Trust / Identity / Admission

event identity · signed source · admission

✓ COMPLETED
Resilient Data Plane

dedupe · hop · targeting · queue

✓ COMPLETED
Multi-platform Shared Core

iOS · Android · Gateway · browser

FUNCTIONAL PLATFORM10 / 10 CORE CAPABILITIESPILOT READY
GATEWAY AGATEWAY BRELAY 1RELAY 2PARTICIPANTRELAY 5PARTICIPANTP2RELAY 3RELAY 6P9P10FOREST / MULTI-GATEWAYdifferent branches can anchor at different Gateways1 ACTIVE UPSTREAM PARENTN downstream · max depth · re-parent after path loss

CONTROLLED MESH

Not all-to-all. Controlled topology.

CrowdMesh deliberately uses a branching / forest structure instead of an uncontrolled broadcast mesh.

01
One active upstreamEach Relay has one active parent and a bounded number of downstream children.
02
Propagation controlHop limit, dedupe and topology policy bound copies and depth.
03
Re-parentingAfter path loss a node may attach to another qualified parent.
04
Diagnostics and scaleA predictable topology supports telemetry and Gateway placement planning.

MESSAGE JOURNEY

Relay is not blind replication.

Every hop applies Event, authenticity, duplicate, propagation, addressing and forwarding-policy checks.

CREATEevent · audience
SIGNsource identity
GATEWAYdata-plane ingress
RELAYvalidate
DEDUPEmessage ID
HOP LIMITrange control
TARGETINGALL · zone · device
RECIPIENTdisplay / terminal
ACKincident response
REJECT / DROP wrong event · invalid signature · duplicate · expired
RELAY WITHOUT DISPLAY a packet can be forwarded even when the local user is not its intended recipient.
EVENT AUTHORITYEVENT ROOTGATEWAY CERT AGATEWAY CERT BGATEWAY Aprivate key AGATEWAY Bprivate key BFAKEno valid certREJECTPHONES / RELAY TRUST EVENT ROOT

SECURITY, IDENTITY & TRUST

Security is part of the architecture, not an add-on.

Trust is scoped to the Event domain rather than a single manually selected Gateway. Gateways keep separate cryptographic identities.

Event-scoped trustidentity bound to deployment
Signed sourceofficial messages verified
Gateway authorizationproof-of-possession model
Anti-replaymessage identity
Credential lifecycleexpiry · rotation · revocation
No shared private keyseparate Gateway identities
Authenticity and confidentiality are separate requirements. Public alerts primarily require strong source authenticity, while sensitive data may require additional confidentiality.

WAN RESILIENCE

WAN OFF is an operational state, not a system stop.

Cloud is not a condition for local operation. The Gateway maintains the local Data Plane and event queue, then synchronizes retained traffic after uplink recovery.

A · NORMAL OPERATION

The standard path is available.

Phones and the local mesh communicate with the Gateway, while WAN connects the Gateway to the central system.

PHONES / CONTROLLED MESH
CROWDMESH GATEWAY
CLOUD / CENTRAL SYSTEM
B · WAN OFF

Local communication continues.

The Gateway maintains local traffic, Local Portal and persistent queue. Functions that do not require immediate Cloud remain usable.

SOSMEDICALALERTSPORTALQUEUE
PHONES / CONTROLLED MESH
CROWDMESH GATEWAY
LOCAL PORTALPERSISTENT QUEUELOCAL DATA PLANE
C · RECOVERY

Store-and-forward closes the continuity loop.

After WAN returns, the Gateway synchronizes retained events and reconciles state with the central system.

PERSISTENT QUEUE
GATEWAY · RECONCILIATION
CLOUD / CENTRAL SYSTEM

ONE CORE · THREE DEPLOYMENT PROFILES

The same core. Different environments.

CrowdMesh Events, Shelter and Critical are not three separate technologies. They are deployment profiles of one shared platform.

CROWDMESH EVENTS

Stadiums · concerts · mass events

ALL / sector / seat, safety messaging and two-way SOS/MEDICAL.

GATEWAYORGANIZERABC
EVENT VENUEEVENT OPENSOS / MEDICAL
CROWDMESH SHELTER

Shelters · metro · underground facilities

Autonomous Gateway, Local Portal, mesh and queue, including physical WAN loss.

HARDWARE GATEWAYportal · queue · meshiPhoneAndroidBrowser
WAN OFFLOCAL PORTALSTORE & FORWARD
CROWDMESH CRITICAL

Infrastructure · industry · transport

An additional resilience layer integrated with existing Edge, private networks and operating processes.

OPERATOREDGE GATEWAYOPSUSER
EDGEPRIVATE 5GOPERATIONS

USE CASE · EVENT

The right message to the right sector.

An Organizer can target everyone or a selected area. A participant can send SOS/MEDICAL, while “help is on the way” returns to the correct incident.

WARNING → Sector BSOS / MEDICAL ↑ to OrganizerACK / HELP ON THE WAY ↓ to the correct report
OPERATOR / ORGANIZERCROWDMESH GATEWAYABCDWARNING → BSOS / MEDICAL ↑ALL / sector / seat
CRISIS / OPERATOR CENTERHARDWARE GATEWAYLocal Wi-Fi / LAN · CrowdMesh RuntimeLocal Portal · Persistent QueueControl PanelWAN IF AVAILABLEiPhone CrowdMeshAndroid CrowdMeshBrowser userno app requiredWAN OFF: LOCAL COMMUNICATION CONTINUES

USE CASE · SHELTER

Portal + mesh. Two complementary channels.

Native CrowdMesh provides the full resilient channel and Relay capability. Local Portal provides basic access to people without the app near the Gateway.

Local Portal in a standard browserMesh extends beyond one Wi-Fi access pointPersistent queue retains events during WAN OFF

USE CASE · CRITICAL

Resilience where the last segment matters.

Metro, tunnels, transport, industry and critical infrastructure can use the same Edge Gateway and Core. Alerts travel down, while status, SOS and MEDICAL travel back to operational systems.

Operator / private network / edgeControlled local mesh in difficult environmentsTwo-way operational traffic
CONTROL / PRIVATE NETWORKEDGE GATEWAYRELAYRELAYRELAYALERT ↓STATUS / SOS ↑

OPERATOR / INTEGRATOR VALUE

CrowdMesh does not compete with the operator. It extends functional reach.

The operator can own uplink, Edge, distribution and management. CrowdMesh provides the local Data Plane, controlled relay, Gateway and resilient fallback.

OPERATORCloud / Control Plane · provisioning · fleet · monitoring · mobile channel
CROWDMESHEdge Gateway · controlled relay · local Data Plane · resilient fallback
INTEGRATORcustomer environment · integration · deployment · operations
PARTNER / INSTITUTIONindependent validation · methodology · reference use-case model
OPERATOR / CENTRAL INFRASTRUCTURELTE · 5G · private 5G · edge · fiber · cloud
↓
CROWDMESH RESILIENCE EXTENSIONGateway · managed topology · trust · local continuity
↓
PEOPLE AT THE POINT OF NEEDalerts ↓ · SOS/MEDICAL ↑

EVIDENCE & MATURITY

From a functional platform to a measurable field pilot.

The functional scope and key flows have been implemented and validated on real devices. Large-scale validation is a pilot objective, not a marketing assumption.

01
COMPLETED

Core Capabilities

10/10 functional platform areas.

02
COMPLETED FOR CORE FLOWS

Physical Device Validation

iOS + Android, multi-hop, ALL/sector, SOS/MEDICAL/ACK, Gateway, WAN OFF.

03
CURRENT STAGE

Pilot Ready

Controlled baseline, real-device flows and a measurable pilot plan.

04
NEXT

Large-scale Field Validation

Scale, radio, KPI, battery, placement and operating model.

REAL-WORLD PILOT

The next question is not whether CrowdMesh works.

The question is where, in which architecture and at which parameters it creates the largest measurable increase in communication resilience.

01FUNCTIONAL PLATFORMcomplete
02REAL-WORLD PILOT1 site · 2–3 Gateways
03MEASUREdelivery · latency · recovery
04OPTIMIZEtopology · placement · policy
05REFERENCE MODELvalidated use case
06DEPLOYMENTpartner operating model
AreaExample metricWhat it tells us
PropagationP50 / P95 latencyoperational usefulness
Deliverydelivery ratioreal service reach
Resiliencere-convergence timeself-recovery after node loss
Store & forwardqueue recoveryWAN OFF / ON continuity
Topologyhop distributionpropagation depth and cost
Mobilitybattery / backgroundreal iOS / Android constraints
Securityrejection rateadmission and trust policy

ASK CROWDMESH

Product & Partnership Guide.

Ask about the Gateway, controlled relay, WAN OFF, Events, Shelter, Critical, security or a pilot model. This version runs locally in the browser and does not send chat content to an external AI model.

CM
CrowdMesh AssistantProduct & Partnership Guide
Ask how CrowdMesh extends existing connectivity, what 10/10 core capabilities means, or how to design a real-world pilot.

CONTACT / PARTNERSHIP

Let’s design the first real deployment together.

If you represent an operator, integrator, facility owner, public administration or infrastructure partner, let’s discuss a scenario worth measuring in a pilot.

Product & partnership contactcontact@crowdmesh.eu

Tell us briefly what facility, event or environment you want to validate. We will respond with a proposed next step.

Discuss a pilotThis address is not an emergency or medical channel.

CROWDMESH

One platform. Multiple deployment profiles. Resilient connectivity from the network edge to people.

Contact usExplore the platform