The survival computer for when everything else is down.

First-aid guides, maps and routes, and an off-grid mesh radio for SOS, in one sealed tablet. No internet, no cell towers, no cloud.

  1. Glass and buttons

    Readable in sun, usable in gloves.

    A sunlight-readable touchscreen, plus a button rail that runs the whole interface: D-pad, OK, back, and an SOS key under a flip cover. A small e-paper strip shows time, battery, position and CO with everything else off.

  2. Display

    The screen dims before the battery does.

    The display is the biggest power draw after the processor, so it sleeps between glances and wakes on any button.

  3. Main board

    Two computers, so one is always awake.

    A Linux compute module runs maps, routes and 125 guides from local storage. Beside it, an nRF52840 safety chip stays on: it watches the air, signs and sends SOS by itself, and restarts the main computer if it freezes.

  4. Power

    Cells you can swap, and scavenge.

    Four standard 21700 cells, about 72 Wh. Charge them by USB-C, solar, 12 V or a hand crank, or swap in fresh ones in the field.

  5. Shell

    Sealed against the weather.

    An IP67 target, a gasketed battery door that opens without tools, external antenna ports for GNSS and LoRa, and one sealed port for the clip-on sensor pod.

Built to last days, not hours.

With the main computer off, the safety chip keeps logging your track, listening to the mesh and watching the air on a fraction of a watt.

6–8 days

Safety chip, GNSS logging, mesh receive, sensors and e-paper. Linux off.

0.3–0.45 W average draw

Estimates from the power budget, on about 62 Wh usable. Expect 20–30% less below 0 °C. To be measured on hardware.

One screen for the worst day of your life.

Emergency first.

One SOS button and sixteen big tiles: bleeding, not breathing, choking, burns, snake bite, smoke and gas, safe water, lost, flood. Each opens the first steps and a clear "Do not" list. Works by D-pad, with night mode and large text.

FieldAssist home screen with an SOS button and emergency tiles

It quotes the guide. It never guesses.

Answers come word for word from 125 survival guides across 13 categories, drawn from WHO, Red Cross and similar public guidance, and each one names its source. In testing, a small on-device AI reversed safety advice, so no AI writes answers by default.

Bleeding guide with numbered first steps

It smells what you can't.

A sensor pod watches carbon monoxide and temperature. When the level climbs, the siren, strobe and vibration start, and the screen tells you exactly what to do.

Carbon monoxide alarm at 217 ppm with an acknowledge button

If you can't answer, it calls for you.

An unanswered alarm escalates to SOS. The safety chip signs it with its own key and sends it by itself, even if the main computer has crashed, and repeats it until someone cancels it.

Automatic SOS being sent after an unanswered alarm

It tells you what broke, and what still works.

The Device Doctor runs fixed self-tests of the safety chip, sensor pod, GPS, clock, storage, guides, routes and maps. Every fault gets a short code and a fix card with the steps and a backup plan.

Device Doctor status page with self-test results
Concept render
Concept render: the tablet held in gloved hands in the rain, showing a route across a mountain valley

Made for gloves, rain and the dark.

Big buttons that work through gloves, a screen you can read in sunlight, and a shell sealed against the weather.

When the towers fall, the devices carry each other.

LoRa reaches a few kilometres. The mesh relays messages from device to device to go further, riding on Meshtastic so cheap stock radios can relay too. The protocol is proven in a simulated valley; real radios are next.

A signed SOS crosses the valley, device to device.
  • FieldAssist device
  • Stock Meshtastic relay
  • Forged packet

Signed SOS

Sent by the safety chip, signed with an Ed25519 key that never leaves it. It carries your last position, the CO level and the reason, and repeats until cancelled.

Prank-proof

A device never shows or sounds anything it hasn't verified itself, even when relays forward everything. Replayed or forged alerts stay silent.

Private by default

End-to-end encrypted messages with delivery receipts. Location sharing per group, with optional fuzzing to about 100 m or 1 km.

Pair without a camera

Hold two devices together and compare a 6-digit code. Someone in the middle gets one guess in a million.

