Best Ignition Modules by Use Case: Third-Party Buyer's Guide
How to pick third-party Ignition modules: seven evaluation checks, the main options for MES, MQTT, charting, diagnostics, security, peripheral access and dev data, a charting comparison, and an 8.3 and 2027 upgrade checklist.

The best Ignition modules are the ones that close a specific gap in your gateway, pass a short due diligence check, and have a clear path to Ignition 8.3 and Ignition 2027. Pick by use case first: MES, MQTT and IIoT, Perspective charting, gateway diagnostics, security auditing, OS and peripheral access, and dev and test data mirroring. Then check every candidate for signing, version compatibility, support, licensing model, a free trial, SDK compliance and JVM impact before it gets anywhere near production.
We are Plantformance, a Swiss Inductive Automation Alliance Partner that works only on Ignition. We have used Ignition since 2013, Inductive Automation named us one of the four launch partners of its Alliance Partner Program in August 2023, and we also build five of the modules in this guide. That is a bias, so here is how we handled it: every other vendor is described only from its own official pages, there are no scores or rankings, and our modules appear only in the use cases where they genuinely fit. Where an Inductive Automation feature already does the job, we say so.
Quick picks, if you only need a starting point:
- MES on Ignition: start with the Sepasoft MES suite.
- MQTT and Sparkplug: start with the Cirrus Link MQTT modules.
- Perspective charts beyond the native palette: compare Embr Charts and Ultra Charts, and check the Ignition 2027 palette first.
- Gateway health in one view: Gateway Analyzer, on Ignition 8.3.2 or later.
- Security audit trails and privileged role monitoring: Security Auditor, alongside native audit profiles.
- Local files, serial ports, scanners and scales from Perspective: Host Agent.
- Live production data in a dev gateway with no write path back: Device Mirroring.
What counts as a third-party Ignition module
A module is a package that adds functionality to the Ignition Gateway: new components, drivers, scripting functions, tag providers or Gateway pages. Inductive Automation builds the core modules (Perspective, Vision, Tag Historian and so on). Everything else is third party, written against the Ignition SDK by vendors and integrators.
There are three places buyers usually look:
- Strategic Partner Modules. Inductive Automation's modules page describes a program that "enables third-party software providers to create modules for the Ignition platform." The Cirrus Link MQTT modules are listed there.
- The Third-Party Module Showcase. Inductive Automation's directory of modules built by outside developers.
- Ignition Exchange. Described by Inductive Automation as community-made Ignition resources. Most Exchange items are project resources rather than compiled modules, so treat them differently.
Inductive Automation is direct about responsibility. Its module installation documentation states that third-party modules are not produced by Inductive Automation and asks you to know who produced the code and perform due diligence. The rest of this guide is that due diligence, made practical.
How to evaluate a third-party Ignition module
We run the same seven checks on every module, including our own. They take an afternoon on a test gateway and save weeks of pain on a production one.
1. Signing
Ignition verifies module authenticity, and the installation docs note that module authors request signing certificates from Inductive Automation. You can see each module's certificate on the Platform, System, Modules page. A module can be quarantined if its certificate is unsigned or needs review, or if there is a licensing issue. You can still choose to trust a quarantined module, but that is a security decision, not a click. Ask the vendor how the module is signed and whether the signing status has changed between versions.
2. Version compatibility
Modules are built per Ignition platform version. Inductive Automation's docs note that a mismatch between the module version and the platform version leaves the module in a Faulted state. Look for a published compatibility table that names the exact Ignition versions and Java versions supported. Ignition 8.3 bundles Java 17, which Inductive Automation itself flags as something that may affect third-party module compatibility. A vendor that publishes this table, with dates, is a vendor that tests against it.
3. Support and maintenance
Find out who answers when the module breaks at 3 a.m. Is there a support policy, a service desk, a forum category, or only a GitHub issue tracker? Check the release history. A module with regular releases for 8.1, 8.3 and the 2027 beta tells you more than any sales page. Open source modules can be excellent, but plan who owns fixes if the maintainer is busy.
4. Licensing model
Third-party licensing varies widely: per gateway, per seat or connected host, per device count, subscription, or free and open source with an optional paid license. Inductive Automation's licensing docs note that a third-party author can issue a license key directly to a customer. Map the model to your architecture before you buy. A per-gateway license behaves very differently across a redundant pair, a dev, test and prod chain, or a fleet of edge gateways.
5. Trial
Ignition's own trial runs for two hours at a time and can be reset as often as you like. Most commercial modules follow the same pattern. Check whether the trial is feature complete or limited, because a limited trial can hide the exact behavior you need to test. Never evaluate on production.
6. SDK compliance
A module built with the public SDK and standard extension points (Gateway pages, tag providers, scripting namespaces, Perspective components) is easier to upgrade and easier to remove than one that reaches into internals. Ask what the module registers in the Gateway and what it leaves behind when disabled. Good vendor docs list every integration point.
7. JVM and client impact
Everything a Gateway module does runs inside the Gateway JVM, alongside your tags, scripts and sessions. Watch memory, CPU and thread counts on the test gateway with realistic load. For Perspective components, also watch the browser: client-side rendering moves load from the Gateway to each session's device, which matters on older panel PCs.
Figure 1. A seven-question check for any third-party Ignition module, in the order we run it.
Best Ignition modules by use case
Below are the options we see most often in real Ignition architectures, grouped by the problem they solve. Each description comes from the vendor's own published material. Inside each use case, we list native Ignition capability first where it exists, because the best module is sometimes no module.
MES
- Sepasoft MES suite. Built on Ignition, with modules for OEE Downtime, Track and Trace, SPC, Batch Procedure, Settings and Changeover, and an Enterprise Business Connector. Inductive Automation's modules page links Sepasoft for MES. Sepasoft describes its MES as scalable from a single site to a global enterprise, with unlimited licensing, tags and clients.
- Native Ignition plus custom projects. Some teams build lighter MES functions with standard Perspective, SQL and scripting. Plantformance does not sell an MES module; for MES projects we work with our partner Kanoa MES.
MQTT and IIoT
- Cirrus Link MQTT Engine. Subscribes to Sparkplug data and creates Ignition tags automatically from incoming payloads. Since version 4.0.23 it can also organize Sparkplug messages into a Unified Namespace style hierarchy.
- Cirrus Link MQTT Transmission. Publishes Ignition tag data as Sparkplug payloads to brokers, other gateways or cloud services.
- Cirrus Link MQTT Distributor. Runs an MQTT server inside Ignition. Cirrus Link lists up to 50 clients for Distributor and up to 250 for Distributor Plus. See the full Cirrus Link MQTT module lineup.
Charting for Perspective
- Native Perspective chart palette. In 8.3 it includes Time Series Chart, Power Chart, XY Chart, Pie Chart, Gauge, Simple Gauge and Chart Range Selector.
- Embr Charts (Musson Industrial). Free, MIT licensed Perspective components based on Chart.js and ApexCharts.
- Ultra Charts (Plantformance). Seven chart families, a Sankey chart and an Expert mode for custom D3 visualizations.
- NoteChart (Automation Professionals). Described by its maker as an enhancement to Ignition's client-side charting.
The charting deep dive below compares these in detail.
Gateway diagnostics
- Native Gateway status pages. Ignition's built-in status and diagnostics views are where every investigation starts.
- Gateway Analyzer (Plantformance). Collects databases, tags, scripts, sessions, alarms, redundancy and store-and-forward data into one health score with findings grouped by severity, plus JSON and CSV exports. It requires Ignition 8.3.2 or later.
- Kymera Pinger Driver. Exposes device reachability and last successful ping time as tags, useful for network health.
Security auditing
- Native audit profiles and security zones. Ignition records audit events to audit profiles, and 8.3 adds service security and security zone changes worth reviewing first.
- Security Auditor (Plantformance). Monitors client, Designer, Perspective and Gateway web sessions plus project changes, watches privileged roles, and can notify, end a session or remove a privileged role on a policy violation. It requires Ignition 8.3.0 or later with the Perspective and Event Stream modules.
OS and peripheral access
Perspective runs in a browser sandbox, which is why local files, serial ports, scanners and scales are a common gap.
- Host Agent (Plantformance). A Gateway module plus a host client that maps approved files, directories and serial ports into Gateway tags and a scripting namespace, with administrator approval of each host. Listed perpetual licenses are €500 for 1 seat, €1,500 for 5 and €3,500 unlimited per gateway.
- Kymera Socket Event Handler. Runs scripts when data arrives on a socket, with configurable incoming and outgoing packets.
- BarTender Drivers (Musson Industrial). Connects Ignition to BarTender servers from the Gateway so Vision and Perspective can trigger label prints through scripting.
Dev and test data mirroring
- Device Mirroring (Plantformance). Streams live OPC tag changes one way from a production gateway to an isolated dev gateway, where virtual devices with identical names receive the data. Supported on 8.1 and 8.3; Ignition Edge is not supported.
- Gateway Network, MQTT or OPC UA. Native or standards-based ways to share production data, each with different write-back and setup trade-offs.
- Programmable Device Simulator. Ignition's built-in simulator for synthetic data when live data is not required.
- Integration Toolkit (Automation Professionals). A free module, formerly called Simulation Aids.
Drivers, historians and utilities
- Automation Professionals. EtherNet/IP Communications Suite, Advanced Modbus and Time Series Database Cache modules.
- Embr (Musson Industrial). Open source SNMP drivers, Periscope design extensions, Thermodynamics functions and SSE streaming.
- Kymera Systems. SNMP driver, InfluxDB Historian, Twilio Notification, Map Panel, Office Document and an Alarm Rationalization module aimed at ISA 18.2.
- Sepasoft MES suite
- Native Ignition plus custom projects
- Cirrus Link MQTT Engine, Transmission, Distributor, Recorder
- Native Perspective chart palette
- Embr Charts (Musson Industrial)
- Ultra Charts (Plantformance)
- Native Gateway status pages
- Gateway Analyzer (Plantformance)
- Kymera Pinger Driver
- Native audit profiles and security zones
- Security Auditor (Plantformance)
- Host Agent (Plantformance)
- Kymera Socket Event Handler
- Musson Industrial BarTender drivers
- Device Mirroring (Plantformance)
- Gateway Network, MQTT or OPC UA
- Programmable Device Simulator
- Automation Professionals Integration Toolkit
- Automation Professionals EtherNet/IP and Modbus
- Embr SNMP, Periscope, Thermodynamics
- Kymera SNMP, InfluxDB Historian, Twilio
Figure 2. Use-case map of the Ignition modules covered in this guide. No scores: fit depends on your architecture.
Charting deep dive: native Perspective charts vs Embr Charts vs Ultra Charts
Charting is the category where buyers ask us the most questions, and where Ignition itself is changing fastest. Every description in this section comes from the option's own documentation.
Native Perspective charts
Ignition 8.3's chart palette includes the Time Series Chart, Power Chart, XY Chart, Pie Chart, Gauge, Simple Gauge and Chart Range Selector. For classic trending, the Power Chart and Time Series Chart cover most operator screens with no extra license and full Inductive Automation support.
Ignition 2027 expands this. In its Ignition 2027 announcement, Inductive Automation describes Perspective Chart Modernization as "a substantially expanded collection of 16 chart components," with improved line, area, bar and scatter charts and new radar and Sankey charts, plus Power Chart 1.5. The 2027.02 beta documentation adds a Radar component and new Pie Chart and Gauge variants. The announcement targets general availability for February 2027, and Ignition 8.3 remains supported as an LTS release through September 2030. Because 2027 was still in beta when we wrote this, check the final chart list in the 2027 release notes.
Embr Charts (Musson Industrial)
Embr Charts adds enhanced Perspective charting components built on Chart.js and ApexCharts. It is free and MIT licensed. Modules run in trial mode by default without limiting functionality; a perpetual, optional license removes the trial indicator and funds development. The Embr repository publishes release lines for Ignition 8.1, 8.3 and 2027. If your team is comfortable with Chart.js or ApexCharts configuration, Embr is a strong, low cost choice.
Ultra Charts (Plantformance)
Ultra Charts adds an Ultra Charts category to the Perspective Designer palette with seven chart families: bar and rectangular marks, line and area, points and text, rules and ticks, network and flow, density and contour, and geometric marks. It also includes a Sankey chart with node and link click events and an Expert mode component that runs project-authored D3 JavaScript. The product page lists 100+ templates, including heatmaps, ridgeline plots, candlesticks and contour plots. Version 1.0.x supports Ignition 8.1.35 or newer on Java 11; version 2.0.x supports 8.3.x on Java 17. Charts render in the browser, and the module keeps no separate data store: configuration lives in the Perspective project.
One point worth knowing before you buy: Expert mode executes browser-side code supplied by the project, so our documentation recommends restricting its authoring to trusted project developers and never binding its code to operator-entered values. That is the price of unlimited flexibility, and the same logic applies to any component that runs custom JavaScript.
What to test in a charting trial
Whichever option you shortlist, test it against your real data, not the demo data. In our experience, these five tests separate a good fit from a frustrating one:
- Data shape. Bind the chart to the dataset your query or tag history actually returns, including nulls and gaps.
- Volume. Load the largest time range an operator will realistically request and time the render on the slowest client.
- Interaction. Check that selection, zoom, brush or click events reach your Perspective scripts the way you expect.
- Theming. Confirm the chart follows your project's styles in light and dark themes.
- Ownership. Ask a second developer to change a chart they did not build. If they cannot, the maintenance cost is higher than the license.
How to choose
- Standard trends and operator screens: native Power Chart or Time Series Chart.
- Familiar Chart.js or ApexCharts charts, open source preferred: Embr Charts.
- Statistical, density, flow or network views, or fully custom D3 visuals: Ultra Charts.
- Heavy data sets on older clients: test any client-rendered option on your slowest panel first.
Do you still need a third-party chart module with Ignition 2027?
For many projects, no. If the 2027 palette covers the chart types on your screens, native charts are the simpler path: one vendor, one support line, one upgrade cycle. A third-party module still earns its place when you need chart types outside the native set, when you are staying on 8.1 or 8.3 for years (8.3 is supported through September 2030), or when developers want full control through code. Make the decision per chart type, not per project.
Upgrade compatibility checklist for Ignition 8.3 and 2027
Inductive Automation's 8.1 to 8.3 upgrade guide is explicit: because of major changes between 8.1 and 8.3, any third-party module must be checked for compatibility. Check the vendor's documentation and release notes for an explicit statement, and contact the vendor if there is none. Here is the checklist we use on customer gateways.
- Inventory. List every installed module with vendor, version and license type, on every gateway, including redundant backups and edge nodes.
- Get written compatibility. For each module, find the vendor's compatibility table for the target version. No statement means no upgrade yet.
- Check Java. Ignition 8.3 bundles Java 17. Modules built for older runtimes need the vendor's 8.3 build.
- Back up. Take a Gateway Backup before anything else, as Inductive Automation advises.
- Plan restarts. Hot swapping modules is no longer supported in 8.3, so installing or upgrading a module requires a Gateway restart.
- Upgrade dev or test first. Inductive Automation strongly advises upgrading development or test before production.
- Install target builds. Replace each module with the build made for the new platform version, then accept certificates and licenses and clear any quarantine.
- Check status. Every module should show Running. Investigate any Faulted module, and any Trial status where you expected Activated.
- Test real screens. Open the views, scripts and reports that depend on each module, with realistic data.
- Watch performance. Compare Gateway memory and CPU against your pre-upgrade baseline for at least one full shift.
- Plan for 2027. Ignition 2027 is a new major version: until each vendor publishes a 2027 compatibility statement, treat 2027 like any other major upgrade.
For our own modules, compatibility as published in the Plantformance documentation is:
- Ultra Charts: 1.0.x for Ignition 8.1.35+, 2.0.x for 8.3.x.
- Gateway Analyzer: Ignition 8.3.2+.
- Security Auditor: Ignition 8.3.0+.
- Device Mirroring: Ignition 8.1 or 8.3, including 8.1 to 8.3 and 8.3 to 8.3 pairs.
- Host Agent: Ignition 8.3; the host client runs on Windows and Linux.
- Ignition 2027: check each module's documentation for its support status before you upgrade.
- List every installed module with vendor and version
- Find a written compatibility statement for the target version
- Take a Gateway Backup
- Plan a restart window (no hot swapping in 8.3)
- Upgrade dev or test first
- Install the target-version build of each module
- Accept certificates and licenses, clear any quarantine
- Check every module shows Running, not Faulted or Trial
- Open the views and scripts that use each module
- Watch gateway memory and CPU for a full shift
- Upgrade production, then repeat the checks
Figure 3. Print this and tick it off per gateway. Based on Inductive Automation's 8.1 to 8.3 upgrade guidance.
Common mistakes when buying Ignition modules
Across the 110+ sites we manage, the module problems we see are rarely about the module itself. They are about how it was chosen and installed.
- Buying for one screen. A module bought to solve one view ends up on every gateway, licensed and upgraded forever. Ask whether the gap is worth that.
- Testing on production. Trial mode makes it tempting. A module that misbehaves under load does it in front of operators.
- No inventory. Nobody remembers who installed a module, which license key it uses or which views depend on it. The next upgrade turns into archaeology.
- Licensing one gateway in a chain. Dev, test, prod, redundant backups and edge nodes all need a plan, even if some of them run in trial.
- Ignoring the client. Perspective components render on the operator's device. A chart that flies on an engineering laptop can struggle on a ten-year-old panel PC.
- Overlapping modules. Two modules solving the same problem double the upgrade work. Pick one per use case and document why.
Questions to ask any Ignition module vendor
Send these before the trial ends. A vendor who answers them quickly and in writing is usually a vendor who will support you well.
- Which exact Ignition and Java versions does this build support, and where is that published?
- How is the module signed, and has that changed between versions?
- When will a build for the next Ignition version be available?
- How is it licensed across redundant pairs, dev and test gateways, and Ignition Edge?
- What does the trial limit, if anything?
- What does the module register in the Gateway, and what remains after it is disabled?
- What is the support channel, and what response time can we expect?
Where Plantformance modules fit, and where they do not
Our five Ignition modules solve problems we kept running into across many sites: Perspective cannot reach local hardware, gateway health is scattered across pages, security teams need audit trails and active responses, developers need real data without touching production, and some charts are beyond the native palette. All five offer a two-hour resettable trial with no feature limits except Gateway Analyzer, whose trial shows the health score and up to five findings.
They are not the answer for MES, MQTT infrastructure or protocol drivers, where the vendors above specialise. If you are mapping modules to a multi-site architecture, or want help running the checklist above on your gateways, talk to our engineers.
Frequently asked questions
What are the best third-party modules for Ignition?
It depends on the gap you are filling. Commonly used options include Sepasoft for MES, Cirrus Link for MQTT and Sparkplug, Embr Charts and Ultra Charts for Perspective charting, and Plantformance modules for gateway diagnostics, security auditing, OS and peripheral access, and dev and test data mirroring. Trial each one on a test gateway first.
What is the best charting module for Ignition Perspective?
Start with the native chart palette. If you need more, Embr Charts is free and open source and wraps Chart.js and ApexCharts. Ultra Charts adds seven chart families, a Sankey chart and an Expert mode for custom D3 code. The right pick depends on chart types, licensing preference and who maintains the views.
Do I still need a third-party chart module now that Ignition 2027 has native charts?
Maybe not. Inductive Automation says Ignition 2027 brings 16 chart components, including radar and Sankey, and the release was in public beta in November 2026. Check whether your required chart types are in the final 2027 palette. If they are, native is simpler. If not, a module still fills the gap.
Will my third-party Ignition modules still work after upgrading to 8.3 or 2027?
Not automatically. Inductive Automation says every third-party module must be checked for 8.3 compatibility, and modules are built per platform version. Get a written compatibility statement from each vendor, install the target-version build, upgrade a test gateway first, and confirm every module reports Running before you touch production.
How do I try an Ignition module before buying it?
Most commercial Ignition modules run in a trial mode. Ignition's trial runs for two hours and can be reset from the Gateway as often as you like. Plantformance modules follow that model, with no feature limits except Gateway Analyzer, whose trial shows the health score and up to five findings.
Talk to a Plantformance Ignition engineer
Tell us about your Ignition setup and we will point you to the right module or managed service for your plants.