RuView

RuView is an open-source spatial-intelligence stack from Cognitum / ruvnet that turns ordinary WiFi into real-time presence, motion, and vital-sign-style sensing—without cameras. The project lives at github.com/ruvnet/RuView (~103k★) and is productized on the Cognitum site at https://cognitum.one/ruview.

Instead of computer vision, RuView treats commodity WiFi radio as a sensor: multipath and channel-state cues are mapped into spatial activity so homes, offices, and edge deployments can detect occupancy and coarse physiology while keeping visual privacy. It sits inside the broader Cognitum ecosystem alongside Seed and ruOS.

Highlights:

• Open GitHub repo with strong daily-trending signal; product page at cognitum.one/ruview;
• Camera-free sensing on commodity WiFi hardware;
• Presence, motion, and vital-sign-style monitoring as first-class outputs;
• Positioned as spatial intelligence for privacy-sensitive environments;
• Part of Cognitum’s Seed / ruOS stack rather than a one-off demo.

Why it matters

Most presence and health-adjacent sensing still depends on cameras or wearables. RuView’s bet is that WiFi CSI and related RF features are already everywhere, so spatial intelligence can ship without new optics or on-body devices. That matters for privacy-sensitive rooms, eldercare, security, and robotics where visual streams are unwanted or restricted.

The GitHub surface and Cognitum product page make it a concrete named product—not a paper-only idea. High star count and recurring trending placement indicate developer mindshare around RF sensing as an alternative to vision pipelines. Integration with Cognitum Seed and ruOS suggests a path from open sensing core to a broader device/OS story.

Limits

WiFi sensing accuracy depends on AP placement, firmware access to CSI, environment multipath, and regulatory RF rules; results will vary by hardware. Vital-sign-style claims should be treated as sensing estimates, not medical devices, unless certified. Camera-free does not mean risk-free: RF occupancy data can still leak behavioral patterns. Confirm license, hardware requirements, and Cognitum commercial terms before production use. Do not conflate RuView with unrelated “review” or generic WiFi-analytics tools.

1. Open https://github.com/ruvnet/RuView and https://cognitum.one/ruview to confirm current docs, license, and hardware requirements;
2. Clone or install per the repo README; verify your WiFi chipset/AP exposes the needed CSI or sensing hooks;
3. Run presence/motion demos in a controlled room, then tune thresholds for your layout;
4. If adopting Cognitum Seed / ruOS, follow their product docs for production packaging; treat vital-sign outputs as experimental sensing unless you have clinical validation.