Real-time situational awareness. Local-first. No cloud required.

Part of the Sovereign Watch family of local intelligence tools.

---

// 00 · BRIEF

Vertex fuses aircraft, vessel, traffic, weather, alerts, radio, and community feeds into a single map-centric dashboard designed to run on hardware you control. Onyx surfaces, amber-gold signal accents, and a desaturated tactical map keep the focus where it belongs — on the data.

DOMAIN · PUBLIC SAFETY    DENSITY · HIGH / DATA-FIRST
THEME  · DARK ONLY        RADIUS  · 0px / ALL

// 01 · ARCHITECTURE

Five containers. One compose file.

Container	Role	Entry point
db	PostgreSQL 16 + PostGIS 3.4	db/ init scripts
redis	State cache + pub/sub event bus	Stock image
backend	FastAPI REST + WebSocket API	backend/main.py
poller	9 async background pollers	poller/main.py
frontend	React + MapLibre GL, Nginx-served	frontend/src/main.tsx

External APIs / SDR hardware
        ↓
    poller (9 async tasks)
        ↓  bulk INSERT
    PostgreSQL ← PostGIS geofence queries
        ↓  Redis pub/sub
    backend WebSocket /ws
        ↓  JSON events
    frontend Zustand → Deck.gl → MapLibre GL

// 02 · DATA SOURCES

Signal	Color	Source
Aircraft (ADS-B)	#00BFFF CYAN	OpenSky · local Ultrafeeder
Vessels (AIS)	#00C853 GREEN	AISstream.io · local AIS-catcher
P25 Radio	#FF8F00 AMBER	OP25 trunked radio
Emergency	#C62828 RED	NWS alerts · FlashAlert · county EM
Traffic	#FFB800 GOLD	ODOT TripCheck
Mesh	#FFB800 GOLD	MeshCore nodes

// 03 · QUICK START

cp .env.example .env
cp config/sources.example.yml config/sources.yml

# Edit .env with your region, API keys, and data sources
$EDITOR .env

docker compose up -d

Open http://localhost. For detailed setup, see docs/getting-started.md.

// 04 · SUPPORTED INTEGRATIONS

• ADS-B — Ultrafeeder (local) or OpenSky Network (cloud fallback)
• AIS — AIS-catcher (local) or AISstream.io (cloud fallback)
• P25 — OP25 trunked radio decoder (local SDR)
• Mesh — MeshCore node tracking over WebSocket
• Weather — NWS observations and alert zones
• Traffic — ODOT TripCheck incidents and camera streams
• Alerts — FlashAlert and county emergency management RSS

// 05 · DOCUMENTATION

Document	Description
Getting Started	Installation, configuration, first run
Architecture Overview	Service layout and data flow
Feature Overview	Dashboard features and panels
Map Key	Icon meanings, zoom behavior, and colors
Environment Config	.env variable reference
Source Config	sources.yml reference

// 06 · LICENSE

GPL-3.0 — see LICENSE.

// 07 · PI 5 DEPLOYMENT

Prerequisites

• Raspberry Pi 5 (8 GB recommended)
• Raspberry Pi OS Bookworm (64-bit)
• Docker CE (docker.io + docker-compose-plugin)
• A .env file configured from .env.example

First-time install

Set the repo URL, then run the install script:

export VERTEX_REPO_URL=https://github.com/d3mocide/Vertex.git
curl -fsSL https://raw.githubusercontent.com/d3mocide/Vertex/main/infra/install.sh | sudo -E bash

If you have already cloned the repo locally:

export VERTEX_REPO_URL=https://github.com/d3mocide/Vertex.git
sudo -E bash infra/install.sh

After the script completes, edit /opt/vertex/.env with your region, API keys, and data sources.

Update

sudo bash /opt/vertex/infra/update.sh

This pulls the latest code and images, then restarts the service via systemd.

Service management

sudo systemctl status vertex        # Show service status
sudo systemctl stop vertex          # Stop the stack
sudo systemctl start vertex         # Start the stack
sudo journalctl -u vertex -f        # Follow live logs

Resource notes

The full stack uses approximately 2 GB RAM under load. A Pi 5 with 8 GB is recommended for comfortable headroom. Resource limits are pre-configured in docker-compose.yml and can be tuned for your hardware.