2. Changes in this release (Neeve Portal v1.6.1, September 2026)
2.1 New Features
None in this release.
2.2 Enhancements
Editable TCP connection ports on Cloud BMS endpoints. The TCP connection on a Cloud BMS endpoint can now be edited in place from the endpoint details page. Open the endpoint, edit the TCP connection, change the port and save; the port is validated, a confirmation is shown, and the endpoint remains active throughout. Changing a port no longer requires deleting the endpoint and onboarding it again. Editing is available to Org Admin and Site Operator roles; users with Access User permissions see the TCP connection in view-only mode.
Standardized site names in the Neeve Agent. Site selection in the Neeve Agent now presents each site in <Node Name>-<System Network Name> format, so the same naming appears in the Neeve Agent and in the Neeve Portal. Existing sites continue to work and are shown in the new format, and site names containing special characters are displayed correctly.
2.3 Bug Fixes
None in this release.
3. Prerequisites
3.1 Cloud Requirements
The following cloud platforms are supported:
Amazon AWS
Microsoft Azure
VMware vSphere v6.x
Google Cloud
3.1.1 Cloud Connector Compute Requirements
2 vCPU
2GB RAM
10GB HDD
Public IP address
4. Issues
4.1 Known Limitations
The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available within the Neeve Portal.
New in this release
None in this release.
Carried forward from previous releases
The Node Config UI displays APN details read from the SIM's carrier profile rather than the custom APN you configured. The configured APN is applied correctly; only the displayed value is wrong. A fix is expected in a subsequent release.
A configured APN can be overwritten with a new value, but it cannot be unset. There is currently no option to remove an APN configuration once saved.
APN names accept special characters that are not valid in an APN. Validation is not applied on this field.
Changing the CIDR of a DHCP network that has TCP connections enabled stops those TCP connections from working. Workaround: disable Remote Access Agent (RAA) on the network and re-enable it; this restores the routes. This will be addressed as part of TCP onboarding changes.
Setting a DHCP address pool where the start and end addresses are the same does not produce an inline error. A toast message appears when you attempt to create the network.
Entering a DHCP TAN subnet smaller than /24 does not produce an inline error. The deployment is blocked, but the message appears only on save.
DNS resolution behavior on a DHCP System Network depends on the network's default destination. The DHCP service (dnsmasq) acts as the DNS server for devices on the network, and forwards queries to an upstream resolver: when the default destination is WAN Network, the node's configured DNS server is used; when the default destination is Tunnel, 8.8.8.8 is used.
If your portal is provisioned with Cloud BMS it can not be deactivated. This does not impact customer's portals without Cloud BMS. There is no currently available workaround.
Privilege escalation for a user doesn't trigger an email notification. There is no current workaround, please inform your users that their privileges have been increased.
For any configuration change or edit, the page requires a refresh to reflect the change.
When bulk onboarding endpoints, the success/failure toast messages fill the screen. Refer to the audit logs for more granular detail of which endpoints were successfully/unsuccessfully onboarded.
For users with access to multiple organization, logging out in one organization does not log them out of other organizations they are currently logged into. Please logout of all orgs manually, as required.
Users with access to a single endpoint or endpoint connection are listed under the parent org in the Hierarchy. There is currently no workaround.
Users with access or admin rights to multiple sites or portfolios are not listed under each of the associated sites or portfolios. The user will be listed under the site or portfolio where they have the highest privilege. A user's specific privilege can be viewed under the user's details page.
When marking a tile on the Launcher page as favorite, it will automatically be moved to the top of the first page. This can cause the tile to appear to disappear when marking a tile as favorite from the bottom of the page or on other pages other than Page 1. To verify access, return to the top of the first page of the Launcher screen.
Any change made to a System Network from the Secure Edge portal will be overwritten if a subsequent change is made to the same network from within the Neeve Portal. Once changes are made to a network from Secure Edge portal, subsequent changes should be made from Secure Edge portal to avoid configuration losses.
When using the "Setup and Configure Remote Access" onboarding flow to onboard Secure Edge Professional and Enterprise Nodes, the illustrations within the flow will not accurately reflect the form factor of these nodes. The network configuration step shows the correct diagram and should be followed as guidance on how to connect these models of nodes.
Export csv features limits the number of entries to 1000.
2. Changes in this release (Neeve Portal v1.6, August 2026)
2.1 New Features
DHCP Server networks. A System Network can now be configured with the Edge Node acting as the DHCP server for devices on that network. When you select DHCP Server as the network address type, the node deploys a DHCP service automatically as part of network creation — no separate service deployment step is required. From the Customize DHCP dialog you can set the CIDR, choose a preset or custom address pool, set the lease time, and define MAC-based host reservations. Once the network is created, a DHCP tab and a Lease tab appear on the network details page.
Enhanced Node Config UI. The node's local configuration interface now includes built-in tools for diagnosing WAN connectivity at the node itself, without needing portal access. This includes connectivity tests for internet reachability, Neeve Portal reachability, and cellular status, plus a cellular signal strength indicator.
Proxy and APN configuration during onsite provisioning. Web proxy settings and cellular APN settings can now be configured directly at the node during onsite provisioning, rather than requiring a separate configuration pass. The node's proxy configuration is visible in the Neeve Portal under the node's Internet Connection tab.
2.2 Enhancements
Cloud Connector is connected automatically. When you onboard a System Network, the Cloud Connector is now selected and connected automatically. You no longer need to choose a Cloud Connector as part of the onboarding flow.
2.3 Bug Fixes
SSO users are no longer prompted for MFA when MFA is handled by the identity provider. SSO-authenticated users were being asked for a second authentication factor even where their IdP had already enforced MFA.
Frozen columns no longer overlap when scrolling. In the Nodes, Networks, and Endpoints tables, scrolling horizontally with columns frozen caused frozen and scrolling columns to render on top of each other.
System Type selection is no longer shown for endpoints on unsupported network types. The System Type option was presented for endpoints on network types that do not support it, offering configuration choices that could not apply.
Deleting a TAN no longer deletes endpoints belonging to another TAN with the same CIDR. Where two TAN networks on the same node used the same CIDR, deleting one removed endpoints from both. (NEEVEDEV-7272)
Proxy port validation on node configuration. Invalid port values are now rejected with an inline error rather than being accepted and saved.
Stack traces removed from user-facing errors. Error messages across the portal have been standardized. Validation failures, invalid CIDR and MAC entries, missing mandatory fields, and invalid email addresses now produce user-readable messages with guidance on how to correct the input, instead of raw technical output.
DHCP CIDR validation, lease table refresh, and MAC reservation persistence. A group of DHCP fixes covering rejection of malformed CIDR values, correct refresh behavior on the lease table, and reservations surviving logout and session restart.
Network management fixes. Corrections to TAN configuration, tunnel connectivity, and DNS query handling.
3. Prerequisites
3.1 Cloud Requirements
The following cloud platforms are supported:
Amazon AWS
Microsoft Azure
VMware vSphere v6.x
Google Cloud
3.1.1 Cloud Connector Compute Requirements
2 vCPU
2GB RAM
10GB HDD
Public IP address
4. Issues
4.1 Known Limitations
The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available within the Neeve Portal.
Refer to this article for a comprehensive list of functional limitations.
New in this release
The Node Config UI displays APN details read from the SIM's carrier profile rather than the custom APN you configured. The configured APN is applied correctly; only the displayed value is wrong. A fix is expected in a subsequent release.
A configured APN can be overwritten with a new value, but it cannot be unset. There is currently no option to remove an APN configuration once saved.
APN names accept special characters that are not valid in an APN. Validation is not applied on this field.
Changing the CIDR of a DHCP network that has TCP connections enabled stops those TCP connections from working. Workaround: disable Remote Access Agent (RAA) on the network and re-enable it; this restores the routes. This will be addressed as part of TCP onboarding changes.
Setting a DHCP address pool where the start and end addresses are the same does not produce an inline error. A toast message appears when you attempt to create the network.
Entering a DHCP TAN subnet smaller than /24 does not produce an inline error. The deployment is blocked, but the message appears only on save.
DNS resolution behavior on a DHCP System Network depends on the network's default destination. The DHCP service (dnsmasq) acts as the DNS server for devices on the network, and forwards queries to an upstream resolver: when the default destination is WAN Network, the node's configured DNS server is used; when the default destination is Tunnel, 8.8.8.8 is used.
Carried forward from previous releases
If your portal is provisioned with Cloud BMS it can not be deactivated. This does not impact customer's portals without Cloud BMS. There is no currently available workaround.
Privilege escalation for a user doesn't trigger an email notification. There is no current workaround, please inform your users that their privileges have been increased.
For any configuration change or edit, the page requires a refresh to reflect the change.
When bulk onboarding endpoints, the success/failure toast messages fill the screen. Refer to the audit logs for more granular detail of which endpoints were successfully/unsuccessfully onboarded.
For users with access to multiple organization, logging out in one organization does not log them out of other organizations they are currently logged into. Please logout of all orgs manually, as required.
Users with access to a single endpoint or endpoint connection are listed under the parent org in the Hierarchy. There is currently no workaround.
Users with access or admin rights to multiple sites or portfolios are not listed under each of the associated sites or portfolios. The user will be listed under the site or portfolio where they have the highest privilege. A user's specific privilege can be viewed under the user's details page.
When marking a tile on the Launcher page as favorite, it will automatically be moved to the top of the first page. This can cause the tile to appear to disappear when marking a tile as favorite from the bottom of the page or on other pages other than Page 1. To verify access, return to the top of the first page of the Launcher screen.
Any change made to a System Network from the Secure Edge portal will be overwritten if a subsequent change is made to the same network from within the Neeve Portal. Once changes are made to a network from Secure Edge portal, subsequent changes should be made from Secure Edge portal to avoid configuration losses.
When using the "Setup and Configure Remote Access" onboarding flow to onboard Secure Edge Professional and Enterprise Nodes, the illustrations within the flow will not accurately reflect the form factor of these nodes. The network configuration step shows the correct diagram and should be followed as guidance on how to connect these models of nodes.
Export csv features limits the number of entries to 1000.
2. Changes in this release (Neeve Portal v1.4.5)
This release is only for our multi-tenant architecture. Not all portals will be upgraded to this release at this time.
2.1 New Features
Single Sign-On (SSO) – SAML Support
Full SAML-based SSO configuration via UI
Create, edit, and manage SSO providers directly in the portal
Identity Provider (IdP) configuration view with key metadata (Entity ID, SSO URL, certificates)
Home Realm Discovery (HRD) support for domain-based login routing
SSO enforcement controls (force users to authenticate via SSO)
Enable/disable SSO connections dynamically
SSO User Experience Improvements
Domain-based user invitation flow aligns users to correct IdP
Improved lifecycle handling for SSO connections (create, update, delete)
2.2 Enhancements
User Management & Organization Experience
Consistent use of Organization Display Name across UI, emails, and system surfaces
Improved user lifecycle handling (disable, delete, restore flows)
Better handling of multi-org user attribution (e.g., “Created By” accuracy)
UI / Design System (DLS) Improvements
Migration from “Card” to “Tile” components for consistency
Improved visual consistency across portal pages
Introduction of reusable Accordion component
Favicon now reflects organization display name initials
General UI cleanup and consistency improvements across components
Table & Form Behavior
Improved validation behavior (e.g., removal of unnecessary mandatory fields)
Cleaner handling of bulk actions and table interactions
Performance & Backend Improvements
Per-request timeout controls for better API reliability
Redis performance improvements (replacing blocking operations with scalable patterns)
Improved handling of high-volume operations and large datasets
Developer & CI/CD Improvements
Automated DLS updates and versioning strategy
Improved deployment automation across control plane and data plane
Enhanced developer tooling and validation checks
Eventing & Data Pipeline Foundations
Introduction of event-driven architecture components:
JetStream-based event publishing
Publisher pipeline with retry and recovery mechanisms
Projector service scaffolding
Metrics instrumentation for event pipelines (rate, lag, errors)
Idempotency and event deduplication logic
Startup recovery (“catch-up”) for missed events
2.3 Bug Fixes
User & Access Management
Fixed issue where user disable action could fail
Fixed deleted users incorrectly remaining in “Active” state
Fixed incorrect “Created By” attribution across organizations
Fixed issues with user deletion and restoration flows
UI / Portal Issues
Fixed Delete button not functioning in configuration screens
Fixed welcome email sender displaying incorrectly (“no-reply” issue)
Fixed UI inconsistencies in SSO configuration views
Migration & Networking
Fixed multiple errors during CloudBrink migration steps (400/500 errors)
Fixed missing WAN network visibility after migration
Fixed issues with service port mismatches in network views
Logs & Audit
Improved migration completeness for audit and access logs
Addressed inconsistencies in log data after migration
3. Prerequisites
3.1 Cloud Requirements
The following cloud platforms are supported:
Amazon AWS
Microsoft Azure
VMware vSphere v6.x
Google Cloud
3.1.1 Cloud Connector Compute Requirements
2 vCPU
2GB RAM
10GB HDD
Public IP address
4. Issues
4.1 Known Limitations
The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available.
Refer to internal documentation for a comprehensive list of limitations.
Cloud BMS-enabled portals cannot be deactivated.
Privilege escalation does not trigger email notifications.
UI does not auto-refresh after configuration changes.
Bulk onboarding toast messages may overwhelm the UI.
Multi-org logout must be handled manually.
User hierarchy visibility limitations across orgs/sites/portfolios.
Launcher favorites reorder behavior may appear inconsistent.
Secure Edge and Neeve Portal configuration conflicts may overwrite changes.
Some onboarding diagrams do not reflect all hardware form factors.
CSV export is limited to 1000 entries.
Release Notes - Neeve Portal V1.4.1 - April 2026
Release Notes - Neeve Portal V1.4.1 - May 2026
2. Changes in this release (Neeve Portal v1.4.1)
This release is only for our multi-tenant architecture. Not all portals will be upgraded to this release at this time.
2.1. New features
2.2 Enhancements
Table v2 customization - Audit and Access Logs
Configurable columns (predefined structure, no hide/show toggle for users)
Better handling of large datasets
Improved UI/UX consistency
Re-fetch /Refresh Interval Centralization
System now fetches fresh data automatically at the defined interval.
The interval is controlled by environment variable
Query Invalidation (Fresh Data Retrieval)
Eliminated stale data issues caused by missed invalidations
Ensures fresh data is always fetched after updates
UI consistently reflects the latest state
2.2 Bug fixes
Access Log pagination persists after browser refresh — page does not reset to Page 1: On browser refresh, Access Log now defaults back to Page 1.
Pagination state no longer persists across browser refresh.
User not permanently deleted after 30-day retention period post-deletion: Issue was resolved.
SL node onboarding: Node details API is triggered repeatedly throughout network creation wizard (excessive duplicate calls): Issue was resolved.
3. Prerequisites
3.1. Cloud Requirements
The following cloud platforms are supported:
Amazon AWS
Microsoft Azure
VMware vSphere v6.x
Google Cloud
3.1.1. Cloud Connector compute requirements
2 vCPU, 2GB RAM, 10GB HDD, Public IP address
4. Issues
4.1. Known Limitations
The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available within the Neeve Portal.
Refer to this article for a comprehensive list of functional limitations.
If your portal is provisioned with Cloud BMS it can not be deactivated. This does not impact customer’s portals without Cloud BMS. There is no currently available workaround.
Privilege escalation for a user doesn’t trigger an email notification. There is no current workaround, please inform your users that their privileges have been increased.
For any configuration change or edit, the page requires a refresh to reflect the change.
When bulk onboarding endpoints, the success/failure toast messages fill the screen. Refer to the audit logs for more granular detail of which endpoints were successfully/unsuccessfully onboarded.
For users with access to multiple organization, logging out in one organization does not log them out of other organizations they are currently logged into. Please logout of all orgs manually, as required.
Users with access to a single endpoint or endpoint connection are listed under the parent org in the Hierarchy. There is currently no workaround.
Users with access or admin rights to multiple sites or portfolios are not listed under each of the associated sites or portfolios. The user will be listed under the site or portfolio where they have the highest privilege. A user’s specific privilege can be viewed under the user’s details page.
When marking a tile on the Launcher page as favorite, it will automatically be moved to the top of the first page. This can cause the tile to appear to disappear when marking a tile as favorite from the bottom of the page or on other pages other than Page 1. To verify access, return to the top of the first page of the Launcher screen.
Any change made to a System Network from the Secure Edge portal will be overwritten if a subsequent change is made to the same network from within the Neeve Portal. Once changes are made to a network from Secure Edge portal, subsequent changes should be made from Secure Edge portal to avoid configuration losses.
When using the “Setup and Configure Remote Access” onboarding flow to onboard Secure Edge Professional and Enterprise Nodes, the illustrations within the flow will not accurately reflect the form factor of these nodes. The network configuration step shows the correct diagram and should be followed as guidance on how to connect these models of nodes.
Export csv features limits the number of entries to 1000.
Release Notes - Neeve Portal V1.4 - March 2026
2. Changes in this release (Neeve Portal v1.4)
This release is only for our multi-tenant architecture. Not all portals will be upgraded to this release at this time.
2.1. New features
Web portal domain is changing to be customer specific. Each customer portal will have their own subdomain in the format of <customer>.app.neeve.ai. If you’ve previously logged into the Neeve Portal via app.neeve.ai, see here for important instructions you need to follow to avoid log-in issues.
OT network convergence Is now better supported. A new system type is available—OT Network—that you can use for converged networks. Endpoints onboarded to an OT Network will have their type defined as part of onboarding (BMS, CCTV, etc.).
Audit logs for nodes and networks are now available within the Neeve Portal. Configuration changes are visible for nodes and networks under the “Analytics” menu. Node changes are also visible under the node details page.
Advanced HTTP rewrite rules for HTTP(s) connections are now supported. These changes need to be applied by Neeve Support. Contact support@neeve.ai if you experience issues with web connections and the “Apply Default Rules” toggle does not resolve the issue. See here for more details.
2.2 Enhancements
Launcher favorites have been improved to respond more quickly to selecting a tile as a favorite. Once you select a favorite, the Launcher page will sort the tiles so that your favorites always appear at the top of the page.
Global address support for sites is now supported in the hierarchy.
Welcome email branding now aligns with customer branding applied to the portal, including color, logo, and account name.
2.2 Bug fixes
Node count mismatch between the Hierarchy and Node list pages has been resolved.
Neeve Remote Access Agent application login issue has been resolved.
User search by company, phone number has been resolved.
Endpoint connection status is now shown correctly on the Launcher page.
Editing the auto-created TCP endpoint for TCP networks has been resolved.
Log-in loops and inability to proceed past the User Agreement acceptance has been resolved.
Portal branding logo not appearing in the top-right corner has been resolved.
When creating a Portfolio, associated Sites can now be created at the same time without issue.
The errant error that presented when changing a SystemNetwork’s Default Destination to “WAN” has been resolved.
3. Prerequisites
3.1. Cloud Requirements
The following cloud platforms are supported:
Amazon AWS
Microsoft Azure
VMware vSphere v6.x
Google Cloud
3.1.1. Cloud Connector compute requirements
2 vCPU, 2GB RAM, 10GB HDD, Public IP address
4. Issues
4.1. Known Limitations
The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available within the Neeve Portal.
Refer to this article for a comprehensive list of functional limitations.
If your portal is provisioned with Cloud BMS it can not be deactivated. This does not impact customer’s portals without Cloud BMS. There is no currently available workaround.
Privilege escalation for a user doesn’t trigger an email notification. There is no current workaround, please inform your users that their privileges have been increased.
For any configuration change or edit, the page requires a refresh to reflect the change.
When bulk onboarding endpoints, the success/failure toast messages fill the screen. Refer to the audit logs for more granular detail of which endpoints were successfully/unsuccessfully onboarded.
For users with access to multiple organization, logging out in one organization does not log them out of other organizations they are currently logged into. Please logout of all orgs manually, as required.
Users with access to a single endpoint or endpoint connection are listed under the parent org in the Hierarchy. There is currently no workaround.
Users with access or admin rights to multiple sites or portfolios are not listed under each of the associated sites or portfolios. The user will be listed under the site or portfolio where they have the highest privilege. A user’s specific privilege can be viewed under the user’s details page.
When marking a tile on the Launcher page as favorite, it will automatically be moved to the top of the first page. This can cause the tile to appear to disappear when marking a tile as favorite from the bottom of the page or on other pages other than Page 1. To verify access, return to the top of the first page of the Launcher screen.
Any change made to a System Network from the Secure Edge portal will be overwritten if a subsequent change is made to the same network from within the Neeve Portal. Once changes are made to a network from Secure Edge portal, subsequent changes should be made from Secure Edge portal to avoid configuration losses.
When using the “Setup and Configure Remote Access” onboarding flow to onboard Secure Edge Professional and Enterprise Nodes, the illustrations within the flow will not accurately reflect the form factor of these nodes. The network configuration step shows the correct diagram and should be followed as guidance on how to connect these models of nodes.
Release Notes - Neeve Portal V1.2.1 - January 2026
2. Changes in this release (Neeve Portal v1.2.1)
2.1. New features
None.
2.2 Enhancements
Improved the input guidance when creating new System Networks with Static IP assignment: We’ve updated the input box label and added tooltips to reduce confusion on the inputs required when configuring a new System Network with Static IP assignment.
Endpoint and Endpoint Connection Naming now supports spaces.
2.2 Bug fixes
Node Serial Number Display Issues: Fixed an issue where Serial Numbers for Nodes were not properly populating in the “Setup and Configure Remote Access” onboarding flow and in the “Available Inventory” page under Manage → Nodes.
TCP Connection Port Display Issue: Fixed an issue where not all configured ports would display within Neeve Portal when viewing and editing Endpoint Connection of type TCP.
TCP Connection Port Definition Issue: Fixed an issue where, when creating a TCP connection for a full network, comma separated ports would not be accepted.
Mobile Rendering Issue: Fixed an issue where the “Launcher” page would not render properly on mobile devices.
Release Notes - Neeve Portal V1.2 - December 2025
2. Changes in this release (Neeve Portal v1.2)
2.1. New features
Onboarding Multiple System Networks: Edge Nodes can now be configured with multiple System Networks (LAN’s). If your Node has multiple LAN interfaces available, you can onboard System Networks to each or multiple System Networks per LAN interface with VLAN tagging. For Nodes with only a single LAN interface, VLAN tagging is supported to add multiple System Networks. Refer to this article to learn more about adding multiple System Networks to a Node. This is not yet available within the Setup & Configure Remote Access workflow.
Table Customization and Improved Search and Filter: Tables within the platform can now be customized to fit your needs and includes improved search and filtering capabilities. Refer to this article to learn more about table customization. This feature is only available on the Users and Endpoints table, and will be made available for additional tables in future releases.
User Statuses: The status of users’ accounts is more clearly displayed. Complimentary actions have been added for each status to help support user management. Refer to this article to learn more about managing users.
2.2 Enhancements
Setup & Configure Remote Access workflow: The Setup & Configure Remote Access workflow has been improved to allow for adding a Site within the hierarchy from within the flow. Refer to this article to learn more about this enhancement.
Delete Handling: Delete handling has been improved. All nested objects are deleted with the parent object. This list of deleted objects is presented to the user before they confirm the delete.
RAA Onboarding: The onboarding of Remote Access Agent (RAA) endpoint connections (TCP connection type) has been improved to reduce the time taken to onboard connections. Please allow up to 5 minutes for TCP connections to be onboarded.
2.2 Bug fixes
Performance and stability enhancements.
3. Prerequisites
3.1. Cloud Requirements
The following cloud platforms are supported:
Amazon AWS
Microsoft Azure
VMware vSphere v6.x
Google Cloud
3.1.1. Cloud Connector compute requirements
2 vCPU, 2GB RAM, 10GB HDD, Public IP address
4. Issues
4.1. Limitations
The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available within the Neeve Portal.
Refer to this article for a comprehensive list of functional limitations.
Node and Network CRUD audit logs are not available within the Neeve Portal audit log. These can be viewed within the Secure Edge portal or Neeve Support can provide you with a CSV report upon request.
Adding multiple System Networks is not possible within the Setup & Configure Remote Access workflow. They can be configured manually by navigating to the Node where the additional networks are to be added.
If your portal is provisioned with CloudBMS it can not be deactivated. This does not impact customer’s portals without CloudBMS. There is no currently available workaround.