FleetPolicy

Inspiration

Small businesses increasingly manage Ring cameras across multiple locations. A configuration change, offline device, or unexpected inventory change can quietly move the fleet away from the privacy and security policy an operator approved. FleetPolicy makes that gap visible, explainable, and reviewable.

What it does

FleetPolicy is a read-only Ring fleet posture tool. It captures versioned device evidence, evaluates it against a deterministic policy, and creates findings with expected and observed values, source paths, stable IDs, timestamps, and SHA-256 evidence hashes. Operators can inspect evidence, acknowledge or resolve findings, record time-limited waivers with mandatory notes, review the append-only audit trail, and export a posture report. FleetPolicy never changes a physical device.

How we built it

The Node.js adapter makes authenticated server-side calls to the official Ring API origin. It discovers devices and reads status, capabilities, coarse location, and configuration resources. It follows only same-origin pagination, validates responses, fails closed when coverage is missing, and never stores or returns the bearer token. A dependency-free local dashboard provides the review workflow and JSON/HTML report export. The evaluator uses canonical hashing and six declarative comparison operators; 44 automated tests cover the core behavior.

Ring integration and evidence boundary

An authenticated Ring Developer Playground run discovered one official simulator device and successfully read all four required device-detail surfaces. The committed evidence is sanitized and contains no token or private raw values. The Store 03 drift scenario uses authored values on those observed field paths and is clearly labeled SYNTHETIC DEMO DATA; it is not presented as a live Ring mutation.

Challenges and lessons

The Playground made hardware-free discovery and device-detail validation fast. The biggest challenge was demonstrating repeatable state change: the tested Motion action did not appear in Event History, and no device status/configuration mutation preset was visible or documented. We kept the baseline and illustrative drift claims separate rather than overstating simulator behavior.

What's next

Deterministic simulator presets for online/offline, configuration toggles, and device add/remove events would unlock richer end-to-end testing. FleetPolicy can then extend its existing evidence and review model across larger multi-site fleets while preserving the same read-only safety boundary.

Built With

• amazon
• developer
• javascript
• partner
• ring
• vision