Head-to-head against SquachWatch, Nyan Box, ESP32 Marauder, Flipper Zero, Wired Hatters Banshee and Chameleon Ultra — plus a works-with map and a reach-for-it decision matrix

*Figure 11.1 — The HaleHound touch home screen. Its signature is five radios and six-band coverage on one $7–18 board; the comparisons below turn on where that breadth helps and where a specialist wins. Photo: HaleHound.com.*

11.1 About this Volume

Volume 11 situates HaleHound against the other tools it is most often weighed against, and ends with a plain decision rule for when it is the right thing to pick up. The comparison targets fall into three groups:

Same hardware, different job. SquachWatch runs on the identical Cheap Yellow Display (CYD) board but is a counter-surveillance detector; it is HaleHound’s mirror image and the sharpest way to understand what HaleHound is (Section 3).
Overlapping handhelds. Nyan Box, ESP32 Marauder and the Wired Hatters Banshee are other ESP32-class handhelds whose coverage overlaps HaleHound’s in parts (Sections 4, 5, 7).
Different silicon, complementary role. Flipper Zero is the polished generalist most people already own (Section 6), and Chameleon Ultra is an NFC emulator HaleHound actively drives over BLE rather than competes with (Section 8).

The treatment is category-level throughout, consistent with Vol 8: what class of work each tool does well, where the overlap and the gaps are, and the tradeoffs — not step-by-step procedures.

Note — Every claim about radios, bands and power for HaleHound here traces to Vols 2–8. The comparison targets are described at reference level; where a competitor’s exact feature set moves independently (Marauder, Ghost ESP, Flipper custom firmware), the hub’s own dedicated deep dives are the authority and are cross-referenced in prose.

11.2 The one-screen scorecard

The quickest way to see where HaleHound sits is band reach and radio count against each rival. HaleHound’s distinguishing trait is breadth on one cheap board: five radios (ESP32 Wi-Fi, ESP32 BLE, external CC1101, external NRF24, external PN532/GPS) spanning sub-GHz through 2.4 GHz, touch-driven, standalone.

Table 1 — 2. The one-screen scorecard

Tool	Platform	Sub-GHz	2.4 GHz Wi-Fi	5 GHz	BLE	NRF24	NFC/RFID	GPS	Posture	FW license
HaleHound-CYD	ESP32 CYD	CC1101 300–439 MHz	Yes	No	Yes	Yes (ext)	PN532 (+ChamUltra)	Yes	Offensive (+Blue Team)	Proprietary
SquachWatch	ESP32 CYD	— (listen via LoRa board)	Scan/detect	C5 board only	Detect	—	—	Wardrive (T-Watch)	Detector / defensive	GPL-3.0
Nyan Box	ESP32-WROOM-32U	—	Scan	No	Yes	3× NRF24	—	—	Education / detect+offensive	MIT
ESP32 Marauder	ESP32 (C5 for v8)	—	Yes	v8/C5 only	Yes	Optional	—	Optional	Wi-Fi/BLE offensive	Open source
Flipper Zero	STM32 (ESP32 add-on)	CC1101 built-in	Add-on only	No	Add-on	—	LF 125k + HF 13.56M	Add-on	Generalist multi-tool	Open (region-locked)
Wired Hatters Banshee	ESP32-C5 + ESP32-S3	—	Yes	Yes (C5)	Yes	Yes	—	Yes	Premium multi-modal	GhostESP (open)
Chameleon Ultra	nRF52840	—	—	—	BLE link	—	HF+LF emulator (8+8 slots)	—	NFC emulate/attack	Open (GPL-3.0)

   Radio breadth on ONE board — HaleHound's headline
   ═══════════════════════════════════════════════════════════════
   HaleHound    sub-GHz │ 2.4 NRF │ 2.4 WiFi │ BLE │ NFC │ GPS   [6 vectors]
   Marauder             │         │ 2.4 WiFi │ BLE │     │        [Wi-Fi/BLE]
   Flipper      sub-GHz │         │ (add-on) │(add)│ NFC │(add)   [RF + NFC + IR]
   Nyan Box             │ 3×NRF24 │ 2.4 scan │ BLE │     │        [2.4 GHz heavy]
   Chameleon            │         │          │ BLE │ NFC │        [NFC only]
   Banshee              │         │ 5+2.4 Wi │ BLE │ NRF │ GPS    [premium, 5 GHz]

