Hardware Guide
Reference configurations at three performance tiers for building a GroundWave field kit.
8 min readOverview
GroundWave runs on any hardware that supports Docker with a 64-bit Linux OS (or Docker Desktop on macOS/Windows). The platform is intentionally lightweight — the Node.js server, PostgreSQL database, and tile server comfortably share a single low-power device. The limiting factor is usually storage for tile data and concurrent client count.
Three reference tiers are documented below: a budget ARM build centered on the Raspberry Pi 5, a standard x86 mini-PC suited to most deployments, and a premium tier for high user counts and extended-range radio integration.
Availability varies by region. Links in the sections below point to reference products — equivalents from other vendors are equally valid.
Budget Tier
The Raspberry Pi 5 8GB is the minimum recommended ARM build. It runs the full GroundWave stack on a <30W power budget, making it compatible with small battery banks and solar panels. Ideal for lightweight reconnaissance or training exercises where user count stays under 10.
Compute Specifications
| Component | Specification |
|---|---|
| CPU | Broadcom BCM2712, quad-core Cortex-A76, 2.4 GHz |
| RAM | 8 GB LPDDR4X |
| Storage | 64 GB microSD (Class 10 / A2 rated) |
| Connectivity | Gigabit Ethernet, Wi-Fi 802.11ac, Bluetooth 5.0 |
| Power draw | 10–25 W (idle to load) |
Accessories
- microSD card — Samsung Pro Endurance 64 GB or larger
- Case with heatsink — Argon ONE V3 or official Pi 5 active cooler
- Power supply — Official Raspberry Pi 5 USB-C PSU, 5 V / 5 A
Portable Power
Anker 737 Power Bank (24,000 mAh) — provides 8–12 hours of runtime for the Pi 5 plus router. Charges via USB-C PD at up to 140 W so it refills quickly when grid power is available.
Field Router
TP-Link TL-WR902AC — compact travel router in AP mode. Powered via USB from the battery bank. Supports up to 32 concurrent wireless clients at 5 GHz 802.11ac.
Supports 5–10 concurrent users. Suitable for small teams and extended field duration thanks to the low power draw.
Standard Tier
The Beelink Mini S12 Pro (Intel N100) delivers a significant step up in performance. The N100 is an x86 Alder Lake-N chip with four efficiency cores, hardware video decode, and fanless thermal design. The x86 architecture removes any ARM compatibility edge cases and offers better single-core performance for PostgreSQL query throughput.
Recommended for most deployments. This tier hits the best balance of performance, power efficiency, cost, and x86 compatibility. It is the configuration the GroundWave team uses for reference testing.
Compute Specifications
| Component | Specification |
|---|---|
| CPU | Intel N100, quad-core, up to 3.4 GHz |
| RAM | 16 GB DDR4 |
| Storage | 500 GB NVMe SSD |
| Connectivity | 2x Gigabit Ethernet, USB 3.2, HDMI 2.0 |
| Power draw | 10–15 W (fanless, passive cooling) |
Portable Power
EcoFlow RIVER 2 (256 Wh) — provides 12–18 hours of runtime for the mini-PC and router combined. Charges at 360 W AC input. LiFePO4 cells rated to 3,000 charge cycles. USB-A + USB-C outputs for peripheral devices.
Field Router
GL.iNet Beryl AX (MT3000) — Wi-Fi 6 (802.11ax) travel router. 2.4 + 5 GHz dual-band, 2.5 Gbps Ethernet uplink port, OpenWrt based for advanced configuration. Connects to the mini-PC via Ethernet; wireless clients get Wi-Fi 6 speeds.
Supports 15–25 concurrent users. The NVMe SSD accommodates large national tile sets (multi-GB) without microSD reliability concerns.
Premium Tier
The premium tier targets large-team operations with 30+ users, long runtimes, solar charging, and potential integration with high-bandwidth data sources (video feeds, CoT network bridges, Meshtastic relay nodes). The Intel NUC 13 Pro or Beelink SER7 (AMD Ryzen 7840HS) provides desktop-class multi-core performance in a 0.5 L form factor.
Compute Specifications
| Component | Specification |
|---|---|
| CPU | Intel Core i5-1340P / AMD Ryzen 7840HS (12–16 cores) |
| RAM | 16–32 GB DDR5 |
| Storage | 500 GB–1 TB NVMe SSD |
| Connectivity | 2x Thunderbolt 4, 2.5 Gbps Ethernet, Wi-Fi 6E, Bluetooth 5.3 |
| Power draw | 25–65 W (varies by load) |
Portable Power & Solar
EcoFlow RIVER 2 Max (512 Wh) — provides 6–10 hours of runtime for the premium compute unit plus router and peripherals. Pairs with a 100 W rigid solar panel (Renogy or EcoFlow brand) to sustain indefinite daytime operation in good conditions and partially recharge overnight loads.
Field Router
GL.iNet Flint 2 (MT6000) — Wi-Fi 6 router with four Gigabit Ethernet LAN ports, 2.5 Gbps WAN, and a 1.8 GHz quad-core CPU capable of routing at line speed. Supports mesh networking with additional GL.iNet nodes for extended coverage areas.
Supports 30+ concurrent users. Suitable for multi-day sustained operations, integration with CoT bridge hardware, and high-density tile datasets.
Storage Planning
Offline tile storage is the dominant driver of storage requirements. Vector tiles (Protomaps .pmtiles) are substantially more compact than raster tiles at equivalent zoom levels. Raster satellite tile sets are significantly larger.
| Coverage Area | Vector Tiles | Raster Satellite | Zoom Levels |
|---|---|---|---|
| City (metro area) | 50–200 MB | 500 MB–2 GB | 0–17 |
| State / Province | 100 MB–2 GB | 2–15 GB | 0–15 |
| Country (medium) | 1–3 GB | 15–50 GB | 0–14 |
| High-detail metro | 5–15 GB | 20–80 GB | 0–19 |
| Terrain DEM (country) | 200 MB–2 GB | N/A | 0–12 |
microSD cards are slower and less reliable than NVMe or SATA SSDs. For sustained tile serving under many concurrent clients, NVMe storage (Standard or Premium tier) is strongly recommended. Use A2-rated cards at minimum if microSD is unavoidable.
Performance Expectations
The following figures are from benchmarks run against reference hardware with 100 MB/s tile throughput, a full tile set loaded, and authentication enabled. Results will vary based on tile data size, network conditions, and client behavior.
| Metric | Budget (Pi 5) | Standard (N100) | Premium (i5/R7) |
|---|---|---|---|
| Recommended concurrent users | 5–10 | 15–25 | 30+ |
| Cold boot to ready | 45–75 s | 20–35 s | 15–25 s |
| Idle power draw | 5–8 W | 8–12 W | 18–30 W |
| Position update latency (p95) | <120 ms | <60 ms | <40 ms |
| Tile serve latency (p95, cached) | <80 ms | <30 ms | <20 ms |
| DB query throughput | ~400 qps | ~1,200 qps | ~3,000 qps |
Assembly Tips
Follow these steps when preparing a field kit for deployment:
- Connect Ethernet first. Always cable the compute unit to the router via Ethernet before configuring wireless. This avoids any chicken-and-egg problem with Wi-Fi setup and keeps the management path reliable.
- Label all cables and connectors. Field environments are dark and stressful. Color-coded cable ties and printed labels on power cables save significant time during rapid setup.
- Conduct a full test before deployment. Simulate field conditions — unplug from AC, connect to battery, connect 5+ client devices, and run for at least one hour. Verify GPS tracking, chat, and tile serving all function correctly.
- Pre-load tiles for your area of operations. Download the tile set via the setup wizard or admin panel while internet is available. Tile downloads can take 30 minutes to several hours depending on area size and connection speed.
- Fully charge all batteries before leaving. EcoFlow and Anker units display charge percentage. Depart with 100%. Carry a USB-C PD charger as a backup if vehicle or generator power is available in the field.
- Include the quick-start card in the kit. Print
docs/QUICKSTART.mdand laminate it. New operators should be able to connect a client device without any prior training using only the card.
Use a rigid Pelican-style case with foam cutouts for transport. Include a printed inventory checklist inside the lid. After each deployment, recharge all batteries before returning the kit to storage.