SafeGround is designed on the assumption that everything will fail. No cellular network. No power grid. No internet. The system must function in the absence of every dependency it would normally rely on.
System Architecture
The SafeGround architecture distributes intelligence, coverage, and redundancy across three node tiers. Each tier is designed to function independently — and to enhance every other tier when connectivity is available.
ADMIN HUB (T3) ←→ CONTRIBUTOR NODES (T2) ←→ USER NODES (T1) · SELF-HEALING · TDMA SCHEDULED
Hardware
Every hardware choice in SafeGround is made with one assumption: it will be deployed in a disaster-prone area, by people without specialist technical training, and must continue operating when no support is available.
The SENTINEL device is designed to be a grab-and-go unit. In GO mode, it operates entirely on battery, provides GPS beaconing, mesh communication, and displays the last known threat assessment on an e-ink screen readable in full sunlight.
Software Stack
The SafeGround software architecture runs from bare-metal firmware on field nodes to an AI-driven threat intelligence layer on the Admin Hub — all operating independently of cloud infrastructure.
The Admin Hub runs a Python-based Claude AI agent on the Raspberry Pi 4. Every 15 minutes, it polls USGS, EMSC, Copernicus EFFIS, and local meteorological services, then generates a structured GREEN / AMBER / RED threat assessment using tool_use-based source verification. The assessment is encoded and broadcast to the mesh.
Full integration with Android Team Awareness Kit (ATAK) — the tactical situational awareness platform used by emergency responders and civil defence teams. SafeGround nodes appear as data sources on ATAK maps, providing real-time mesh topology and alert status overlays for responding teams.
Every alert and node registration includes a What3Words location reference. A 3-word address encodes a 3m² square anywhere on Earth — making precise location communication possible for anyone, regardless of technical literacy, in any language, without coordinates.
All SafeGround alerts conform to the Common Alerting Protocol v1.2 — the international standard for emergency alerts. A hexadecimal encoding layer compresses CAP messages for LoRa's low-bandwidth radio link while preserving the full structured alert payload on the receiving end.
Communications Protocols
LoRa networks in Europe operate under EU868 spectrum regulations, imposing strict duty cycle limits that make naive broadcast protocols impractical at scale. SafeGround solves this with a custom TDMA scheduling layer and a hexadecimal alert encoding scheme that reduces message payloads to the minimum necessary for CAP-compliant alerts.
Every message on the SafeGround mesh is end-to-end encrypted using XChaCha20-Poly1305 — a modern, authenticated stream cipher with 192-bit nonces that provides forward secrecy and resistance to nonce-reuse attacks.
Post-Event Communications
SafeGround is not only a pre-event warning system. The same mesh infrastructure that broadcasts alerts before a disaster provides the communications backbone for structured Situation Report (SitRep) and Resource Request messaging in the immediate aftermath.
Standardised message types enable affected communities to report casualty status, infrastructure damage, and resource needs to Admin Hubs — and for responders to coordinate without relying on cellular or internet connectivity.
Why Not Meshtastic?
Meshtastic and similar consumer mesh solutions are effective at small scale. SafeGround targets 30–200 nodes per deployment area. At this scale, Meshtastic's flooding protocol creates unacceptable duty cycle violations under EU868 regulations. SafeGround's custom TDMA layer assigns scheduled transmission windows to each node, enabling reliable EU868-compliant mesh operation at community scale.
Candidate Pilot Site
Interactive 3D visualisation of a proposed SafeGround mesh deployment across the Pissouri area — situated on the African-Eurasian plate boundary, with documented landslide risk, growing wildfire exposure, and no existing LoRa infrastructure.
PISSOURI BAY, CYPRUS · 34.6627°N 32.7012°E · PROPOSED 30-NODE PILOT DEPLOYMENT · CANDIDATE SITE — NOT YET CONFIRMED
The 2012 Pissouri ground movement displaced 24 families. Over 150 homes remain at ongoing risk. Cyprus Geological Survey monitors the slope continuously. No community warning system exists.
The 2021 Arakapas fire destroyed 55,000 hectares and killed four people. Pissouri sits in the expanding wildfire risk corridor of the eastern Mediterranean, with annual fire seasons growing in intensity.
Located on the African-Eurasian plate boundary, Cyprus experiences routine seismic activity. Pissouri's coastal cliffs amplify the landslide risk following seismic events — an ideal multi-hazard PoC environment.