HN Showcase
Back to browse

An API that resolves conflicting IoT device state in 47ms

by TylerArrows·Mar 3, 2026·2 points·3 comments
Visit ProjectView on HN

AI Analysis

●●●BangerBig BrainSolve My Problem

Multi-signal arbitration engine solves out-of-order IoT state with 47ms latency and confidence scoring.

Strengths
  • •Weighs signal strength, sequence continuity, and timestamp plausibility simultaneously, not naive timestamp checks
  • •Returns arbitration trace explaining reasoning, enabling debugging and confidence calibration
  • •47ms latency claim is concrete; demo endpoint accessible without signup, verifiable
Weaknesses
  • •SaaS dependency: 47ms resolves if the API is geographically close, adds vendor lock-in
  • •Business model unclear: pricing, uptime SLA, and data retention policies not disclosed
Target Audience

IoT platforms and edge systems managing devices with unreliable network conditions and clock drift

Similar To

Temporal.io · AWS IoT Core state management

Post Description

I built this after watching the same bug surface in three different IoT projects: a device sends "offline" then "online" 200ms later, they arrive out of order, and your system marks a live device dead.

The naive fix is a timestamp check. But timestamps lie — clock drift, late-arriving packets, firmware bugs. So I built a multi-signal arbitration engine that weighs event arrival time, signal strength, sequence continuity, and timestamp plausibility together before committing to a resolved state.

You POST your raw device payload to /v1/sign, then /v1/resolve. You get back a single authoritative state, a confidence score (0.50–1.0), a recommended_action enum (ACT / CONFIRM / LOG_ONLY), and a full arbitration trace showing exactly why it resolved the way it did.

The demo works right now with no signup — just grab the demo key from the landing page and fire a request. Happy to answer any questions about the arbitration logic.

Similar Projects

Infrastructure●●Solid

Fostrom, an IoT Cloud Platform built for developers

They combined typed payload validation, per-device sequential mailboxes and JS Actions running inside a WASM sandbox — a practical feature set that actually improves predictability for fleet code. The tiny Rust agent plus Python/JS/Elixir SDKs and an Elixir+DuckDB backend signal thoughtful infra choices rather than vaporware. Nice UX on the landing page, but the space is crowded; integrations and real-world scale will determine whether this stands out.

WizardryNiche Gem
arjunbajaj
304mo ago