11.2.1 Capability-per-dollar

HaleHound’s thesis is vectors per dollar, so the most honest single chart counts transmit/attack vectors against entry price. The bars below count distinct radio vectors (sub-GHz, 2.4 GHz-NRF24, Wi-Fi, BLE, NFC, GPS) and set them beside the cheapest way to own each tool. Prices are 2026-10-16 snapshots and mix new/kit/used markets, so treat the ratio as a shape, not a quote.

   Vectors vs entry price (vectors shown as █, entry $ at right)
   ═══════════════════════════════════════════════════════════════
   HaleHound (DIY 2.8″)  ██████   6 vectors .......... ~$139
   HaleHound (bare board)██████   6 vectors (DIY all) . ~$16 board + parts
   Flipper Zero          ████     4 (RF/NFC/IR/GPIO)* .. ~$169  *Wi-Fi add-on
   ESP32 Marauder        ██       2 (Wi-Fi/BLE) ........ ~$30 board
   Nyan Box              ███      3 (3×NRF24/BLE/scan) . ~$ (vendor)
   Chameleon Ultra       █        1 (NFC) .............. ~$ (vendor)
   Banshee               ██████+  6+ (adds 5 GHz, HID) . ~€240
   ───────────────────────────────────────────────────────────────
   Read: HaleHound and Banshee cover the most vectors; HaleHound does
   it an order of magnitude cheaper, Banshee adds 5 GHz + wired/HID.

Table 2 — 2.1 Capability-per-dollar

Tool	Cheapest path (2026-10-16)	Distinct vectors	$/vector (approx)
HaleHound (DIY 2.8″ kit)	$139	6	~$23
HaleHound (bare CYD + sourced parts)	~$16 board + modules	6	lowest
Flipper Zero	~$169 (+Wi-Fi devboard)	4 native	~$42
ESP32 Marauder	~$30 board	2	~$15
Wired Hatters Banshee	~€240	6+ (incl. 5 GHz)	~€40

The caveats are real: a Marauder board is cheaper per vector because it only has two, and “6 vectors” on HaleHound still means 2.4 GHz-ceiling Wi-Fi and HF-only NFC. The chart measures span, not depth — Sections 5–6 are where depth decides.

11.3 vs SquachWatch — same board, opposite posture

SquachWatch is the single most illuminating comparison because the hardware is identical — both run on the ESP32-2432S028R CYD, both are web-flashed, both scale a touch UI across 2.8″/3.5″ panels. What differs is the entire intent.

Table 3 — 3. vs SquachWatch — same board, opposite posture

Axis	HaleHound-CYD	SquachWatch-CYD
Author	Jesse C. Hale (`JesseCHale`)	skizzophrenic / “Talking Sasquach”
Firmware license	Proprietary (source closed)	GPL-3.0 (source open)
Core job	Transmit / attack across 6 vectors	Listen / name surveillance gear
Default on boot	VALHALLA gate → offensive or Blue Team	Passive detector, transmit off by default
External radios	CC1101, NRF24, PN532, GPS	Optional LoRa (T-Watch), GPS (wardrive)
Output	Loot to SD (captures, creds, dumps)	Alerts, HUNT gauge, CSV log, watch list
Legal centre of gravity	Authorization required to use safely	Safe to run almost anywhere (passive)

