Richmond, Virginia, United StatesCity area Natural Earth · GeoNames

Tridium: Building system integration through Niagara software and JACE controllers

Tridium provides Niagara software, JACE controllers and supervisory tools for integrating building systems and operational data.

Company-reported

1,000,000+ Niagara Framework instances worldwide7 Reported 2021

Summary

Best for
Multi-vendor building projects needing a common engineering, visualisation and supervisory layer.
Less suited to
Assuming every driver, point count or third-party module is included in any Niagara-branded controller licence.
Deployment
Niagara on JACE hardware, compatible partner controllers or a server-level Supervisor, with optional cloud services.
Data in
Device and system data through configured Niagara drivers; Supervisor aggregates histories, alarms and operational information.
Pricing
Software, controller capacity, drivers and maintenance depend on the partner offering; obtain a licence-specific project quotation.
Assessed
15 October 2026, against our March 2026 criteria

Overview

Niagara Framework is Tridium's integration software for connecting devices and operational systems into a shared environment. It provides the platform on which controllers, supervisory applications and partner products are built. Niagara is therefore a software ecosystem as well as a set of Tridium-branded hardware products.

The Niagara Supervisor illustrates the supervisory layer: it combines information from JACE controllers and other devices, with browser graphics, alarms, histories, scheduling and enterprise integration. For a building owner, this creates a common operating view across equipment supplied by different manufacturers. For an integrator, it provides one engineering environment for organising points and building the required application.

Offering

The JACE controller range hosts Niagara close to field equipment. Tridium's current page presents JACE 9000 for Niagara 4.13 and later, alongside documentation for JACE 8000 and IO R expansion. IO R adds physical inputs and outputs, so a project can combine software integration with direct connections to suitable sensors and actuators.

Niagara Edge 10 is a separate compact controller offering, while Niagara Supervisor provides server-level functions above the field estate. Keeping those roles distinct helps a designer decide where control logic, data collection and long-term histories belong. The controller and supervisor are complementary parts of a system rather than identical devices in different enclosures.

Products and platforms

  1. Niagara Framework

    Integration software

    Software platform for device integration and operational applications.2

  2. Niagara Portability SDK

    OEM development toolkit

    Enables partner deployment of Niagara on approved hardware.1

  3. Niagara Cloud Suite

    Cloud services

    Separate data, recovery and remote-access services.6

Technology

Tridium's developer resources support building modules and extensions for Niagara. Its Portability SDK allows approved partners to deploy the framework on their own hardware, extending the platform beyond Tridium's JACE range. This explains why Niagara-based products can have different physical interfaces and additional manufacturer-specific software.

The platform's protocol and driver ecosystem does not mean every licensed installation has identical capabilities. Driver availability, device limits and module versions must be checked for the actual station. Tridium's product-security resources provide a separate route for reviewing advisories and maintaining the software estate.

The Niagara 4.14 features overview from 2024 shows the breadth of the driver library: BACnet, Modbus, LonWorks, M-Bus over serial and TCP/IP, OPC UA, MQTT and an HTTP client sit in the same driver manager, and histories can be exported to MySQL, Microsoft SQL Server or Oracle databases or to CSV. Tagging supports Project Haystack and, from 4.14, a Brick Schema dictionary. Release 4.14 also added SAML authentication options, a certificate signing service for station PKI and a multi-tier security dashboard. BACnet support is tested independently: BTL listing 31446 records Niagara Edge 10 as a BACnet building controller, router, gateway and broadcast management device at protocol revision 16, tested in November 2025 with BACnet/SC hub and MS/TP support.

Security has a public record too. CISA advisory ICSA-18-191-03, first posted in July 2018, covered a path traversal flaw and an authentication bypass in Niagara AX 3.8 and Niagara 4.4 on Windows. In July 2025 Nozomi Networks Labs reported 13 vulnerabilities in Niagara Framework, six rated CVSS 9.8, which are fully exploitable when a station is misconfigured with encryption disabled. The Hacker News lists fixes in 4.14.2u2, 4.15u1 and 4.10u11, and Facilities Dive reports Tridium's advice to patch, review authorised users and follow its hardening guide. Tridium's development lifecycle holds an ISASecure SDLA certificate against IEC 62443-4-1, issued by exida in January 2024 and valid until February 2027; it certifies the process, not each release.

Markets

Niagara Supervisor combines centralised logging, alarms, schedules and graphics for a network of controllers. Those functions are useful across a campus or a portfolio of buildings, where an operator needs to compare conditions and investigate faults without treating every controller as an isolated screen. Tag-based graphics and analytics support repeatable engineering across that estate.

