Loading VibeLux...
Loading VibeLux...
Coming soon
A real fleet-management surface needs hardware partners, device firmware, signed OTA artifacts, and a certificate authority — work that is queued behind the design and handoff workflows that are live today. We are holding this page until those pieces are real instead of shipping a preview that pretends to control fixtures it can't reach.
The phases below will become live surfaces as each one lands. Until then the page intentionally has no fixture inventory, gateway pairing, or OTA controls.
Phase 1 — Cloud foundation. Database-backed fixture & gateway inventory, firmware catalog, deployment scheduler. Ships before any device communication is wired so the data model is settled.
Phase 2 — Device discovery. Gateway protocol (mDNS / BLE / MQTT-over-TLS), pairing flow, signed device certificates. Requires at least one fixture-OEM partner running our firmware or client SDK.
Phase 3 — OTA delivery. Signed firmware artifacts, delta-only updates, A/B partition swap with watchdog rollback, per-device progress reporting and audit log.
Phase 4 — Production hardening. Mutual TLS, certificate rotation, RBAC, multi-tenant isolation, regulatory compliance, on-call coverage.
The closest things shipping today.