SPECTRE
Measurement equipment for paranormal investigation — a multi-sensor hub, wireless pods, and a full-spectrum camera, all writing to one timestamped log. It records evidence. What the evidence means is the investigator's call.
> status
// 2026-11-17
SPECTRE line: IN DESIGN — concept stage. Nothing fabricated, nothing orderable. The line queues behind IMP-1 batch one.
The interest list is open — message DeadbugLabs on Facebook or email imp-ai@muse.ai.
> the_honest_part
This equipment does not detect ghosts — and no Deadbug Labs page, listing, or manual will ever claim it does. It measures magnetic fields, RF energy, temperature, humidity, pressure, motion, and vibration, in real units, and it records all of it. What those measurements mean at a location is the investigator's interpretation. The incumbent market sells mystery; this line sells measurement. That is not a limitation of the product — it is the product.
One deliberate exclusion, on the record: no word-bank devices. A word bank driven by sensor noise performs — it does not measure. This line ships instruments, not performances.
> spectre_1
The hub. Handheld, ESP32-S3, one swappable 18650, USB-C, 1.47″ colour display. Every channel below is sampled and written to microSD as CSV on one shared timestamp — one card, one clock, one file per session. When something happens at 02:13, the log shows what every sensor in the building read at 02:13.
- DC magnetic field — 3-axis magnetometer, numeric µT per axis + magnitude
- AC EMF — sense coil + op-amp front end, calibrated milligauss readout. Done as an instrument: a number in real units, logged — a spike nobody was watching is still in the record
- AC electric field — E-field probe, numeric V/m readout
- RF density — broadband RF detector, mW/m² class readout + trend. With the coil, the hub covers the full broadband EMF trio — AC magnetic, AC electric, and RF — plus a DC field vector alongside
- RF sweep — AM/FM/SW receiver, adjustable sweep rate and direction, speaker output. The audio is receiver output — broadcast fragments and band noise, chopped by the sweep — and the sweep settings are logged so a session is reproducible
- EVP recorder — a dedicated audio channel, separate from the sweep receiver: WAV at 48 kHz / 24-bit class to the same card, on the same clock, with live headphone monitoring. A voice on the recording and a fragment off the sweep are never confused in the log
- Temperature / humidity — °C / %RH
- Barometric pressure — hPa, trended
- CO2 / air quality — NDIR CO2 in ppm plus an air-quality index, logged
- Carbon monoxide — electrochemical CO cell, ppm, logged, with a safety alarm. This is the debunker's instrument: CO poisoning and stale, high-CO2 air produce dread, headache, and a sense of presence — a documented class of “haunted house” reports with a physical cause. The alarm comes first; the data is second
- Vibration / knock — accelerometer with event thresholding, timestamped events
- Motion — PIR, timestamped events
- Module bay — an expansion bay, logged like any other channel. First bay item: a Geiger counter module — counts per minute, in the same record
Estes Mode — a hub firmware mode for the Estes Method: sweep audio routes to the noise-isolating headphone output only, the display dims and blanks, and the second operator marks each question in the log — a button press on the hub, or a voice mark on the EVP channel — so every answer fragment in the recording sits next to the question that preceded it, on the clock. The method is the investigators'; the mode just makes its record reviewable.
Performs as real equipment — design targets, verified at bring-up before any unit is described by them:
- Magnetometer: ±1600 µT class range, noise floor ≤0.5 µT RMS target, 10–50 Hz sampling
- AC EMF: 0.1 mG resolution target across ~0–100 mG in the calibrated band; per-unit calibration against a known reference field, cal date recorded in the session manifest
- E-field: ~0–1,000 V/m class; RF density: mW/m² class readout, detector band stated on the spec sheet
- RF sweep: FM 64–108 MHz plus AM/SW per the receiver; 50–300 ms per step, adjustable
- EVP audio: 48 kHz / 24-bit class WAV target, live monitor path; question marks written as event rows
- Temperature / humidity: ±0.2 °C / ±2 %RH class; pressure ±0.5 hPa class
- CO2: ±50 ppm + 5% of reading class; CO: ±5 ppm class target at low range, alarm threshold per safety practice — the CO cell is a consumable with a stated service life
- Logging integrity: one monotonic timestamp across hub, pods, and camera; events written at fire time, never rounded to the grid; each session writes CSV plus a manifest (start, firmware, channel list, sweep settings, calibration date)
> spectre_pod
The satellites. A small wireless node that sits in a room and watches one thing: a capacitive/EM proximity antenna — the proximity-pod function. A field disturbance near the antenna triggers the pod locally (RGB LED + buzzer, so the room sees and hears it) and reports to the hub, so the trigger lands in the hub's timestamped log with the pod's ID attached, correlated against every other channel.
A standalone proximity pod beeps in an empty room and tells nobody. A SPECTRE pod's trigger is a row in the record. No display, no card — the hub is the recorder, so pods stay cheap enough to run several rooms at once. A pod bought later joins the same hub and the same log.
Static pod variant — a second pod adds an E-field proximity channel: a static/electrostatic detector watching the local electric field rather than the capacitive antenna's near field. A different front end with a different false-trigger profile — a mixed set gives the log two independent proximity channels to correlate, instead of one beep to argue about.
POD LITE — the trigger-object pod: the light-up motion ball, done as a node. Ball-form, motion sensor and light — it flashes locally and reports the trigger to the hub with its pod ID attached. The same object investigators already buy by the bag, except its trigger is in the record. Priced to buy in sets.
> spectre_cam
A night camera built on the same rule as the rest of the line: it records evidence, and the investigator judges it.
- Full-spectrum optics — the sensor ships with no IR-cut filter, the standard full-spectrum conversion used in forensics imaging: sensitive across near-UV, visible, and infrared. Starlight-class low-light sensor — the camera works in dark rooms, not despite them
- Switchable illuminators — 850 nm IR (faint red glow), 940 nm IR (no visible glow), and a 365 nm UVA bank. Every saved frame records which illuminator was on, plus exposure and gain — the same shape under 940 nm and under UVA is different evidence, and the record keeps them separate
- Shape detection that saves the frame — on-device person/shape detection flags a “humanoid shape” event, and the camera saves the actual frame, with its full-spectrum channel data, to microSD and syncs the event into the hub log by timestamp
- CAM THERMAL — a thermal variant: a radiometric microbolometer thermal core blended as an overlay with the full-spectrum frame. Both frames are saved, side by side in the record, with the crosshair temperature in the log. A cold spot in the overlay is a temperature map anyone can re-read, not a colour smear. NETD <50 mK class target
- CAM DEPTH — a depth variant: a depth channel alongside the full-spectrum sensor, with skeletal mapping in the preview. Every mapped-figure event saves the actual depth frame and the full-spectrum frame that produced it — a stick figure drawn over a saved depth frame can be judged against the frame. The overlay is a mapping of depth data, labelled as such, never an identification
- Laser grid — a grid projector pen throws a dot grid across a room; the CAM watches the grid, and a grid break — dots displaced or occluded in a region — is logged as a motion event with the frame saved. The projector is a dumb accessory; the detection and the record live in the CAM, where they belong
DVR rig mode — professional teams run static multi-camera DVR rigs: fixed cameras, one recorder, one timeline. That is already this line's architecture, stated as a named mode: multiple CAMs as fixed nodes, hub-synced clocks, and a single session manifest covering every node — every camera's events and frames on the one hub timeline.
The car-camera parallel, stated honestly: dashboard cameras that “see ghosts” in cemetery videos feed a neural net that renders the shapes it detects — including humanoid false positives, figures drawn on the screen where no person stands. The display shows a rendering of a detection and keeps no evidence you can re-examine. SPECTRE CAM does the same class of detection deliberately, then does the part that matters: it saves the photograph. A false positive in this log is a frame anyone can look at and dismiss. The detection flag is labelled as what it is — a shape classification, not an identification.
UVA handling, plainly: 365 nm is UVA, the low-energy end of ultraviolet, and the array is still not something to look into at close range. The build guide carries the warning, the enclosure carries the label, and the UVA bank only runs while the camera is armed.
> estimates
Estimates only — nothing is locked. Final prices are set at batch open, like everything in the catalog.
- SPECTRE-1 hub — ESTIMATE $120–150 class
- SPECTRE POD — ESTIMATE $40–60 each
- POD LITE — ESTIMATE $25–35 each
- SPECTRE CAM — ESTIMATE $150–200 class
- SPECTRE CAM THERMAL — ESTIMATE $350–450 class
- SPECTRE CAM DEPTH — ESTIMATE $250–350 class
- Geiger module (hub bay) — ESTIMATE $60–90 class
- Laser grid pen (accessory) — ESTIMATE $20–30 class
- EM emitter / calibration source (accessory) — ESTIMATE $30–50 class — the line's own calibration reference source, dual-purposed as the field-experiment emitter investigators call an EM pump. A known field at a known frequency, described physically; no claims attach to it
- Bundle: hub + 2 pods — ESTIMATE ~$220 class
Anchors: a lights-only EMF meter runs ~$60; a sweep radio runs ~$70 and records nothing; a standalone proximity pod runs $50–90 and reports to nobody.
> interest
The line is in design, so there is nothing to order — but the interest list is open, on the same intake as everything else: message DeadbugLabs on Facebook or email imp-ai@muse.ai. When the line reaches a batch, the list hears first.
> responsible_use
Responsible use — Deadbug Labs products are tools for testing systems you own or have explicit authorization to test. Testing systems that do not belong to you, without authorization, is illegal. By purchasing, you agree to use these products only on your own systems or systems you are authorized to test, and you accept full responsibility for how you use them. Deadbug Labs is not liable for misuse.