The Niagara Cloud Suite adds services alongside the deployed Niagara systems. Tridium presents separate offerings for data, recovery and remote access, rather than one mandatory replacement for local control. A buyer can therefore distinguish the on-site automation architecture from additional services used to support data access, maintenance or recovery across multiple locations.

Company

Tridium's history describes a functional prototype in 1997 and the launch of Niagara Framework in 1999. Tridium’s Niagara Summit history timeline dates company founding to 1995, separately from the 1999 Niagara launch. The same history records Honeywell's acquisition in 2005 and describes Tridium as an independent business entity within Honeywell International.

The company gives its headquarters as Richmond, Virginia, with offices in other regions. Its commercial model includes systems integrators, developers and manufacturers building on Niagara. The Powered by Niagara programme is a concrete example: partner hardware can use the framework through Tridium's portability approach, while the partner contributes its own hardware and application offering.

Tridium's own history traces the growth of the installed base: Niagara passed 100,000 instances in 2008, 500,000 in 2016 and 1,000,000 in 2021. Niagara 4 and the JACE 8000 launched in 2015, Niagara Edge 10 in 2018 and JACE 9000 in 2023. Product security is handled by a response team that takes encrypted reports and follows coordinated vulnerability disclosure, as set out on its product security page.

Assessment

Niagara is the established integration layer for multi-vendor building estates, and the evidence supports that standing: more than one million instances by 2021, BTL-listed BACnet controllers including BACnet/SC, and a driver library covering Modbus, LonWorks, M-Bus, OPC UA and MQTT. Honeywell has owned Tridium since 2005. The caution is security in the field. CISA published a Niagara advisory in 2018 and Nozomi Networks disclosed 13 flaws in July 2025, six rated CVSS 9.8 where encryption is misconfigured. Tridium's development process holds an ISASecure IEC 62443-4-1 certificate, but outcomes depend on integrators keeping stations patched and hardened. Commercial terms are set by partners and are not published.

  • Interoperability

    Independent sources Proven for legacy and current estates: BACnet Testing Laboratories listed Niagara Edge 10 in November 2025 as a building controller, router, gateway and BBMD at revision 16 with BACnet/SC and MS/TP.

    Full note and sources

    The 4.14 driver manager adds Modbus, LonWorks, M-Bus, OPC UA, MQTT, SQL export and Haystack and Brick tagging, and OEMs run Niagara on their own hardware. Driver availability varies by licence and partner build.

    Sources: 1, 2, 11, 13

  • Scale

    Independent sources Tridium reports 1,000,000 Niagara instances in 2021, up from 100,000 in 2008, and Facilities Dive cites more than a million instances worldwide in 2025.

    Full note and sources

    The platform reaches many more buildings through Powered by Niagara partner products, which the public sources do not count.

    Sources: 1, 7, 16

  • Stability

    Independent sources Founded in 1995, Niagara launched in 1999 and Tridium has been a Honeywell business since 2005.

    Full note and sources

    Niagara 4 has run since 2015 with a long-term-support release (4.10) and yearly feature releases through 4.14 in 2024. Honeywell ownership is confirmed by independent press coverage.

    Sources: 7, 10, 11, 16

  • Functionality

    Independent sources Covers supervisory control, alarming, scheduling, trending, on-call notification, history archiving, provisioning jobs across many stations and cloud services.

    Full note and sources

    The BTL listing confirms alarm, scheduling and trending services at the BACnet level. Analytics beyond tagging and history export depend on partner modules.

    Sources: 3, 6, 11, 13

  • Security

    Independent sources Process and features are strong: an exida ISASecure SDLA certificate against IEC 62443-4-1 valid to February 2027, a PSIRT with coordinated disclosure, TLS 1.3, SAML, MFA enrolment and a station security dashboard.

    Full note and sources

    The field record is mixed: a 2018 CISA advisory rated CVSS 7.4 and 13 flaws disclosed in July 2025, six rated 9.8 when encryption is disabled by misconfiguration, fixed in 4.10u11, 4.14.2u2 and 4.15u1.

    Sources: 9, 11, 12, 14, 15, 16

  • Quality

    Independent sources Mature, versioned platform with public developer resources, unit-test APIs added in 4.14 and an independent BACnet conformance listing.

    Full note and sources

    The 2025 vulnerabilities and the dependence on partner engineering quality hold the score below 5.

    Sources: 8, 11, 13, 15

  • Transparency

    Independent sources Product pages, feature overviews, history and the security reporting process are public, and advisories reach CISA and the press.

    Full note and sources

    Pricing, licence capacity and driver bundles are set by channel partners and are not published.

    Sources: 4, 9, 11, 14

How we score companies

Alternatives in Building operations software

What to look for in Building operations software