What is new in version 3.2.0 🚀?
This is an overview of the features and changes added in Nerve 3.2. For an extensive list of all changes, refer to the release notes.
Nerve 3.2 is a major usability release. The focus of this version is a refreshed user experience across the Management System and Local UI, with a cleaner interface, more consistent navigation, improved icons, and a redesigned node list that makes managing large device fleets easier and more intuitive.
The most visible change is the new UI experience. Nodes are now managed in one consolidated node view, with node groups defined by labels instead of the previous folder structure. Users can drag and drop nodes into these groups, and the related label assignment is updated automatically. This makes node organization more flexible, more transparent, and easier to maintain.
Below are the highlights.
✨ A New UI Experience for Everyday Work
Nerve 3.2 introduces a refreshed UI and UX foundation across the Management System and Local UI.
The new design improves visual consistency, reduces friction in daily workflows, and makes common actions easier to understand. Icons have been updated to be more visible, more distinct, and more consistent across the product. Dialogs, forms, menu behavior, and action wording have also been aligned to provide a more predictable user experience.
New node list with label-based grouping
The node list has been cleaned up into one central view. Instead of managing nodes through a folder structure, node groups are now defined by labels. Nodes can be moved between groups by drag and drop, and the label assignment changes automatically.
This gives users a more flexible way to organize fleets, especially when nodes need to be grouped by customer, site, machine, project, version, or operational status.
Key benefits
- Faster navigation and easier orientation in large node fleets
- More flexible grouping through labels
- Less maintenance compared with folder-based structures
- Automatic label assignment when nodes are moved by drag and drop
- A clearer and more modern node management experience
More consistent icons, dialogs, workflow and navigation
Nerve 3.2 improves the consistency of the interface. Icons are now easier to distinguish and follow the same visual language. Dialog titles, button names, and form actions are aligned more consistently, so users do not have to interpret different wording for similar actions.
The main menu behavior in the Management System has also been updated to provide a more consistent navigation pattern. When entering the workload name, pressing Enter continues directly to adding the first version instead of creating an empty workload and returning to the workload list.
Key benefits
- Easier recognition of actions through clearer icons
- More consistent wording across dialogs and forms
- Reduced risk of user confusion
- More predictable navigation between Management System and Local UI workflows
- Users can follow the natural workload creation flow with fewer mistakes and fewer unnecessary clicks.
🧭 Cleaner Deployment and Administration Workflows
The Dry run capability has been removed. The Retry action for deployment campaigns has also been removed.
Key benefits
- Cleaner administration experience
🧬 DNA Improvements: More Automation, More Traceability
Nerve 3.2 continues to expand DNA-based configuration and visibility.
User-defined metadata in DNA
Workload DNA and Node DNA files can now include user-provided metadata. This metadata is also available through GET DNA status. In addition, Nerve creates a read-only node details label from the metadata.
This makes it easier to understand which version, customer state, project setup, or other customer-defined information was used to configure a node or workload.
Key benefits
- Better traceability of deployed configurations
- Easier grouping and filtering through generated labels
- More transparency when checking DNA status
- No impact on the DNA process itself
Node DNA UI in the Management System
Node DNA status information is now available in the Management System. Users can get and set relevant Node DNA information.
Key benefit
Administrators can manage and verify node configuration more centrally from the Management System.
NTP configuration through DNA
NTP server configuration can now be included in DNA. This is especially useful when devices are preinstalled and the final NTP server address is only known later.
Nerve also provides feedback when synchronization succeeds or is lost, for example through syslog or audit logs.
Key benefits
- Configure time synchronization during runtime
- Reduce manual post-installation steps
- Improve visibility into synchronization status
Logging configuration through DNA
Logging behavior can now be configured through DNA and API-based workflows. This includes system logs, system monitoring, Docker workload monitoring, Docker workload logging, and log levels for selected components.
Key benefits
- Configure logging without manual UI interaction
- Support repeatable node setup
- Make logging configuration part of automated deployment processes
Included change: NERVESW-10629. 【1-0a3b5d】
Custom compose restrictions
Customers can now manage compose restrictions without manually connecting to the node through SSH after each update. A mechanism is provided to supply a customized restrictions file, including API-based automation through Management System API, Local API, and nerve-cli support.
Key benefits
- Preserve customer-specific compose restrictions more easily
- Enable automation instead of manual SSH changes
- Reduce effort after node updates
⚙️ Better APIs and Automation for Customer Workflows
Nerve 3.2 improves automation capabilities for customers, DevOps teams, and external systems.
Access tokens for automated API access
Users can create named access tokens for API usage. Tokens follow the same RBAC permissions as the user, are shown only at creation, can be deleted, and are visible in logs by token name.
This enables automated scripts to use Management System APIs in environments where MFA is required, without relying on manual authentication steps.
Key benefits
- Better support for automation and CI/CD workflows
- MFA-compatible API usage for scripts
- Clear traceability of token-based API activity
- RBAC stays aligned with user permissions
OAuth authentication flow for Docker registry access
The Management System registry now supports the OAuth token authentication flow required by newer Docker behavior. This enables users to continue using standard Docker commands such as docker login and docker push.
Key benefits
- Compatibility with newer Docker versions
- Standard Docker workflows continue to work
- Easier image publishing to the Management System registry
Local UI APIs for system metrics
New Local UI API endpoints provide access to system metrics already monitored by Nerve. This includes disk capacity and usage, CPU usage, RAM usage and availability, CPU temperature, and network information such as physical interface IP addresses and link state.
This is especially useful for customer applications that need to include Nerve node health information in their own monitoring portals without giving end users access to the Management System.
Key benefits
- Easier integration with customer monitoring solutions
- More transparency about node health
- Support for asset-level dashboards and alerting
- Less need for custom data collection inside workloads
RCM download from the Management System
The Remote Connection Manager can now be made available directly from the Management System. Users can access the correct version more easily without requiring an additional login to the Nerve Software Center.
Key benefits
- Better version alignment with the connected Management System
- Reduced setup effort for users
🧩 More Control Over Workloads
Nerve 3.2 improves control over container-based workloads.
Users can now control individual containers inside a compose workload without affecting the other containers in the same workload.
Key benefits
- More precise workload operation
- Faster recovery of individual containers
- Less disruption to running compose workloads
- Better control for machine operators
🛡️ Improved Reliability, Auditability, and Field Support
TPM lockout behavior improved
Default TPM lockout parameters have been adjusted to reduce the risk of access loss during repeated power cycles, for example during machine setup. The goal is to make lockouts less likely and recovery faster.
Key benefits
- Better availability of Nerve nodes during commissioning
- Reduced risk of temporary access loss
- More robust behavior in real-world installation scenarios
Network connection status visible on the console
The console can show high-level network connection information without login. This includes the Management System URL and whether the Management System can be reached by HTTPS.
Key benefits
- Field staff can check connectivity quickly
- No login required for basic network diagnostics
- Faster troubleshooting during installation and service
Audit log coverage extended
Audit logging has been extended to cover remaining events in the Management System and Local UI. This includes node-side events similar to Management System events, deletion of deployment logs, and downloads of node activity log files.
Key benefits
- Better traceability of important actions
- Improved audit readiness
- More complete operational history across Management System and Local UI
🚦 Summary
Nerve 3.2 is a usability-first release that makes day-to-day work with Nerve easier, clearer, and more consistent.
The biggest step forward is the new UI experience: a modernized interface, improved icons, cleaner navigation, and a redesigned node list. Node grouping is now based on labels instead of folders, and drag and drop automatically updates the label assignment. This makes fleet organization more flexible and easier to understand.
At the same time, Nerve 3.2 improves automation and operational control with expanded DNA capabilities, better APIs, access tokens, Docker registry compatibility, system metrics APIs, and more reliable deployment workflows.
In short, Nerve 3.2 helps users:
- Work faster with a cleaner and more consistent UI
- Manage nodes more flexibly through label-based grouping
- Automate more configuration through DNA and APIs
- Integrate Nerve more easily into customer monitoring and DevOps workflows
- Troubleshoot and operate nodes with better visibility and less confusion
If Nerve 3.1 focused on security and production readiness, Nerve 3.2 focuses on making the product easier and more efficient to use every day.