Architecture overview

Nodectra separates engineering, cloud coordination and site-local execution.

Nodectra Cloud
  ├─ organizations, users, projects and revisions
  ├─ Development Studio web application
  ├─ agent and MCP proposal review
  └─ deployment control plane
                │ signed versioned bundle
                ▼
Nodectra Site Runtime on a Site Server
  ├─ protocols and physical Points
  ├─ programs, schedules and alarms
  ├─ historian and operational audit
  └─ Web Station / Client View
                │ site LAN
                ▼
Edge Controllers, Field Controllers and field devices

Design principles

• Site autonomy: active control continues locally without a cloud round trip.
• One project model: Studio, bundle validation and Runtime use a shared project contract.
• Typed bindings: signals connect through declared ports, engineering types and units.
• Explicit deployment: editing a cloud project does not silently change a running building.
• Human approval: agents and MCP create reviewable proposals; they do not apply or deploy changes.
• Separated interfaces: engineering tools, Runtime management and operator applications have different capabilities.

Product family