CurNext

Documentation

Docs

Long-form product documentation for CurNext - site path, solutions, API, SDKs, firmware, integrations, security, hosting, and commercial scope. Built from public material on curnext.app.

Overview

What CurNext is, how Docs is organized, and where to go next.

What is CurNext?

CurNext provides build-ready site intelligence for construction surfaces and spaces. Field nodes measure conditions on the work itself. The platform answers whether work can proceed - with readiness, alerts, and an audit trail mapped to your project.

The product is sold as construction intelligence, not a radio bill of materials. Site and office teams act on go / no-go decisions. Developers and operators extend the same stack through the REST API, SDKs, Market Place integrations, and firmware operations.

This Docs surface summarizes public product material already published on curnext.app. It is meant to be readable end to end. Detailed hardware security runbooks, factory fixtures, and private ops procedures stay in internal documentation.

Who it is for

CurNext is built for contractors, project teams, BIM coordinators, facilities roles after handover, and integrators who need readiness decisions in tools they already run.

  • Site teams acting on go / no-go readiness on slabs, walls, air, leaks, structure, and plant
  • Office teams tracking surfaces against schedule and handover evidence
  • Developers calling the REST API or official SDKs
  • Operators reviewing firmware catalog, reported versions, and edge OTA context
  • Procurement and security reviewers reading Security, Datacenters, and DPA pages

Operating markets

CurNext currently sells into Finland, Canada, and Cameroon. Pricing is native list pricing per market (EUR, CAD, XAF) - not a single FX conversion table.

Platform Client Data for those markets is hosted on the EU-anchored production stack (application origins in Germany, database and auth in Frankfurt) unless a written enterprise residency addendum says otherwise. Selling into Canada or Cameroon is not the same as hosting a local production region there.

How this documentation is organized

Use the tabs across the top to move between topics. On large screens, the left rail lists section headers for the active tab and highlights the section in view as you scroll.

  • Overview - product framing and navigation
  • Site path - L1 through L5 and connectivity
  • Solutions - each factory-fixed SKU in depth
  • API - base URL, auth, domains, webhooks
  • SDKs - languages, install, patterns
  • Firmware - catalog, history, edge OTA
  • Integrations - Market Place catalog
  • Security - public architecture summary
  • Hosting - residency and scale posture
  • Commercial - pricing model and contact paths