The two are best understood as a matched pair on one platform: SquachWatch answers “what is watching me?”, HaleHound answers “what can I test against here?” HaleHound even carries a defensive slice that overlaps SquachWatch’s territory — the Jam Detect suite (deauth-flood/carrier-jamming/broadband detection) and the Flock You ALPR/Raven BLE-fingerprint detector — but those are a minority of its modules and are reachable in Blue Team mode. SquachWatch is defensive end-to-end; HaleHound is offensive-first with a defensive mode bolted on.

Note — The vendor persona overlap is a trap: HaleHound’s seller uses a “Talking Sasquatch” (with a t) branding on some cases, while SquachWatch’s author publishes as “Talking Sasquach” (no t). Different people, different projects, opposite postures. See the project CLAUDE.md naming note.

One consequence of the shared hardware is economic: a single exposed-SPI CYD can be either tool on any given day. An operator can keep one board and reflash between HaleHound (offensive, when authorized) and SquachWatch (detector, for everyday carry), swapping the posture without swapping the hardware. The only costs are the reflash step (web flasher, a laptop and cable) and that the two never run at once. For someone who wants both a legal-to-carry detector and an authorized-use attack tool, “two firmwares, one $15 board” is a genuine option the rest of this volume’s rivals cannot match.

   Posture axis on the SAME CYD board
   ═══════════════════════════════════════════════════════════
   DEFENSIVE ◀─────────────────────────────────────▶ OFFENSIVE
   SquachWatch                           HaleHound (Blue Team) ─┐
   (detector, GPL)                       HaleHound (VALHALLA) ──┘
                                         (proprietary, TX at max power)

11.4 vs Nyan Box — the multi-NRF detector-handheld

Nyan Box (Nyan Devices) is an education-first multi-radio handheld — ESP32-WROOM-32U + three NRF24L01+ radios + 0.96″ OLED + a 2500 mAh battery — with MIT-licensed firmware (nyanBOX). Its signature is the triple-NRF24 array, which allows genuinely parallel 2.4 GHz channel work, and a feature set weighted toward drone Remote ID detection and hidden-camera detection.

Table 4 — 4. vs Nyan Box — the multi-NRF detector-handheld

Axis	HaleHound-CYD	Nyan Box
Display	2.8″/3.5″ color touch	0.96″ OLED
2.4 GHz radios	1 NRF24 (2 on Cinder Ferret V2.2)	3× NRF24
Sub-GHz	CC1101 300–439 MHz	None
NFC / GPS	PN532 + GPS	None
Firmware license	Proprietary	MIT (open)
Lean	Broad offensive + some detect	Detect-leaning, education, drone/camera

Where they overlap is 2.4 GHz and drone awareness. Nyan Box’s three NRF24s beat HaleHound’s one (or two) for parallel-channel sniffing; HaleHound beats Nyan Box on sub-GHz, NFC, GPS, a color touch UI, and offensive Wi-Fi/BLE breadth. The choice is detector-density on 2.4 GHz (Nyan Box) vs a broad offensive toolkit (HaleHound). For the drone-detection use specifically, HaleHound’s dual-radio passive RID (ESP32 Wi-Fi + NRF24 on separate cores) and RID-spoof are more offensive; Nyan Box frames the same band detect-first. See the Nyan Box deep dive.

Table 5 — 4. vs Nyan Box — the multi-NRF detector-handheld

Overlap axis	HaleHound	Nyan Box	Edge
Parallel 2.4 GHz channels	1 NRF24 (2 on V2.2)	3× NRF24	Nyan Box
Drone Remote ID	Detect + spoof	Detect-first	HaleHound (offensive)
Display	Color touch	0.96″ OLED	HaleHound
Sub-GHz / NFC / GPS	Yes / yes / yes	No / no / no	HaleHound
Firmware openness	Proprietary	MIT (open)	Nyan Box

11.5 vs ESP32 Marauder — the Wi-Fi/BLE specialist

