ALL SYSTEMS ONLINE / NewAHU Graphic Builder — configure any AHU and export native Niagara PX · $749, 25 exports included Try it live →

NIAGARAUI / HELP & ANSWERS

Clear answers.
Confident next steps.

Everything you need to choose, license and use your NiagaraUI products. From your first host ID to your next export.

FIND YOUR ANSWER

From purchase to project.

Search by keyword or choose a topic. Product-specific terms and the included guide apply to your purchase.

50 answers

A dashboard license covers the selected template for one Niagara host ID. Purchasing a template does not license every dashboard or every host in your organization. Check the product page and included license terms for the exact scope.

The host ID identifies the Niagara platform being licensed. It is not a station name, IP address, browser URL or Shopify order number. Connect to the target platform in Workbench and inspect its licensing information, typically in Platform > License Manager. Copy the host ID exactly; if you are unsure, ask the site administrator before purchasing.

Use the host ID of the Niagara platform where the licensed dashboard will run. Do not automatically use your engineering laptop’s host ID or the ID of a connected field controller. If your deployment spans a Supervisor and JACEs, confirm where the dashboard is installed and ask support about the required licensing before ordering.

Open Licensing & Credits, choose the dashboard and enter the new Niagara host ID. The displayed price is the selected template’s current price. Complete checkout for that additional license. Your license key is generated and emailed through the existing licensing process after purchase.

A dashboard license is tied to one host ID. A separate host requires an additional license, even when the same integrator manages both sites. A single host serving several buildings is different from several separately licensed hosts; confirm any multi-host or unusual deployment with support.

No. Select and license the dashboard you intend to deploy. ATRIUM, NODE, LUMA, PULSE, THERMA, SOLAR IQ, MESH and NEXA are separate products. A license for one template is not an all-template entitlement.

Contact support with your order reference, product, current host ID and intended new host ID before attempting activation on another host. Re-downloads and station backups do not change a license’s host assignment. Corrections, hardware replacements, VM migrations and transfers need review under your product terms; do not assume an automatic or free transfer.

Do not assume a production license also covers a separate development or recovery host. Explain the host IDs and intended use to support before deployment. A time-limited demo license is for evaluation and is not a substitute for production licensing.

The currently listed dashboard licenses are one-time purchases for the selected template and host ID. Builder credits are separate purchases. No monthly all-template or host-ID allowance is offered on the current Licensing & Credits page. Updates and any future plans follow their published product terms.

No. NiagaraUI dashboard and builder licenses are separate from Tridium Niagara platform, device, driver and third-party module licenses. Your station must also meet the product’s technical requirements and have the appropriate platform permissions.

Start with the application: ATRIUM for schools and education; LUMA for commercial offices; PULSE for campuses and portfolios; NODE and MESH for data centers at different levels of detail; THERMA for chiller plants; SOLAR IQ for solar and storage; and NEXA for laboratory and pharmaceutical environments. Compare the live demos, included views and specifications rather than choosing by appearance alone.

Templates differ in application, view structure and depth. Current dashboard prices range from $995 to $1,895 per host ID; the product page and checkout show the current price. Buying an additional host license uses that dashboard’s current price. A higher price does not mean every project needs that template.

Review the selected product’s Overview & features and Specifications & download sections and its included guide. Packages can contain dashboard files, PX pages, images, modules and documentation depending on the product. A demo screenshot does not promise that every visible asset, data source or integration is included.

Treat storefront demos as product previews with sample data unless explicitly stated otherwise. Your installation needs its own point bindings, permissions and configuration. Purchasing a graphic does not connect it to your building automatically or provide a building-management service.

Open the dashboard product page and choose View live demo in browser where available. Use the demo to explore navigation, views and the level of detail before purchasing. A browser preview does not activate a license on your Niagara host.

Use Request a free 5 day demo license on the product page, or open the license-server demo application. Complete the requested details accurately and follow the licensing emails and instructions. The demo is time-limited evaluation access; check its activation and expiry details before testing.

Choose Request a live demo on a product page to open the scheduling window and select an available date and time. Have your application, target Niagara version and questions ready. A scheduled walkthrough is separate from a five-day demo license.

Dashboards provide an operator interface for a particular application. Builder programs help you create equipment or floorplan graphics. Their application licenses and export credits are separate from dashboard host-ID licenses; owning one does not automatically include the other.

The current AHU Builder offer is $749 for one Windows 10/11 x64 application installation, bundled Blender/rendering resources, a PDF guide and 25 export credits. It is a one-time application purchase with no annual renewal stated in the current offer. Review the product page for current system requirements and included files.

Activation and licensed exports connect to the licensing server and require internet access. Check connectivity and any network restrictions before an export. Do not assume the browser Lite demo or an offline preview provides commercial export entitlement.

Moving an activated installation requires a device reset through support. Downloading or reinstalling the application does not reset activation or grant another installation. Provide the purchase email, order reference and Install ID when requesting help; keep a backup of your editable projects.

The Builder Programs page shows current availability. AXIS Floorplan Builder is currently marked Coming soon. Do not treat a preview or an available refill option as confirmation that a builder application has launched. Purchase a refill only when you already have a license for that matching builder.

Each completed top-level export uses one credit. Building, editing, saving and previewing do not use credits. A rendered image is different from the editable project file; save your project so you can revise it later. Check the current guide for your export workflow.

Open Licensing & Credits, select the matching builder and choose 25, 50, 75 or 100 credits. Complete checkout and follow the emailed refill-key instructions. In AHU Builder, redeem the key in License / Credits. Buying credits does not include a new builder application license.