Missing-person alerts, with moderation.

Built so it can find a lost child, and so it can't be used to hunt someone who is hiding.

  1. ReportA parent's report goes, encrypted, only to community moderators.
  2. VerifyA moderator checks it. With no moderator around, three neighbours can endorse a child or medical alert.
  3. AlertEvery device in range shows the alert. Adults always need a moderator.
  4. SightingsSightings go back to the moderators, not out to everyone.
  5. FoundWhen the person is found, the details are deleted.

Tested before it's built.

A virtual lab runs the real safety-chip firmware, on a PC and as the ARM binary in an emulator, and simulates the whole mesh: airtime, path loss, collisions, stock relays and partitions. These are 30 random runs of a 10-device valley, about 1.2 km apart.

Simulated mesh results over 30 runs
ScenarioReached every device
Missing-child alert and "found"30 / 30
Report and sighting reach a moderator30 / 30
Endorsed child alert, no moderator29 / 30
Safety-chip SOS and its cancel30 / 30
Forged or adult-endorsed alerts shown0

Start with what you have.

The software comes first. Run it on a laptop today, and move to dedicated hardware as it arrives.

Product images are concept renders

Laptop or mini PC

Runs today
Concept render: a laptop with a USB GPS receiver and a LoRa radio
  • Python 3.10 or later (developed on Linux)
  • Several GB of RAM to build routes for a region, plus Java 17
  • A few GB of storage for maps, routes and place names
  • Optional USB GNSS receiver through gpsd
  • Optional LoRa node over USB, such as a RAK4631 (mesh on real radios is in development)

Your phone can be the screen over a hotspot you trust.

Android phone and a LoRa node

Planned
Concept render: an Android phone next to a pocket LoRa radio
  • Android phone with GPS
  • A Bluetooth LoRa node. For battery life, pick nRF52840: RAK WisMesh or RAK4631, Heltec T114.
  • To spend less, ESP32-S3 boards such as the Heltec V3 or LilyGO T-Beam Supreme will work too, but draw more power.

Raspberry Pi 5 field kit

Next
Concept render: a Raspberry Pi 5 with a touchscreen, GPS board and LoRa radio
  • Raspberry Pi 5, 8 or 16 GB, with a touchscreen
  • Quectel LC29H dual-band GNSS HAT
  • RAK4631 LoRa radio
  • An nRF52840 board as the safety chip
  • CO and temperature sensor pod

FieldAssist tablet

In design
Concept render: the FieldAssist tablet
  • Everything in one sealed shell: compute module, safety chip, dual-band GNSS, LoRa
  • Sensor pod for CO and temperature
  • Swappable cells, solar and crank charging

Any stock Meshtastic node on a rooftop or ridge extends the mesh. It relays packets it cannot read.

When no one is in range, look up.

Satellite messaging is the next horizon. When the mesh has no neighbour to hop to, an SOS could go to orbit instead, and one device with a sky link could carry a whole valley's messages out. We're evaluating short-burst satellite messaging and NB-NTN direct-to-device links. It is not part of version 1.

  1. Done

    Software that works today

    • Laptop app: guides, offline routes, field tools, Device Doctor
    • Safety-chip firmware, tested on a PC and as the ARM binary in an emulator
    • Mesh protocol proven in a simulated valley, with real attacks
  2. Next

    Field kit and Android

    • Raspberry Pi 5 field kit: measure power, radio range and the CO pod
    • Android app with a Bluetooth LoRa node
  3. Then

    The tablet

    • Custom carrier board and a sealed IP67 tablet shell
    • Sunlight-readable screen, e-paper status strip, glove buttons
    • Radio approvals per region and battery transport tests
  4. Exploring

    Beyond version 1

    • Satellite SOS fallback and a sky gateway for the mesh
    • Plug-in pods: radiation, pulse oximeter, IR thermometer
    • Carry-and-forward messages and shared map markers
    • Voice input

Built so that when help can't reach you, knowledge still can.

The software runs on a laptop today. The tablet is next.