ESP32 Marauder (JustCallMeKoko) is the canonical open-source Wi-Fi + BLE pentest firmware. It is the reference against which every ESP32 Wi-Fi tool is measured, and it runs on a wide range of ESP32 hardware (the v8 line targets the ESP32-C5 for 5 GHz — Vol 10 §10).

Table 6 — 5. vs ESP32 Marauder — the Wi-Fi/BLE specialist

Axis	HaleHound-CYD	ESP32 Marauder
Wi-Fi 2.4 GHz	Yes	Yes (the specialty)
5 GHz	No	Yes on C5 (v8)
BLE	Yes	Yes
Sub-GHz (CC1101)	Yes	No (Wi-Fi/BLE focus)
NRF24 2.4 GHz	Yes	No (not core)
NFC / GPS	PN532 + GPS	GPS optional; no NFC
License	Proprietary	Open source
Maturity of Wi-Fi tooling	Broad but one of six vectors	Deep, mature, widely audited

Marauder is the sharper, more mature, open Wi-Fi/BLE instrument, and the only one of the pair with a 5 GHz path (on C5). HaleHound’s Wi-Fi/BLE is one of six vectors rather than the whole product, but it adds sub-GHz, NRF24, NFC, GPS and drone work that Marauder does not attempt. For a pure 2.4/5 GHz Wi-Fi engagement, Marauder (especially on C5) is the specialist pick; for a single device that also does sub-GHz replay, NFC and tracker work, HaleHound carries more vectors. The hub’s ESP32 Marauder Firmware deep dive is the authority on Marauder’s capabilities.

11.6 vs Flipper Zero — the polished generalist

Flipper Zero is the device most operators already own, and the comparison is less “which is better” than “what each is for.” Flipper is an STM32-based multi-tool with a built-in CC1101 sub-GHz radio, 125 kHz LF + 13.56 MHz HF NFC/RFID, iButton, IR, and GPIO, wrapped in a polished UI with a large app and .sub ecosystem. Its Wi-Fi/BLE attack capability is not native — it relies on an external ESP32 Wi-Fi dev board. Stock firmware is region-locked; custom firmware (Momentum, Unleashed) removes guardrails.

Table 7 — 6. vs Flipper Zero — the polished generalist

Axis	HaleHound-CYD	Flipper Zero
Sub-GHz	CC1101 300–439 MHz (+E07 20 dBm)	CC1101 built-in (region-locked stock)
`.sub` files	Reads/transmits Flipper .sub from SD	Native `.sub` ecosystem
NFC	PN532 HF (+ChamUltra over BLE)	LF 125 kHz + HF 13.56 MHz, mature
Wi-Fi/BLE attack	Native (ESP32 built-in)	External ESP32 dev board required
2.4 GHz NRF24	Yes	Via external module only
GPS / drone RID	Yes / yes	External module / apps
Build / UI	DIY, touch, color	Polished consumer product
TX power	Max by design (+20.5/+20/+12–20/+9 dBm)	Lower, region-limited stock

The clean division: Flipper is the refined generalist with the best NFC and the smoothest sub-GHz workflow; HaleHound is the higher-TX, Wi-Fi/BLE-native, multi-radio board that reads Flipper’s own .sub files. The .sub compatibility makes them complementary — a signal captured or curated on either can be moved to the other. For LF (125 kHz) RFID specifically, Flipper has a radio HaleHound’s PN532 (HF-only) does not; for Wi-Fi/BLE offensive work without an add-on, HaleHound is self-contained where a stock Flipper is not.

Tip — The /subghz/ folder on HaleHound’s SD takes standard Flipper .sub files (RAW, Princeton, CAME, Nice FLO). A library curated on a Flipper transfers directly — the two tools interoperate at the file level rather than competing.

11.6.1 The NFC depth gap (and where Proxmark3 sits)

