A real-time situational-awareness platform equipped with a data-fabric ingestion layer, RTSP/OpenCV camera feeds, a 3D globe map, and on-device WebGPU AI (analyst chat and autonomous Overseer agent capable of driving the application). It offers in-browser inference for real-time keyword data queries, ingestion of OSINT, government data, open-source public data feeds, RSS feeds, and drone feeds. Connectors are readily available to accommodate any data source you require. Should a connector not function as expected, please contact me or refer to the Test-Driven Development agentic workflow implemented. Feed any agent with the desired data, and it will process it efficiently.

I hope you find this platform valuable. Please feel free to reach out if you have any questions or need assistance.

Extended with: pluggable connectors, generic IoT/MQTT/Webhook/RSS ingest, 3D globe (Cesium) + 2D MapLibre, browser-side computer-vision detection, and an autonomous browser agent powered by @huggingface/transformers on WebGPU.

pnpm install
# In one terminal
pnpm --filter @overwatch/fabric dev
# In another terminal
pnpm --filter @overwatch/web dev
# Optional: seed demo data once fabric is running
pnpm seed

Open http://localhost:3311.

cp .env.example .env
docker compose -f infra/docker-compose.yml up --build
# then:
pnpm seed

On the first start of the fabric backend, two files are created automatically. The path depends on how you run it:

• pnpm dev (local) — files land in apps/fabric/data/
• docker compose up — files land in the overwatch_data named volume mounted at /data inside the fabric container (see infra/docker-compose.yml)

In either case, two files are created if they don't exist:

These files are intentionally not tracked in git (see .gitignore). Each clone of the repo generates its own key and its own database — there are no shared secrets in the repo.

You can override the locations with environment variables:

OVERWATCH_DB=/var/lib/overwatch/overwatch.db
OVERWATCH_KEY_PATH=/var/lib/overwatch/key.bin

overwatch.db and key.bin belong together — back them up as a pair. Losing the key makes every encrypted connector config (API keys, etc.) unreadable. The infra/docker-compose.yml already persists both onto a single named volume.

Connector configs are encrypted with key.bin, so rotating the key invalidates any configs already stored in overwatch.db. Two paths:

Easy (wipes the DB along with the key — fastest, loses local state):

# Stop fabric first
rm apps/fabric/data/key.bin
rm apps/fabric/data/overwatch.db apps/fabric/data/overwatch.db-shm apps/fabric/data/overwatch.db-wal
# Restart fabric — a fresh key and DB are generated automatically
pnpm --filter @overwatch/fabric dev
# Repopulate demo data
pnpm seed

Preserve state (keeps connectors and history): write a one-off migration that reads each row in connector_instances, decrypts config with the old key, and re-encrypts with a new key — then swap key.bin. There is no built-in script for this; do it manually if/when you have production state worth preserving.

apps/
  web/         Next.js 15 + React 19 dashboard, 3D globe, analyst, overseer
  fabric/      Fastify + WS hub + connector orchestrator + SQLite + threatcon
packages/
  schemas/     Shared Zod schemas (events, threatcon, PIR, cameras, CV detections…)
  connectors/  23 connectors (NWS, USGS, EMSC, EONET, OpenAQ, OpenSky, ISS,
               GDELT, HN, Reddit, GitHub, Open-Meteo, CoinGecko, SpaceX,
               NOAA SWPC, Wikipedia RC, NASA FIRMS, MQTT, Webhook, RSS,
               REST poller, Demo simulator, Drone RF)
  agent/       Scaffolded — Overseer agent extraction target
  ai/          Scaffolded — on-device LLM/VLM extraction target
  cv/          Scaffolded — vision Workers extraction target
  ui/          Scaffolded — shared React components extraction target
infra/
  docker-compose.yml + Dockerfiles + go2rtc.yaml
scripts/
  seed-demo.ts + demo-drone-server.ts + smoke-drone.ts
docs/
  FEATURES.md — canonical feature inventory
  drone-detection-readme.md, plans/, specs/
future/
  IDEAS.md — 10 forward-looking proposals (capability, UX, security, DX)

Each top-level folder has a README.md with files, conventions, and agent-friendly notes. Start there before editing.

Visit /connectors to add/configure/disable any source. API-key sources expose a form generated from their Zod schema; values are encrypted at rest with AES-256-GCM (per-install random key in data/key.bin).

Add Camera on the bottom strip supports:

• webcam — local getUserMedia
• hls / mjpeg — direct URL
• rtsp — proxied through go2rtc (WHEP/WebRTC ≤500 ms)
• youtube — embed

Per-camera detectors run in a Web Worker. Each tile has a detection mode: OFF / YOLO (DETR-ResNet-50 for drone-like objects) / VLM (LFM2-VL-450M for scene captioning) / BOTH. Detections emit cv events back to the fabric. See apps/web/README.md for the pipeline.

• Analyst: chat with on-device LLM (SmolLM2 / Qwen2.5 / Llama 3.2) over your live event context, automatic WebGPU when available, WASM fallback.
• Overseer: autonomous agent that screenshots the page, captions it via image-to-text, reasons over a DOM outline of data-agent-tagged elements, and dispatches whitelisted actions (click, flyTo, setView, toggleNightVision, navigate, say, stop). Press Esc to abort.

Models are pulled from the Hugging Face CDN on first run and cached in the browser.

MIT (demo). Be a good citizen with public data sources.