CurNext
Back to blog

CurNext · Product

CurNext platform roadmap: smarter alerts, richer twins, faster installs

By Content Marketer11 min read

Where CurNext is heading in 2025: fleet-aware alerting, deeper BIM-linked twins, faster CN-CC onboarding, and tighter QA exports for curing operations.

Analytics dashboard on a laptop representing product roadmap planning

Built for curing operations, improved with pilots

CurNext is a vertical platform for concrete curing intelligence: CN-CC hardware, LoRaWAN connectivity, project RBAC, BIM surfaces, maturity and readiness workflows, alerts, and compliance-ready records. The 2025 roadmap doubles down on what pilots taught us - less noise, richer context, faster time to first trusted sample.

Smarter alerts

Alert noise kills field trust. Roadmap work focuses on:

  • Zone ownership and quiet hours so the right person acts once.
  • Severity that matches operational urgency (stall vs informational drift).
  • Fleet health signals (last-seen, battery, gateway coverage) separated from curing maturity alerts.

Supers should open CurNext because it helps, not because it cries wolf.

Richer twins

Surface-level readiness continues to deepen:

  • Stronger material and pour metadata on surfaces.
  • Inspection and compliance hooks beside live telemetry.
  • Exportable packs that match owner QA numbering.
  • Clearer multi-building navigation for sites like the Helsinki pilot pattern.

The twin stays useful only if geometry and physics stay linked. That remains a product principle.

Faster installs

Time from crate to first valid sample is a competitive metric for CurNext field teams:

  • Device config templates and batch commissioning flows.
  • Clearer RF diagnostics during gateway staging.
  • Mobile-first association of devices to surfaces.
  • Training paths inside the platform for installers and content/ops roles.

Every minute saved before the truck arrives is a minute of better coverage.

Platform foundations underneath the curing UX

Behind the dashboard, CurNext continues to invest in the shared stack pilots already rely on: authenticated web and API access, project-scoped data, MQTT ingestion paths for telemetry, and operational tooling for devices and BIM. Roadmap items that unblock critical-path field work rise first.

How partners shape the backlog

Pilot GCs and owners see friction first. Share it with your CurNext contact: alert noise, install steps that slip under pour pressure, export gaps for auditors. The curing workflow is the product - roadmap priority follows the pour.

What stays constant

  • Evidence over calendar superstition for critical pours.
  • Surfaces over orphan device lists.
  • Calibration and identity as part of every serious reading.
  • Hyphen-clean documentation in the product voice you read here.

CurNext exists to make concrete time visible, actionable, and defensible. That mission drives 2025.

0 comment

Sign in to interact

Like, comment, and reply require a CurNext account. Sign in on dash.curnext.app, then return to this post.

Open dashboard