The one place a Flipper (and a Proxmark3) clearly out-reaches HaleHound is RFID. HaleHound’s PN532 is 13.56 MHz HF only; it cannot touch the 125 kHz LF badges that dominate legacy building access. Flipper carries both an LF (125 kHz) and an HF (13.56 MHz) front end; Proxmark3 is the lab-grade instrument for both bands with the deepest attack library.

Table 8 — 6.1 The NFC depth gap (and where Proxmark3 sits)

NFC/RFID need	HaleHound (PN532)	Flipper Zero	Proxmark3	Chameleon Ultra
HF 13.56 MHz scan/read/clone	Yes	Yes	Yes (deep)	Yes (emulate)
LF 125 kHz badges	No	Yes	Yes (deep)	Yes (8 LF slots)
MIFARE Crypto1 / key brute	Yes	Yes	Yes	Yes (mfkey32)
NTAG read/write/lock	Yes (NTAG Tools)	Yes	Yes	Yes
Emulation slots	— (live clone)	limited	limited	8 HF + 8 LF

The practical read: for HF/NTAG tasks HaleHound’s PN532 suite is capable; for LF 125 kHz reach for a Flipper or Proxmark3; for emulation depth and key recovery pair a Chameleon Ultra over BLE (Section 8). HaleHound does not try to be the best NFC tool — it tries to put a workable NFC suite in the same box as five other radios.

The Wired Hatters Banshee is the flagship end of this category: a dual-MCU handheld (ESP32-C5 + ESP32-S3) with NRF24, GPS, triple IR TX + RX, Ethernet, USB-A host (HID), stereo mics, UV/white flashlights, a main TFT plus a status OLED, and joystick/touch/encoder input, running GhostESP. It is priced around €240 and its C5 gives it the 5 GHz reach HaleHound structurally lacks.

Table 9 — 7. vs Wired Hatters Banshee — the premium multi-modal

Axis	HaleHound-CYD	Wired Hatters Banshee
MCU	Single ESP32 (CYD)	Dual: ESP32-C5 + ESP32-S3
5 GHz Wi-Fi	No	Yes (C5)
Sub-GHz	CC1101 300–439 MHz	Not a core radio
NRF24 2.4 GHz	Yes	Yes
Extras	PN532 NFC, GPS	Ethernet, USB-A HID, IR×3, mics, lights
Firmware	Proprietary	GhostESP (open)
Price (as of 2026-10-16)	$139–245 (SKU-dependent)	~€240

Banshee is the more capable and more expensive instrument — dual MCUs, 5 GHz, Ethernet and USB-HID put it in a different class and price bracket. HaleHound’s counter is sub-GHz plus NFC on a far cheaper board: the CC1101 (and E07 PA) and the PN532 NFC suite are vectors the Banshee’s feature list does not emphasise, and a complete HaleHound costs a fraction of a Banshee. The decision is 5 GHz + wired/HID breadth at premium price (Banshee) vs sub-GHz + NFC + low cost (HaleHound). See the Wired Hatters Banshee deep dive.

The two also differ in what a failure or loss costs. A HaleHound is cheap enough to treat as semi-disposable field kit — a lost or bricked $139 unit is an inconvenience; a ~€240 Banshee is an asset to protect. For high-churn or higher-risk carry, the price floor is itself a feature of the HaleHound side of the comparison. The Banshee’s dual-MCU design, by contrast, buys genuine concurrency (one MCU on 5 GHz Wi-Fi, another handling the rest) that a single-ESP32 HaleHound approximates only with dual-core task splitting on one radio set.

11.8 vs / with Chameleon Ultra — the NFC companion