Choose the exact builder you use. Refills are product-specific; do not assume AHU, Plant or future Floorplan credits are interchangeable. Dashboard host-ID licenses do not use builder export credits. If you bought the wrong pack, contact support before redeeming it.

Use the credit-pack and application license terms applicable to your purchase. Do not assume unused credits can be transferred, refunded or moved to a different builder or account. Contact support with your order reference before a planned account or installation change.

Yes. Software downloads are public so customers can download or re-download the packages. A download is not a license: a valid license for the selected dashboard and host ID is required to run it. Keep the package version and included guide together.

No. Downloading files again does not buy another host license, change the licensed host, reset a builder installation or refill export credits. Use Licensing & Credits for a new host license or refill and contact support for activation issues.

Use Account to access purchases with the email used at checkout. My Licenses is available for builder license details. Keep your order confirmation and licensing emails. If a purchase is missing, check which email was used and send support the order reference. Store account access and product activation are separate steps.

Check spam, junk, quarantine and the email address used at checkout. Confirm that payment completed and keep the order confirmation. If the licensing email is still missing, contact support with the product, order number and purchase email. Do not place a duplicate order just to trigger another email.

Contact support with your order reference and explain the requested correction. Ownership may need to be verified before access or license details can be changed. Do not share passwords or forward full license keys publicly. An email change does not automatically transfer a product license.

Review the published Terms & Conditions and the specific product terms before buying. The terms describe digital sales as final, with limited exceptions reviewed for issues such as corrupted files, duplicate purchases or inability to access a product. AHU Builder is non-refundable except where required by applicable law. Contact support about your specific order; do not assume a blanket 30-day refund guarantee.

Purchased products remain subject to their license. Redistribution, resale, sublicensing or sharing the original files is prohibited unless expressly permitted by the applicable terms. Deploying a licensed project for a client does not give permission to sell the underlying template as your own product.

Use the payment methods available at checkout. If your organization needs a purchase order, invoice or clarification on several project licenses, contact support before placing the order so the available arrangement can be confirmed.

Back up your station, extract the package and follow its instructions. Copy the required PX and image assets to the station locations referenced by the page, then attach the intended view and verify its point bindings. Import a BOG or install a module only if the package includes it and its guide requires it. Test before replacing a production view.

You must map and verify the graphic against your station points. Names alone do not guarantee correct binding. Copy actual ORDs from Workbench, confirm their data types and units, and check any relative or tag-based binding context. AHU Builder CSV matching assists this review; it does not remove the need to check each mapping.

Use a new project folder and unique filenames when importing. Copying files into an existing location can overwrite same-named assets. Keep a station backup and test the new view before deliberately switching operators to it.

AHU Builder exports target Niagara 4.8 and later. Dashboard templates list their own requirements, commonly N4.10+. Check required modules, station permissions and the target browser before deployment. We do not claim every combination of Niagara release, modules and browser has been tested. AX and R2 are not supported by AHU Builder exports.

Try the relevant demo at the screen sizes you expect to use. Dashboard templates and fixed equipment graphics have different layout behavior; a rendered PNG does not rearrange itself on a phone. Check text, navigation and control targets in the final station view at the actual device size.

Back up the station and test graphics, required modules, bindings, permissions and commands in a test environment before upgrading production. Contact support with a reproducible issue and the exact old and new Niagara versions. Update entitlement follows your product terms.

Use the styling controls documented for the selected product. Where a template exposes color tokens, edit those shared values; otherwise review the relevant PX widget or asset settings. A rendered image needs to be re-exported to change its embedded colors.

Editable Niagara PX elements can be configured in Workbench, subject to your product license. AHU Builder also saves an editable project for later changes and re-export. A PNG or GIF is a rendered asset, not editable application source code. Do not redistribute the purchased software or source assets as a competing product.

Graphics display point values and equipment states; they do not implement or commission your control sequence. Smart Build provides a configurable starting arrangement. Verify equipment order, sensor location, command/feedback bindings and all safeties against the approved project sequence before handover.

Copy the actual point ORD from Workbench in the target station. Preserve spelling, case and escaped characters. Resolve it in the station and compare the source value with the exported widget. A display label or browser URL is not a point ORD.

Verify the source point is available. Check the ORD, view context, account permissions and widget binding type. Test a known-good point to distinguish a binding issue from a display issue. A last-known value does not prove a healthy connection.

Preserve the exported folder structure and copy all referenced assets, not just the PX file. Compare each image ORD with the actual station file location, including case and filename. Reload and check the view with the intended operator account.

Back up the station, import to a separate location, verify images and bindings, and compare displayed values with their sources. Test navigation and allowed commands as the operator. Record the Niagara build, package version, tested role and unresolved exceptions.

Check the application error and balance after reconnecting. Record the version, time and export type before repeated retries. Send support the order reference and Install ID if the balance appears wrong. Do not send passwords or full license keys.

Include product/version, exact Niagara build, browser or Workbench environment, order reference, reproduction steps and error text. Redact sensitive customer data. Never include passwords, passkeys, payment details or license secrets.

No. Save the editable project explicitly before closing. A new session starts with a fresh workspace; use Load to reopen a saved build. A rendered image does not replace the editable project file.

STILL NEED A HAND?

Let’s get your project moving.

Send your product, order reference and Niagara version so we can help with the right details.

Keep passwords, payment information and full license keys out of support messages.
Contact support