Control plane
Central authority for APIs, operator UI, governance, trust, scheduling, messaging, and system-wide decisions.
Hexe is a modular, local-first control plane made tangible through custom voice endpoints—from governance and runtime control to wake word, screen, speaker, and response.
Hexe brings home, edge, and trusted external execution under one structure. Core holds authority and policy; Supervisor owns host-local runtime control; Nodes declare capabilities and execute across explicit trust boundaries.
Voice is where that architecture becomes physical. Microphones, displays, transport, speech services, and interaction logic work as one inspectable stack—without treating the room as a cloud peripheral.
It is an active open-source engineering project: working software and physical devices first, with the edges documented honestly.
Central authority for APIs, operator UI, governance, trust, scheduling, messaging, and system-wide decisions.
Local authority for system health, resource visibility, lifecycle control, and workload management.
Trusted systems declare capabilities, receive governance, publish telemetry, and execute beyond Core.
Inside the wider Core → Supervisor → Nodes platform, a real-time WebSocket path carries commands and PCM audio between room endpoints and HexeVoice. HexeInteraction turns recognized speech and shared events into useful behavior.
Wake word · microphones · speakers · touch displays
Streaming · STT · TTS · speaker identity · device control
Context · automations · task routing · response behavior
Endpoints detect a wake phrase, then move command and PCM traffic over a persistent WebSocket architecture.
STT and TTS are part of the same system path, with local options and ready-state audio handling.
Hexe can associate voices with enrolled speakers while keeping identity handling grounded in the local system.
Calibration and room-aware signal behavior help endpoints understand the acoustic space around them.
Room devices register independently, report state, and receive targeted screens, audio, and commands.
Firmware and interface assets can move through managed update paths without dismantling an endpoint.
Hexe runs across custom endpoint builds, from compact ESP32-S3 voice devices to a Waveshare ESP32-P4 touch display with a full visual surface. Firmware, audio, UI assets, provisioning, and OTA all meet at the edge.
The real-time layer between microphones, speakers, displays, and speech services. It owns endpoint connections, audio transport, voice processing, and device-facing presentation.
The context and coordination layer. It turns recognized speech, timers, weather state, and shared events into responses that make sense for a person, room, and endpoint.
Roadmap items are direction, not shipped capability. Hexe grows by proving each layer on real devices before calling it done.
Continue refining calibration, noise context, and endpoint-specific behavior.
More backend-owned screens and event-driven UI across capable displays.
Synchronized playback and room-aware media are a destination—not a current feature.
Hexe is developed in public across the Core, Voice, and Email repositories. Hexe Email can connect to Gmail—with the user’s permission—to fetch, display, classify, summarize, label, and send email under user or operator control. The code is the clearest view of what exists today; the docs preserve the platform-level architecture and operating contracts.