Chameleon Ultra (RRG/Proxgrind) is an nRF52840-based NFC/RFID emulator with eight HF and eight LF slots, a Crypto1 attack suite, and a BLE link. The relationship with HaleHound is cooperative, not competitive: HaleHound’s RFID menu offers a Chameleon Ultra backend over BLE, using it for NTAG read/write and mfkey32 key recovery — work beyond what the on-board PN532 does. HaleHound becomes the touch controller; the Chameleon does the NFC heavy lifting.

   HaleHound ⇄ Chameleon Ultra (BLE link)
   ═══════════════════════════════════════════════════════════
   HaleHound (touch UI, RFID menu)  ──BLE──▶  Chameleon Ultra
     backend picker: PN532 / ChamUltra / ST25R3916(stub)        (nRF52840)
                                                 │
     NTAG read/write ◀───────────────────────────┤
     mfkey32 key recovery ◀───────────────────────┘

Table 10 — 8. vs / with Chameleon Ultra — the NFC companion

Axis	HaleHound PN532 backend	Chameleon Ultra (BLE backend)
Role in pair	Controller + default HF suite	Emulator / key-recovery engine
Slots	n/a (live card suite)	8 HF + 8 LF emulation slots
mfkey32	No	Yes
NTAG read/write	Yes (NTAG Tools)	Yes
Standalone	Yes	Yes (own UI/app)

So the question is rarely “HaleHound or Chameleon Ultra” — a Chameleon owner gains NFC depth by pairing it to a HaleHound over BLE, and a HaleHound gains emulation-slot and mfkey32 capability it lacks on the PN532 alone. See the Chameleon Ultra deep dive for its standalone capabilities.

11.9 The works-with map

HaleHound interoperates with several tools at the file level or over a radio link. The map below is the practical “these play together” summary.

   HaleHound works-with map
   ═══════════════════════════════════════════════════════════════
                         ┌───────────────────────────┐
     Flipper Zero  ──────┤ .sub files (RAW/Princeton/ │──▶ /subghz/ on SD
     (sub-GHz lib)       │  CAME/Nice FLO)            │    .Sub Read module
                         └───────────────────────────┘
                         ┌───────────────────────────┐
     Chameleon Ultra ────┤ BLE link (NFC backend)     │──▶ RFID menu picker
     (NFC emulator)      │  NTAG r/w + mfkey32        │
                         └───────────────────────────┘
                         ┌───────────────────────────┐
     hashcat (host) ◀────┤ EAPOL/PMKID in hashcat fmt │──  /eapol/ on SD
                         └───────────────────────────┘
                         ┌───────────────────────────┐
     WiGLE / mapping ◀───┤ GPS-tagged wardrive CSVs   │──  /wardriving/ on SD
                         └───────────────────────────┘
                         ┌───────────────────────────┐
     SquachWatch (det.) ─┤ same CYD board, reflash    │──  swap firmware
                         └───────────────────────────┘

Table 11 — 9. The works-with map

Partner	Link	What moves	Direction
Flipper Zero	microSD `.sub` files	Sub-GHz captures (RAW/Princeton/CAME/Nice FLO)	Either way
Chameleon Ultra	BLE	NFC control: NTAG r/w, mfkey32	HaleHound drives Chameleon
hashcat (desktop)	SD export	EAPOL/PMKID in hashcat format	HaleHound → host
WiGLE / GIS	SD export	GPS-tagged AP CSVs from wardriving	HaleHound → host
IoT Recon creds	SD `/creds.txt`	Custom credential list	host → HaleHound
SquachWatch	reflash same board	— (firmware swap, not data)	n/a

Note — “Works with SquachWatch” means only that the same CYD board can be reflashed from one to the other; they do not exchange data and cannot run at the same time. The genuine data/link interop is with Flipper (.sub), Chameleon Ultra (BLE), and desktop tools (hashcat, WiGLE) via the SD card.

11.9.1 What it does not interoperate with

It is worth being explicit about the non-links, because the “multi-protocol” framing can imply more integration than exists. HaleHound does not share live radio state with Marauder, Nyan Box or a Banshee — those are separate devices with their own firmware, and any coordination is manual (two operators, two screens). It does not import Proxmark3 dumps, and it does not drive a Flipper (the relationship is file-level .sub exchange, not control). The only device HaleHound actively controls is a Chameleon Ultra over BLE; everything else is either file exchange via SD or simply a separate tool used alongside it.

Table 12 — 9.1 What it does not interoperate with

Relationship	Type	Live link?
Chameleon Ultra	Control (BLE)	Yes
Flipper Zero	File exchange (`.sub`)	No (SD sneakernet)
hashcat / WiGLE	Export	No (SD → host)
Marauder / Nyan / Banshee	Separate tool	No
Proxmark3	Separate tool	No

11.10 Decision matrix — reach for HaleHound when…

   "Reach for HaleHound when…"           "Reach for something else when…"
   ═══════════════════════════════════   ═══════════════════════════════════
   ✓ One cheap board must cover           ✗ 5 GHz Wi-Fi is required
     sub-GHz + 2.4 GHz + Wi-Fi + BLE        → Banshee / Marauder v8 (C5)
     + NFC + GPS in one touch UI          ✗ Deepest, audited Wi-Fi/BLE tooling
   ✓ Max TX power matters                   → ESP32 Marauder (open, mature)
     (Wi-Fi +20.5, NRF24 +20, CC1101      ✗ Best NFC incl. LF 125 kHz
      +12/+20 dBm)                           → Flipper Zero / Proxmark3
   ✓ Flipper .sub playback + capture      ✗ Pure counter-surveillance detect
     on a color touch handheld              → SquachWatch (same board, GPL)
   ✓ Driving a Chameleon Ultra over BLE   ✗ Parallel-channel 2.4 GHz density
     for NFC depth                          → Nyan Box (3× NRF24)
   ✓ Drone Remote ID detect/spoof +       ✗ Open-source firmware is a
     a defensive Blue Team mode             requirement → anything but HaleHound
   ✓ Capability-per-dollar is the          ✗ Ethernet / USB-A HID / wired
     priority ($139–245 all-in)             → Banshee

11.10.1 What HaleHound adds to a bench that already has a Flipper

Many operators arriving at HaleHound already own a Flipper Zero, so the sharper question is not “which?” but “what does adding a HaleHound change?” The answer is concentrated in three places: native Wi-Fi/BLE offensive work without an add-on, a second NRF24-class 2.4 GHz radio (MouseJack, promiscuous sniffing), and drone Remote ID detect/spoof plus a color touch UI with on-SD loot management. Where the two overlap — sub-GHz capture/replay and HF NFC — the Flipper’s workflow is more polished, and the .sub interop means a sub-GHz library built on the Flipper carries straight over.

Table 13 — 10.1 What HaleHound adds to a bench that already has a Flipper

On a bench with a Flipper, HaleHound adds	HaleHound does NOT replace the Flipper for
Native Wi-Fi + BLE offensive suite (no devboard)	Polished sub-GHz UX + mature `.sub` ecosystem
2.4 GHz NRF24 (MouseJack, Goodspeed sniff)	LF 125 kHz RFID (Flipper has it; PN532 doesn’t)
Drone RID detect/spoof, dual-radio passive RX	iButton / 1-Wire, IR blaster, GPIO breakout
Higher max TX (+20.5 dBm Wi-Fi, +20 dBm NRF/E07)	App ecosystem + consumer polish
Color touch UI, on-SD loot browser	—

11.10.2 The three questions

The decision reduces to three questions:

Breadth or depth? If the job wants one board across the most vectors for the least money, HaleHound wins. If the job is one band done expertly, a specialist (Marauder for Wi-Fi/BLE, Flipper/Proxmark for NFC, Nyan Box for 2.4 GHz density) wins.
Is 5 GHz or open source non-negotiable? Either one rules HaleHound out — 5 GHz needs C5 silicon (Vol 10 §10), and HaleHound’s firmware is proprietary. A C5 board (Banshee, Marauder v8) answers 5 GHz; any of the open cousins answer the licensing requirement.
Offensive or defensive? Offensive-first with a defensive fallback is HaleHound (VALHALLA/Blue Team); detect-only is SquachWatch on the very same hardware.

