Working observation / Maker Labs
A Raspberry Pi can do dependable field work when storage, power, networking, recovery, and the enclosure are designed as one system.
Most people buy a Raspberry Pi because it is cheap. The useful ones get bought because they survive a power cut, boot headless, and still phone home.
Raspberry Pi documents NVMe boot and the Pi 5 PCIe interface, but the storage choice alone does not make sudden power loss safe. Filesystem behavior, buffered writes, service recovery, and a deliberate shutdown path still matter. Start with the official Raspberry Pi hardware guidance, then test the assembled system under the failures it will actually see.
A useful setup boots unattended, mounts durable storage, starts the service, and keeps a bounded local queue when the network is unavailable.
[Unit]
Description=Workshop Field Drop
After=network-online.target
[Service]
Type=simple
ExecStart=/usr/bin/python3 /opt/fielddrop/main.py
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.targetThat pattern can support temperature, door-state, motion, or equipment alerts: record locally first, then send a small update when connectivity returns.
Local inference may be possible, but memory size alone does not answer whether a model will meet the required latency, accuracy, power, and thermal limits. Benchmark the exact workload before treating it as part of the field design.