Products
Seven products. One platform.
Each MachBeat product is a separable revenue line that shares one identity, tenancy and data model — so you can buy Edge and monitoring without seats, or API access on its own, and add the rest as you grow. Status below is honest: what runs today, what’s partial, and what’s planned.
MachBeat Edge
The ESP32-based vibration node running today, evolving into an industrial multi-sensor gateway (RS485/CAN/PoE, DIN-rail, secure boot). It captures condition on the machine and does on-device signal processing and buffering, so nothing depends on your existing infrastructure.
MachBeat Cloud
Device registry, MQTT broker, ingestion, digital-twin state, a time-series store and the API gateway. The core runs today for a single site; the streaming and time-series scale layer that takes it from hundreds to millions of devices is being built.
MachBeat AI
The signal + ML predictive engine: heuristic diagnostics and classical DSP (FFT, bearing fault frequencies) run today, producing health, RUL, root cause and cost. Unsupervised and deep-learning tiers plug in behind the same contract as your data deepens.
MachBeat Vision
The live digital twin of each machine, line and factory. The 2D twin is built into the platform today; an immersive 3D twin is on the roadmap.
MachBeat Insight
Reliability and executive dashboards, KPIs and reports — the mission-control view that is built and running today. This is where a maintenance manager reads fleet health at a glance.
MachBeat Mobile
The engineer’s app: push alerts, a read-only machine twin, maintenance checklists, QR-scan device provisioning, and photo/voice capture on a work order — offline-first for plant-floor dead zones. Ships after web tenancy and notifications are solid.
MachBeat API
The developer platform: tokens, webhooks, and CMMS/ERP connectors (SAP, Maximo). The REST API with Swagger docs is built today; webhooks and connectors are being added.
Design principle
Separable revenue lines, one system.
Because every product shares one tenancy and data model, a customer can land with Edge + managed monitoring, then expand into premium AI, more seats, or API licensing without a migration. That is also the retention lever — switching cost grows with the history and trained models a customer accumulates.
Not sure which module to start with?
Most teams start with Edge and monitoring on one critical asset, then expand. Tell us the machine and we’ll recommend the smallest useful footprint.