
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.
Pilot-ready
End-to-end device-online, TLS on transport, idempotent ingest, health checks and email alerts.
→ Unlocks: first paid pilotDesign 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.
→ Unlocks: 3–5 factories, real case studiesMulti-tenant SaaS
SSO / SCIM, billing + per-asset metering, mobile app v1, observability & DR, and the first unsupervised-ML anomaly tier.
→ Unlocks: self-serve mid-marketScale
Autoscale to 100k+ devices, the 3D Vision twin, CMMS/ERP connectors, and white-label.
→ Unlocks: enterprise pilotsEnterprise & compliance
SOC 2 Type II + ISO 27001, deep predictive models with MLOps, multi-cloud, and an OEM channel.
→ Unlocks: Fortune-500 contractsHonest 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.
| Layer | Built | Partial | Not started |
|---|---|---|---|
| Edge | Vibration node, DSP, buffering, OTA hook, provisioning | Industrial gateway, cert identity, multi-sensor | Secure-boot hardware, enclosure |
| Cloud | MQTT ingest, device registry, database, REST + Swagger, WebSocket, RBAC, audit | Tenancy depth, TLS | Streaming buffer, time-series, autoscale, connectors |
| AI | L0 heuristics, FFT, bearing, health, RUL, cost, explainable evidence | Envelope / cepstrum | L2/L3 ML, MLOps, retraining |
| SaaS | Multi-tenant core, roles, billing tiers | Hierarchy depth, full role set | SSO/SCIM, billing engine, white-label |
| Apps | Mission-control web, 2D digital twin, explainable AI | Reports / export | Mobile, 3D twin |
| Security | Argon2, JWT + refresh, RBAC, audit, rate-limit | TLS, device certs | SOC 2 / ISO, signed OTA |
| Ops | Docker, CI, compose | Health checks | Kubernetes, observability, DR, backups |
FAQ
Questions engineers actually ask.
What machines can MachBeat monitor?
What does the sensor measure today?
Do I need existing sensor history for the AI to work?
How does data reach the platform?
How are alerts generated?
Is it secure enough for enterprise?
Can it integrate with our CMMS/ERP?
How long does a pilot take?
Want the technical deep-dive?
We’re happy to walk an engineering team through the architecture, the AI ladder, and exactly what runs today.