Introduction

Learn how to deploy and use the GroundWave situational awareness platform.

5 min read

What is GroundWave?

GroundWave is an open-source, field-deployable situational awareness platform inspired by ATAK (Android Team Awareness Kit). It provides mapping, real-time position tracking, messaging, and team coordination through a standard web browser — no native app installation required.

The platform is packaged as a suite of Docker containers designed to run on portable, low-cost hardware such as a Raspberry Pi or Intel NUC. A single server unit creates a local Wi-Fi access point; client devices — phones, tablets, laptops — connect to that network and open GroundWave in their browser.

GroundWave is fully self-contained and operational without internet connectivity. Offline map tiles, position data, chat messages, and all coordination tools are served entirely from the local device. When connectivity does exist, optional features such as online map style fallback and server federation become available.

GroundWave is MIT-licensed. The source repository will be open to contributions when GroundWave exits beta.

Design Principles

Every architectural and feature decision in GroundWave is guided by a core set of principles:

  • Offline-First. The system must be fully operational with zero internet access. Map tiles, APIs, and real-time communication all run locally. Internet connectivity, when present, is treated as an optional enhancement rather than a requirement.
  • Containerized. All server-side components run inside Docker containers orchestrated by Docker Compose. Deployment is a single command regardless of the host operating system. Updates and rollbacks are clean and reproducible.
  • Web-Native. Clients connect via any modern web browser. No native app is required on phones, tablets, or laptops. This eliminates app store dependencies and device enrollment friction in the field.
  • Replicable. A complete GroundWave deployment — server hardware, Docker images, and tile data — can be reproduced from a self-contained release archive. No external registries or cloud services are needed to stand up a new unit.
  • Modular. Features are organized into discrete, independently toggleable modules (chat, markers, file sharing, overlays, voice, federation). Operators can enable only what their mission requires via environment configuration.
  • Resource-Conscious. The platform is designed to run on single-board computers with limited CPU, RAM, and storage. Performance budgets are validated against a Raspberry Pi 4 baseline. Unnecessary dependencies are avoided.
  • No Cloud Dependencies. GroundWave does not phone home, require license validation, or depend on any third-party SaaS. All data remains on the local device under operator control.
  • Network-Agnostic. The server communicates over standard TCP/IP and works on any network topology — Wi-Fi hotspot, wired LAN, mesh radio, or ad hoc. The client needs only a browser and an IP route to the server.

Technology Stack

GroundWave is built on a pragmatic, well-supported open-source stack chosen for stability, offline viability, and low resource consumption:

Layer Technology
Server Node.js + Express + Socket.IO
Database PostgreSQL + PostGIS
Frontend React + Vite + Tailwind CSS
Mapping MapLibre GL JS
Tile Server TileServer GL
Proxy Nginx
Containers Docker + Docker Compose

All components are open-source and run without internet access. The tile server serves pre-downloaded .pmtiles or .mbtiles archives, and the PostgreSQL database with PostGIS handles all geographic storage and spatial queries locally.

Jump directly to the section most relevant to your role: