Niagara 5 Readiness: A Practical Checklist for Niagara 4 Sites
Niagara 5 brings Java 21, a new interface and mandatory module signing. Here is what changes, which hardware is supported and how to prepare your sites.
Niagara 5 is the first major version of Tridium's framework since Niagara 4 replaced NiagaraAX in 2015. It is a big change under the bonnet but, handled properly, a smooth one for building owners. This guide sets out what we know about Niagara 5, what it means for your controllers, supervisors and drivers, and a checklist you can work through now so the move is planned rather than forced.
Niagara 5 release timeline
Tridium has staged the Niagara 5 release over 2026:
| Milestone | Timing |
|---|---|
| Developer alpha | Q1 2026 |
| Early access for systems integrators | Q3 2026 |
| Beta release | End of Q3 2026 |
| General availability (Niagara 5.0) | Target Q4 2026 |
| Niagara 4 end of life | Q3 2028 |
| Niagara 4.15 updates and maintenance | Through Q4 2028 |
Dates can move, and early versions of any major release are best trialled before they reach a live estate. For most building owners the realistic plan is: prepare during 2026, pilot Niagara 5 on a supervisor and a few controllers during 2027, and complete the estate before Niagara 4 support ends in 2028.
What changes in Niagara 5?
Java 21
Niagara 4 runs on Java 8. Niagara 5 moves to Java 21, bringing performance, security and long-term support benefits. For end users this is invisible. For anyone with custom modules it is the biggest change: code written for Java 8 may need refactoring before it will compile and run.
Mandatory module signing
In Niagara 4 an unsigned module produces warnings and, depending on the verification level, may still load. In Niagara 5 every module must carry a valid digital signature. Unsigned or legacy-signed modules will not load. This affects:
- third-party drivers from smaller vendors
- custom modules written in-house or by a previous integrator
- old modules carried forward from NiagaraAX migrations
Our guide to code signing certificates explains how signing and trust stores work today; the same principles apply, but with no "warn and continue" option.
New user interface
Niagara 5 introduces redesigned navigation and new light and dark themes. Niagara 4 themes do not carry over. Px graphics migrate through Tridium's N4-to-N5 migrator, but anything relying on custom widgets or modules needs testing.
Hardware support
| Hardware | Niagara 5 |
|---|---|
| JACE 9000 | Supported |
| JACE 8000 / JACE 834 | Not supported; stays on Niagara 4 (4.15 final) |
| Niagara Edge 10 | Not supported; stays on 4.15, end of life |
| NiagaraAX JACEs (JACE-3E, 6E, 7…) | Not supported; AX only |
| Supervisors (Windows/Linux servers) | Supported, subject to OS requirements |
| OEM / third-party controllers | Each manufacturer sets its own Niagara 5 schedule |
A Niagara 5 supervisor can supervise Niagara AX, Niagara 4 and Niagara 5 stations at the same time, so unsupported controllers do not block a supervisor upgrade.
Migration rules
- Niagara 4 to Niagara 5: the station must first be on Niagara 4.15 LTS, then the N5 migrator converts it.
- NiagaraAX to Niagara 5: no direct path. Migrate to Niagara 4 first, then to Niagara 5.
- Highest version at the top: the supervisor must always run the highest Niagara version in the architecture. Upgrade supervisors before controllers.
- Coexistence on one PC: Niagara 4 and Niagara 5 Workbench can be installed side by side, but cannot run at the same time.
Licensing and SMA
An active Software Maintenance Agreement (SMA) is required for a Niagara 4 supervisor to be eligible for migration to Niagara 5, and a migration fee may apply. SMAs for Niagara 4 JACEs and supervisors remain available after Niagara 4 reaches end of life, so you can keep supported Niagara 4 sites covered while you migrate.
Your Niagara 5 readiness checklist
Work through these steps now. None of them depends on Niagara 5 being released, and most improve your current system anyway.
1. Build an inventory of every Niagara host
For each controller and supervisor, record:
- model (JACE 8000, JACE 9000, Edge 10, IONA, OEM device, server)
- Niagara version and build
- Host ID and licence features
- SMA expiry date
- installed modules, including third-party drivers and versions
- criticality of the site or plant
A spreadsheet is fine. Without it, every later step is guesswork.
2. Renew lapsed SMAs on assets you will migrate
Supervisors without an active SMA cannot migrate. JACE 8000s without an active SMA cannot use Tridium's licence transfer promotion to a JACE 9000. Renewing is almost always cheaper than relicensing.
3. Standardise on Niagara 4.15
Niagara 4.15 is both the final Niagara 4 release and the required starting point for Niagara 5. Moving stations to 4.15 now:
- gets them on the best-supported Niagara 4 version until 2028
- surfaces module, driver and licence problems early
- makes the eventual Niagara 5 migration a single, predictable step
Use matching Workbench and driver builds for each release; see Niagara Workbench versions.
4. Plan the JACE 8000 and Edge 10 replacements
These controllers will never run Niagara 5. Decide for each one whether it will:
- stay on Niagara 4.15 under a Niagara 5 supervisor for now
- be replaced with a JACE 9000, using the licence transfer promotion where eligible (see the JACE 8000 to 9000 upgrade guide)
- be replaced with an IONA Niagara 4 controller where onboard I/O, LoRaWAN or 4G would simplify the panel
For Edge 10 sites, see Edge 10 end of life and replacements.
5. Audit every module for signing
List each module that is not from Tridium. For each, confirm the vendor will provide a Niagara 5 build signed with a valid certificate. Custom modules need a developer to port them to Java 21 and sign them. If the author is no longer available, plan to replace the function with standard components or a supported driver.
For Tyrrell Products drivers, contact our team with your driver list and Niagara versions and we will confirm the Niagara 5 position for each one.
6. Review custom graphics and themes
Identify Px pages that use custom widgets, third-party modules or theme overrides. Standard Px pages migrate automatically; custom ones need testing, and themes will need redoing in the new UI.
7. Check supervisor infrastructure
Confirm the supervisor's operating system, CPU, memory and disk meet Niagara 5's requirements. A supervisor running an unsupported Windows version is a problem regardless of Niagara. Check memory allocations too; see managing memory allocations.
8. Tidy up security
Use the preparation as a chance to remove shared accounts, enforce strong passwords, enable two-factor authentication or LDAP, renew expiring certificates and segment BMS networks from corporate IT.
9. Train the team
Niagara 5 looks and feels different. Engineers will need refresher training on the new interface and any changed workflows. Make sure their Niagara 4 certification is current first; see the Niagara 4 certification guide.
10. Pilot before the estate
When Niagara 5 is generally available, migrate a test supervisor and one or two non-critical controllers first. Run them for several weeks, check alarms, histories, graphics and integrations, then roll out site by site.
Niagara 5 and cyber security
Security is one of the strongest reasons to plan the move. Java 8 reaches the end of its supported life across the industry, while Java 21 is a current long-term support release. Mandatory module signing closes a route for tampered or untrusted code to load into a station. And hardware such as the JACE 9000 adds secure boot, which checks the integrity of the software from power-on. For organisations whose building systems now sit inside IT security audits, cyber insurance questionnaires or public-sector frameworks, being able to show a supported, signed, patched platform matters.
What Niagara 5 means for each role
Building owners and estates teams
Your main decisions are budget and timing. The controllers that need replacing (JACE 8000, Edge 10, AX hardware) are known now, so the cost can be phased over 2026 to 2028 instead of arriving as an emergency. Ask your integrator for an inventory and a costed plan, and keep SMAs active on everything you intend to keep.
Systems integrators
Expect questions from every client with Niagara 4 sites. The integrators who win the migration work will be those who have audited their customer base, tested their standard templates and graphics on Niagara 5, confirmed their driver supply chain, and trained their engineers early.
Developers of custom modules
Port to Java 21 and sign everything. Code that relied on deprecated Java APIs or on unsigned modules loading with warnings will need work. Start testing against the early-access builds as soon as you can.
Facilities and operations staff
Day-to-day operation changes the least. Graphics migrate, schedules and alarms behave the same, and browsers remain the front end. The new interface will need a short familiarisation session.
A sample migration timeline
For a typical estate with one supervisor and a mix of JACE 8000 and JACE 9000 controllers:
| When | Activity |
|---|---|
| Now to Q4 2026 | Inventory, renew SMAs, upgrade stations to 4.15, audit modules, order JACE 8000 replacements under the transfer promotion |
| Q4 2026 to Q2 2027 | Test Niagara 5 on a lab supervisor with copies of real stations; confirm drivers and graphics |
| 2027 | Upgrade the supervisor to Niagara 5; it continues to supervise Niagara 4 JACEs |
| 2027 to 2028 | Migrate JACE 9000 stations to Niagara 5 site by site; replace remaining JACE 8000 and Edge 10 hardware |
| By Q4 2028 | Every critical site either on Niagara 5 or on Niagara 4.15 with a dated replacement plan |
Budgeting for Niagara 5
Typical cost lines for a migration programme:
- SMA renewals on assets you will keep
- Migration fees for supervisors, where they apply
- Replacement controllers for JACE 8000 and Edge 10 hardware, reduced by the licence transfer promotion where eligible
- Third-party driver updates for Niagara 5 builds
- Engineering for station upgrades, testing and site visits
- Training for engineers and operators
Spreading the work over two or three budget years is usually possible if planning starts in 2026.
What if you do nothing?
Your sites will keep running. Niagara 4.15 is supported until the end of 2028, and controllers do not stop working when software support ends. But over time:
- security patches stop, which becomes a problem for audits and cyber insurance
- new drivers and features arrive only for Niagara 5
- JACE 8000 and Edge 10 spares become harder to find
- the licence transfer promotion and other migration offers expire
- engineers trained on Niagara 5 become the norm
Planning early spreads the cost across budget years and avoids emergency replacements.
Frequently asked questions
When is Niagara 5 released?
Tridium is targeting general availability of Niagara 5.0 in Q4 2026, after early access in Q3 2026 and a beta at the end of Q3 2026.
Will the JACE 8000 support Niagara 5?
No. The JACE 8000 and JACE 834 stay on Niagara 4, with 4.15 LTS as their final version. The JACE 9000 is Tridium's Niagara 5 controller.
Can a Niagara 5 supervisor work with Niagara 4 JACEs?
Yes. A Niagara 5 supervisor supports Niagara AX, Niagara 4 and Niagara 5 stations together. The supervisor must run the highest version in the system.
Do I need an SMA to upgrade to Niagara 5?
Yes, an active SMA is required for a Niagara 4 supervisor to be eligible for migration, and a migration fee may apply.
How long will Niagara 4 be supported?
Niagara 4 reaches end of life in Q3 2028, with 4.15 receiving updates and maintenance through Q4 2028.
Will my Px graphics work in Niagara 5?
Standard Px pages are converted by Tridium's N4-to-N5 migrator. Pages that rely on custom widgets, third-party modules or theme overrides need testing and may need rework, and Niagara 4 themes do not carry over.
Can I migrate NiagaraAX straight to Niagara 5?
No. AX stations must be migrated to Niagara 4 first, then from Niagara 4.15 to Niagara 5.