Home / Resources

Resources

Building in the open.

MachBeat is under active development, and we’d rather be honest about it. Here is the roadmap, the real build status of every layer, and answers to the questions engineers actually ask.

Roadmap

From working pilot to enterprise platform.

The plan is sequenced so early revenue funds the next layer — and so we don’t build scale features before there are customers who need them.

Phase 0 · Now

Pilot-ready (lab)

Device online path, JWT auth, RBAC, health checks. HTTPS at the web edge when deployed. MQTT TLS, per-device broker auth, and reliable email alerts are still in progress.

→ Unlocks: private pilot
Phase 1 · 1–2 quarters

Design partners

Durable streaming buffer, time-series store and windowed AI to break the per-packet ceiling; deeper hierarchy and roles; reports & export; envelope + cepstrum DSP. Same phase: selectable detection methods, a certified healthy baseline, RPM operating-state ranges, and an alert policy that requires agreement instead of one averaged score.

→ Unlocks: 3–5 factories, real case studies
Phase 2 · 2–3 quarters

Multi-tenant SaaS

SSO / SCIM, billing + per-asset metering, mobile app v1, observability & DR, and the first unsupervised-ML anomaly tier.

→ Unlocks: self-serve mid-market
Phase 3 · 3–4 quarters

Scale

Autoscale to 100k+ devices, the 3D Vision twin, CMMS/ERP connectors, and white-label.

→ Unlocks: enterprise pilots
Phase 4 · 4–6 quarters

Enterprise & compliance

SOC 2 Type II + ISO 27001, deep predictive models with MLOps, multi-cloud, and an OEM channel.

→ Unlocks: Fortune-500 contracts

Honest build status

What runs today, what’s partial, what’s next.

The same matrix the founding team works from. No layer is claimed as finished before it is.

LayerBuiltPartialNot started
EdgeVibration node, DSP, buffering, OTA hook, provisioningIndustrial gateway, cert identity, multi-sensorSecure-boot hardware, enclosure
CloudMQTT ingest, device registry, database, REST + Swagger, WebSocket, RBAC, auditTenancy depth, TLSStreaming buffer, time-series, autoscale, connectors
AnalyticsRule-based health indicators, FFT features when supported, and explainable evidenceBroader frequency methods and operating-condition baselinesTrained ML forecasts and RUL
DetectionMethod picker, alert policy, class or OEM limits, certified baseline approval, RPM-state rangesEnvelope and gear mesh; load-only when current or pressure existsAcoustic emission, magnetic flux, fleet-trained models
SaaSMulti-tenant core, roles, billing tiersHierarchy depth, full role setSSO/SCIM, billing engine, white-label
AppsMission-control web, 2D digital twin, explainable AIReports / exportMobile, 3D twin
SecurityArgon2, JWT + refresh, RBAC, audit, rate-limitTLS, device certsSOC 2 / ISO, signed OTA
OpsDocker, CI, composeHealth checksKubernetes, observability, DR, backups

Engineering extension · under assessment

Lubricant monitoring is a multi-signal problem.

Oil condition depends on lubricant type, temperature, load, contamination and machine context. MachBeat is evaluating an integration-led approach using established fluid sensors; this is not a capability of the current vibration-only V1 device.

01

Delivery signals

Level, pressure, flow, pump cycles and filter differential pressure can help investigate leaks, restrictions, pump issues or insufficient lubricant supply.

02

Oil-condition signals

Selected sensors can trend viscosity/temperature, water saturation or particle cleanliness. Density alone does not diagnose oil health; many chemistry and wear questions still require a lab.

03

Validation before alerts

Machinery-specific sampling points, fluid compatibility, oil-grade reference values and lab comparison are needed before thresholds can support a maintenance decision.

No guaranteed remaining-oil-life estimate or failure prediction is claimed. A human reviews evidence before work is planned.

FAQ

Questions engineers actually ask.

What machines can MachBeat monitor?
Rotating industrial assets — motors, pumps, compressors, fans and gearboxes — are the primary focus. Fit for a specific machine is confirmed during the pilot.
What does the reference device measure today?
The current ESP32 + ADXL345 reference node measures vibration on three axes. It does not measure temperature, RPM, oil properties or lubricant delivery. Optional telemetry fields and future multi-sensor gateway work do not mean those channels are present on the current node.
Do I need existing sensor history for the AI to work?
No. The L0 heuristic and L1 DSP tiers work cold-start, with no failure history. The unsupervised and supervised tiers deepen the diagnosis as your machines accumulate data.
How does data reach the platform?
The edge node streams over MQTT into the MachBeat backend. Transport TLS and per-device certificates are being rolled in; a local-network path is used for lab and early pilots.
How are alerts generated?
The design uses four methods — engineering limits, a healthy baseline, an operating-condition baseline, and frequency patterns — and raises a warning when the chosen policy says they agree. A critical engineering limit can alarm on its own. Today the engine still produces one health score from limits, a recent statistical baseline, and frequency features. Early indications are investigative cues, not guaranteed failure predictions. Status is on the platform page.
Can we choose which detection methods run?
Yes. On the machine you select any combination and an alert policy. Frequency analysis stays off until the sample rate, waveform length, and speed are enough. Acoustic emission and magnetic flux stay unavailable on the current sensor.
How do you know the captured data is healthy?
Vibration alone cannot prove it. A certified baseline needs a person to confirm the machine was inspected, a quality score from stable samples across operating states, and an explicit approval. “Not sure” stays a reference baseline. The steps are on the machine page and described on Solutions.
What happens to the baseline after maintenance?
Completing maintenance keeps the previous baseline and asks whether to keep it, start a new one, blend new data, or compare before and after. The old baseline is archived.
Is it secure enough for enterprise?
The app has role-based access, JWT auth and a full audit log today. TLS and device certificates are in progress, and a mapped path to SOC 2 Type II and ISO 27001 is on the roadmap before the first large-enterprise deployment.
Can it integrate with our CMMS/ERP?
A REST API with Swagger docs is available today. Webhooks and CMMS/ERP connectors (e.g. SAP, Maximo) are being added — integration scope is discussed during the pilot.
How long does a pilot take?
It depends on the site and asset. During the pilot we mount, connect, collect a baseline window, and review signals with your team.

Want the technical deep-dive?

We’re happy to walk an engineering team through the architecture, the AI ladder, and exactly what runs today.