Table 14 — 10.2 The three questions

Scenario	Best pick	Why not HaleHound
Broad authorized red-team on one board	HaleHound	— (its home turf)
5 GHz Wi-Fi audit	Banshee / Marauder v8	ESP32 CYD is 2.4 GHz only
Deep Wi-Fi/BLE engagement	ESP32 Marauder	Marauder is the mature specialist
LF 125 kHz badge work	Flipper / Proxmark3	PN532 is HF-only
NFC emulation + key recovery	Chameleon Ultra (paired to HaleHound)	HaleHound drives it, doesn’t replace it
Counter-surveillance sweep	SquachWatch	HaleHound is offensive-first
2.4 GHz parallel sniffing	Nyan Box	1–2 NRF24 vs Nyan’s 3

11.11 Summary and cross-references

HaleHound’s edge is breadth-per-dollar. Five radios and six vectors (sub-GHz, 2.4 GHz NRF24, Wi-Fi, BLE, NFC, GPS) on a $7–18 board with max-power TX and a color touch UI — no single rival matches that span at the price.
Its two structural limits are 5 GHz and licensing. The classic ESP32 cannot do 5 GHz (reach for C5 hardware — Banshee, Marauder v8), and the firmware is proprietary (reach for an open cousin if that matters).
Its closest mirror is SquachWatch — the same CYD board, GPL, detect-only — and its closest partners are Flipper (shared .sub files) and Chameleon Ultra (NFC backend over BLE), which it works with rather than against.
Specialists still win their lanes: Marauder for Wi-Fi/BLE depth and 5 GHz, Flipper/Proxmark for NFC (especially LF), Nyan Box for 2.4 GHz density, Banshee for wired/HID breadth and 5 GHz at premium price.

For the capability categories behind these comparisons see Vol 8; for the ecosystem and the 5 GHz gap see Vol 10; for the field cards, legal envelope and glossary see Vol 12.

HaleHound Volume 11 — Comparison & Where It Fits

11.1 About this Volume

11.2 The one-screen scorecard

11.2.1 Capability-per-dollar

11.3 vs SquachWatch — same board, opposite posture

11.4 vs Nyan Box — the multi-NRF detector-handheld

11.5 vs ESP32 Marauder — the Wi-Fi/BLE specialist

11.6 vs Flipper Zero — the polished generalist

11.6.1 The NFC depth gap (and where Proxmark3 sits)

11.8 vs / with Chameleon Ultra — the NFC companion

11.9 The works-with map

11.9.1 What it does not interoperate with

11.10 Decision matrix — reach for HaleHound when…

11.10.1 What HaleHound adds to a bench that already has a Flipper

11.10.2 The three questions

11.11 Summary and cross-references

Comments (0)

HaleHound Volume 11 — Comparison & Where It Fits

11.1 About this Volume

11.2 The one-screen scorecard

11.2.1 Capability-per-dollar

11.3 vs SquachWatch — same board, opposite posture

11.4 vs Nyan Box — the multi-NRF detector-handheld

11.5 vs ESP32 Marauder — the Wi-Fi/BLE specialist

11.6 vs Flipper Zero — the polished generalist

11.6.1 The NFC depth gap (and where Proxmark3 sits)

11.7 vs Wired Hatters Banshee — the premium multi-modal

11.8 vs / with Chameleon Ultra — the NFC companion

11.9 The works-with map

11.9.1 What it does not interoperate with

11.10 Decision matrix — reach for HaleHound when…

11.10.1 What HaleHound adds to a bench that already has a Flipper

11.10.2 The three questions

11.11 Summary and cross-references

Comments (0)