Technologies

The CurNext stack from field nodes to cloud - industrial connectivity, BIM-mapped readiness, and APIs your teams can call.

This page covers public platform capabilities. Detailed hardware security procedures stay in private operations documentation.

Connectivity

Standard industrial protocols - named at the capability level, not as an attack surface guide.

LoRaWAN
EU868 field uplinks for battery nodes - long-range, site-friendly radio into the CurNext floor path.
MQTT over TLS
Device and gateway telemetry into the platform over encrypted MQTT for the hardware path.
WireGuard
Secure tunnel themes for building edge connectivity into CurNext cloud services.
HTTPS REST
Versioned buyer integrations at api.curnext.app - readiness, BIM, devices, alerts, webhooks.

SKUs you already see across Solutions - same stack, different site jobs.

CurNext turns site measurements into build-ready decisions mapped to your project.

Surface readiness
Scores, status, and estimated ready timing for monitored surfaces.
Concrete curing model
In-house prediction for CN-CC slab readiness, trained and served with TensorFlow.js.
BIM context
Buildings, spaces, and devices for coordination - not a detached sensor dump.
Alerts & events
Operational alerts and webhook events into the tools your teams already run.
Weather context
Outdoor context where it helps curing and drying decisions on site.

Cloud product and developer entry points your teams already use.

Themes we can state publicly. Implementation detail stays in private security documentation.

Encrypted transport
TLS for cloud APIs and MQTT paths; WireGuard for edge tunnel themes.
Signed field updates
OTA is staged at the edge on CN-BC with checksum-addressed images - not a public browser flasher.
Device identity
Hardware identity and verification themes for field units; factory and field install procedures are ops-controlled.
Audit trail
Project activity and readiness decisions leave a clear trail for handover and compliance conversations.