QSARshared live map
Get started

How it works

The whole system in plain language — what talks to what, and what happens when the internet goes down.

The one-sentence version

Everything — phones, the drone, satellite beacons — reports to a shared server in the cloud, and that server keeps every screen showing the same live map.

The picture

                     ☁️  CLOUD SERVER (always on, rented)
                     ├── TAK server  = the shared map
                     └── MediaMTX    = the video switchboard
                          ▲                ▲               ▲
            positions,    │                │ drone video   │ beacon
            messages      │                │               │ positions
                          │                │               │
   ┌──────────────────────┴───┐   ┌────────┴─────────┐   ┌─┴──────────────┐
   │ Searchers' phones        │   │ Skydio X10 drone │   │ Somewear cloud │
   │ (ATAK / iTAK / browser)  │   │ + controller     │   │ (satellite)    │
   │ via village Starlink     │   │ via Starlink     │   │                │
   └──────────────────────────┘   └──────────────────┘   └─▲──────────────┘
                                                           │ Iridium satellites
                                                    ┌──────┴─────────┐
                                                    │ Somewear beacon│
                                                    │ on each        │
                                                    │ searcher       │
                                                    └────────────────┘

Why the server is in the cloud, not the village

Starlink is excellent at calling out but does not let outside computers call in (a limitation called CGNAT). A server in Quinhagak would be invisible to Eek, Goodnews Bay, and the Somewear system. A small rented cloud server (~$12–24/month) has a public address that everything can reach — and every part of our system only ever needs to call out.

What happens when the internet goes down

The system degrades gracefully instead of failing:

  • Maps keep working. Every device carries downloaded maps of our operating area — that’s policy, not luck. Searches happen beyond cell service, so the map on your screen never depends on an internet connection. The server hands out map downloads between missions; it is never needed during one.
  • Satellite beacons keep working. Somewear uses Iridium satellites, not Starlink — searchers stay on each other’s maps and can still message.
  • Phones on the same WiFi still see each other. TAK apps share positions directly on a local network without any server.
  • The drone still flies and records. Video sharing to remote viewers pauses; local operations continue.
  • (Future) Meshtastic radios add a third layer that needs no infrastructure at all.

What each person carries

Role Carries Sees
Searcher Phone with ATAK/iTAK + a Somewear beacon The whole team + drone on their phone
Drone operator Skydio controller (its screen runs the map too) Flight view + team map
Coordinator Any computer with a browser (CloudTAK) or WinTAK Everything, on a big screen

Is it private?

Yes. Connections to the server are encrypted, each member gets their own login/certificate, and the server is ours — no public map, no public video. (Somewear and Skydio see their own devices’ data, as they do today.)

Ocean conditions on the map

Three wave buoys float in Kuskokwim Bay — off Quinhagak, Mud Point, and the Halibut grounds. Every 15 minutes the server checks each buoy’s latest report and places it on the shared map as a marker. Tap a buoy to see the wave height, how often the waves are coming, which direction they’re coming from, and how many minutes old the reading is.

If a buoy stops reporting (dead battery, winter pull-out), its marker fades after a couple of hours — a faded buoy means “don’t trust these numbers,” never “the water is calm.”