WB-1 · v1.0 now shipping

Orchestrate the air.

Devices don’t speak the same language. The Bobulator translates — in real time.

The Wireless Bobulator is a modular device that aggregates signals from any source, processes them through a real-time orchestration engine, and broadcasts coordinated output across your facility, gym, factory, or venue.

FIG. 1 · WB-1 · v1.0 · aluminium machined puck · 3 radios concurrent
scroll

A control plane for the wireless layer.

Most devices either receive or transmit. The Bobulator does both — simultaneously, intelligently, and with sub-millisecond timing.

12 CHANNELS · 0.1% FS ACCURACY

Capture any signal

Twelve input channels spanning analog, digital, BLE, Wi-Fi, and serial. Pluggable sensors for motion, environmental, RF, and more.

8.0ms ± 0.4ms · 1kHz TICK

Process in real time

Dual-core SoC runs the Bobulation Engine — a fusion + decisioning layer that resolves conflicts, prioritizes, and routes signals.

3 RADIOS · 200m LINE-OF-SIGHT

Broadcast everywhere

BLE 5.3, Wi-Fi 6, and LoRa in one box. One device, three radios, simultaneous transmission to hundreds of endpoints.

REST + WS · 64KB RULE DSL

Open API, no lock-in

REST + WebSocket control plane. Define rules in YAML, push them to the fleet, observe everything in a live dashboard.

01Architecture

Five layers. One orchestrated device.

From sensor input to wireless broadcast, every signal passes through a deterministic pipeline tuned for low latency and high reliability.

01INPUTS12 channels02NORMALIZEunified wire03ENGINE<8ms decide04TRANSMIT3 radios05OUTPUTSactuate / API
01 / 05

Twelve mixed-signal channels enter one timestamped frame.

frame.raw[12]

Dive into the architecture →

The hardware is honest. The software is where the magic happens.

02The Bobulation Engine

The brain inside the box.

Hardware is commoditized. Software is not. The Bobulation Engine is the layer that decides what to amplify, dampen, route, ignore, and actuate — in under 8 milliseconds.

  • Multi-input fusion — combine up to 12 channels with weighted confidence
  • Real-time decisioning — rule engine + optional on-device ML
  • Conflict resolution — deterministic priority + freshness scoring
  • Context-aware routing — route by device, location, time-of-day, user identity
Inside the engine →
rules/gym-entrance.bob
# soft-open the floor on the early shiftrule "gym-entrance-soft-open":  when:    - sensor.door.reed == CLOSED    - time_of_day() in "06:00-09:00"  then:    - light.zone.2.fade_to(30%, over=5s)    - audio.zone.2.play("morning-warmup.m3u")    - hvac.zone.2.setpoint = 68    - log.info("auto-warmup-triggered", room="main-floor")

·The Hardware

Dissect the puck.

Eight systems share one machined shell. Isolate a callout to see what each component owns, then follow the full hardware path into the WB-1 technology brief.

  • Triple-radio · BLE 5.3 / Wi-Fi 6 / LoRa
  • USB-C power + console · PoE optional
  • Aluminium shell · 86 mm × 24 mm

Explore WB-1 hardware →

Select a system to isolate its leader line.

03Wireless Topologies

Pick the topology that fits the room.

Hub Model

One Bobulator. Many devices.

  • Best for single-floor or single-room installations
  • Centralized rules + audit trail
  • Easiest to deploy and manage

Edge + Cloud Hybrid

Local first. Cloud for the heavy lifting.

  • Local latency for real-time decisions
  • Cloud coordination for fleet-wide analytics and ML
  • Works fully offline — syncs when reconnected

See topology diagrams →

05Design-partner evidence

Measured in rooms that fight back.

Read all case studies →

“Before the Bobulator, every tournament started with someone walking the courts and chasing clocks. Now one reviewed rule leaves every court together.”

Maya Chen · Director of Operations · Riverside Athletic Center 14 courts · 9 nodes · 72 active channels View measured result →

“The useful change was not another dashboard. It was proving why the line stopped, in order, while the evidence was still warm.”

Luis Ortega · Controls Engineering Lead · Hartwell Controls 6 cells · 8 nodes · 84 active channels View measured result →

“We stopped treating every room flip like a new integration. The state follows the wall plan, and the show keeps its cues when the uplink does not.”

Nia Brooks · Technical Operations Manager · Meridian Event Hall 3 halls · 12 nodes · 108 active channels View measured result →

·ATLANTA GA · 33.75°N

Built in Atlanta.

The WB-1 is engineered, assembled, and shipped from Atlanta, Georgia. Boards are populated locally, then flashed, calibrated, and functionally tested in-house before any unit gets a serial number.

We’re hiring — tell us what you’d build →

05Specs

Numbers that matter.

Inputs
12 channels (analog, digital, I²C, SPI, UART)
Radios
BLE 5.3, Wi-Fi 6 (2.4/5 GHz), LoRa (868/915 MHz)
Compute
Dual-core SoC (Cortex-M7 + ESP32)
Latency
< 8 ms sensor-to-broadcast
Power
USB-C PD or 18650 battery pack, 12 h standby
Management
REST + WebSocket, YAML rule engine, web dashboard

Full specifications →

06v1.0 · 2026-11 · REV 1.0

What’s new in v1.0.

The first production release. Four things that weren’t in the prototype and changed what the box can do.

  1. 01

    Three radios, concurrent

    BLE 5.3, Wi-Fi 6, and LoRa transmit at once on independent antennas with >20 dB isolation — no time-sharing.

  2. 02

    Dual-SoC architecture

    A Cortex-M7 owns the deterministic path; an ESP32 owns the radios and web stack. A slow request can’t stall a deadline.

  3. 03

    Mesh fallback

    A degraded radio escalates its traffic to mesh neighbours, so a single RF failure downgrades range instead of dropping the link.

  4. 04

    64 KB rule DSL

    A declarative YAML engine that compiles to a static graph and still ticks in single-digit milliseconds. Hot-reload, fleet push.

Read how it’s built →

Build something that orchestrates.

Join the first 50 teams piloting the Wireless Bobulator. We’re shipping units now and onboarding customers personally.

If you’re not bobulating, what’s the point?

copied!