Platform architecture

Embedded control, secure connectivity, and operational intelligence.

The NovaFir platform is the shared technology underneath every product family. Local control and optimization on the device, approved connectivity into the data model, monitoring and analysis in NovaCloud, and advanced optimization in ASCEND.

Architecture informed by IEC 62443NIST SP 800-82In development
One platform · four layersLIVE
POWER
AND EDGE
NovaCore · NovaTrack
Device control and optimization, local and deterministic
CONNECT
NovaConnect · Atlas
Approved third-party and commercial site integration
UNDERSTAND
NovaCloud
Monitoring, analytics, forecasting, diagnostics
OPTIMIZE
ASCEND
Operational intelligence within approved constraints

Atlas is commercial and industrial hardware shown beside the platform layers, not a universal software layer.

Core technology

Six platform components, one shared architecture.

Product tiers and software layers are separate things. These are the technology components shared across Prime, Nexus, NexusPlus and commercial deployments.

01 · EMBEDDED

NovaCore

The embedded runtime inside NovaFir hardware.

  • ›Device services and communications
  • ›Deterministic and local control support
  • ›Diagnostics and secure execution
  • ›Update lifecycle management
02 · OPTIMIZATION

NovaTrack

Adaptive optimization and MPPT. Exact function depends on the product tier.

  • ›MPPT and harvest optimization
  • ›Forecast-assisted control
  • ›Related on-device algorithms
03 · CONNECTIVITY

NovaConnect

Third-party connectivity architecture for approved equipment.

  • ›Supported cloud-to-cloud connectors
  • ›NovaConnect Gateway for local equipment
  • ›Normalization into the NovaFir data model
04 · CLOUD

NovaCloud

Where normalized data becomes an operational view.

  • ›Monitoring, history and trends
  • ›Analytics, forecasting and reports
  • ›Fleet visibility and remote diagnostics
  • ›Update coordination
05 · OPERATIONS

ASCEND

Advanced operational intelligence built on trusted data.

  • ›Constraint-aware optimization
  • ›Scenario analysis and recommendations
  • ›Approved coordination logic
06 · APPLICATIONS

NovaFir Mobile

Provisioning and field workflows for installers and service teams.

  • ›Commissioning and provisioning
  • ›Monitoring and offline support
  • ›Service workflows
Hardware family

Atlas sits beside the platform

Atlas provides NovaFir’s commercial and industrial edge hardware for secure site integration, communications and field connectivity. It is a hardware family rather than a software layer, and it is not a universal plant controller.

View Atlas →

NovaCore and NovaTrack are platform technology inside NovaFir products rather than separately sold product families. Platform capabilities are in development, and feature availability will vary by product tier.

Connectivity

Three paths into the platform, depending on the equipment.

There is no single universal route. How an asset reaches NovaCloud depends on whether it is NovaFir-native, supported third-party equipment, or part of a commercial or industrial site.

Path 01

NovaFir-native equipment

DevicePrime · Nexus · NexusPlus
↓
TelemetryNovaCore native telemetry
↓
CloudNovaCloud

NovaFir-native products do not require NovaConnect.

Path 02

Third-party residential and prosumer

EquipmentSupported OEM equipment
↓
IngestionSupported cloud connector, or NovaConnect Gateway where local communications are needed
↓
CloudNovaConnect into NovaCloud

The Gateway is one ingestion path, not the only one. Support depends on OEM availability, region, model, firmware and terms.

Path 03

Commercial and industrial sites

SiteSCADA, meters, inverters, BESS, OEM systems, sensors
↓
IntegrationAtlas and approved integrations
↓
CloudNovaCloud Commercial
↓
OptionalASCEND optimization

NovaCloud remains useful without ASCEND.

The key distinction

NovaCloud explains the operation. ASCEND advises on it.

The two products are related but not interchangeable. NovaCloud is the monitoring and analysis platform. ASCEND is the advanced operational layer built on top of it.

NovaCloud asks

What happened? What is happening? What is likely to happen?

  • ›Current operating visibility and history
  • ›Trends, alerts and reports
  • ›Weather and production forecasting
  • ›Anomaly detection and expected versus actual
  • ›Integration and data-quality visibility
ASCEND asks

Given that information and the approved constraints, what should the operator consider doing next?

  • ›Loss attribution and root-cause decomposition
  • ›Constraint-aware optimization
  • ›Scenario and what-if analysis
  • ›Operating and maintenance recommendations
  • ›Bounded orchestration only where separately validated and authorized
Security and control boundary

Safety-critical control stays local.

Safety-critical and deterministic control remains with the appropriate NovaFir or OEM device. Existing protection relays, inverter safety, turbine controllers, hydro governors and battery management systems remain authoritative. Loss of cloud connectivity does not compromise local operation.

  • ✓Hardware-rooted device identity and mutual authentication
  • ✓Authenticated communications and signed software and firmware
  • ✓Segmentation, least privilege and auditable access
  • ✓Read-only default posture for approved third-party integrations
IEC 62443Design reference
NIST SP 800-82Design reference
SBOM and HBOMDisclosure
Signed updates and rollbackDesigned to

Design and alignment references, not achieved certification claims. Product and market-specific certification pathways are planned.

Bounded intelligence

The platform advises, it does not own safety.

NovaCloud and ASCEND use forecasting, anomaly detection and optimization models to explain what happened and to propose what to consider next. They do not hold autonomous authority over safety-affecting or material decisions, and they do not write setpoints into third-party equipment.

NovaCloudMonitoring, history, forecasting and anomaly detection
ASCENDOptimization, scenario analysis and operating recommendations
HumanSafety-affecting and material operating decisions
LocalProtection logic, deterministic and on-device
OEMCertified machine-control systems remain authoritative
Connect layer

Two integration products for two different situations.

NovaConnect and Atlas are not the same product and the NovaConnect Gateway is not an Atlas SKU. Which one applies depends on site complexity, not on brand preference.

NovaConnect and NovaConnect Gateway

Supported third-party connectivity

Brings approved third-party equipment into the NovaFir data model, through supported cloud connectors or a physical gateway where local communications are required.

EnvironmentResidential, prosumer and lighter field integration
CloudCloud-to-cloud where OEM APIs and terms permit
GatewayEthernet, serial and RS-485, Modbus where supported, CAN where justified
PostureRead-only by default, no remote OEM parameter changes
Atlas

Commercial and industrial edge hardware

Connects approved commercial site equipment, normalizes field data, bridges industrial interfaces and supports resilient site-to-platform communications.

EnvironmentCommercial, institutional and industrial OT environments
OTSegmentation as a core design consideration
InterfacesDesigned to support Ethernet, serial and RS-485, CAN, Modbus, OPC UA, MQTT, historian integration and vendor APIs where justified
CoexistenceHistorian and SCADA coexistence, local buffering, offline resilience

Interface categories are design and support targets. Not every driver or OEM integration exists today.

Serviceability

Designed for long-cycle serviceability and support.

The commitment is not that every component lasts untouched. It is that the platform is designed to remain serviceable, updatable and supportable across a long operating horizon.

Field-serviceable

Designed around serviceable assemblies and replacement-part availability.

Update paths and crypto-agility

Signed update paths with rollback, and crypto-agility designed in from the start.

Lifecycle-aware components

Component selection and support planned around lifecycle availability.

Standards posture

OT architecture informed by IEC 62443 and NIST SP 800-82, including segmentation, least privilege, authenticated communications, device identity, signed updates and auditable access. Product and market-specific certification pathways are planned.

Get the brief

Build on the platform.

Send us your single-line and a few details. We’ll come back with an architecture sketch and an integration plan.