alternatives

Sutrace as an Ignition SCADA alternative — honest comparison

A direct comparison between Inductive Automation Ignition and Sutrace for plants that want unified observability without per-tag pricing or a Java client. Honest about where Ignition still wins.

TL;DR

Ignition is excellent SCADA. It has 20+ years of plant-floor mileage, a vibrant integrator community, and one of the few honest no-per-tag pricing pages in the industry. If your job is "draw a screen with 4,000 tags from a stack of Allen-Bradley PLCs and put it on a panel PC bolted to a press," Ignition wins, and we won't pretend otherwise.

Sutrace is for a different job: unifying the SCADA view with software infra, web/APIs, and AI agents in one EU-residency dashboard, so a 5–100-person plant doesn't need three tools and two consultants to know whether the line is up. We speak Modbus TCP, OPC UA, MQTT Sparkplug B, EtherNet/IP, BACnet, and the OTel/Prom side too. No per-tag pricing. No Java desktop client. No $50k integrator project to start.

Most teams who land on Sutrace asked the question that's been on the Inductive Automation forum since 2018: "Better than Ignition. Any SCADA?" The honest answer is "depends what you're using SCADA for." This page is that conversation.

The forum thread that started it

The Inductive Automation forum thread is unusual because it's hosted by Inductive Automation and the answers are still all over the place. Wonderware/AVEVA, Ignition itself, GE iFix, Citect, FactoryTalk View — every replier has a different favorite based on what they last shipped. The thread has stayed alive for years because no answer is universally correct.

What the thread actually reveals: SCADA buyers are evaluating against a moving target. The 2018 question was "which HMI runtime do I license per machine?" The 2026 question is closer to "how do I see the plant, the cloud, and the LLM agent in one place without replatforming?" That's not a SCADA question anymore. That's an observability question that happens to include a PLC.

Where Ignition still wins (we mean this)

We're a small EU-based team. We're not going to ship more screen widgets than Inductive Automation in the next 24 months. If your project is one of these, buy Ignition, finish your project, and come back when the next one is more cross-domain.

Job	Why Ignition wins
Greenfield SCADA for a single plant with 1,000+ tags and panel HMI	Designer + Vision/Perspective is genuinely the best tool for this job. Maker is free for hobbyists; Unlimited is one license per server, not per tag.
Bottom-up alarm management with shelving, acknowledgement chains, runtime workflow	Ignition's alarm pipeline is mature. We're 18 months behind.
Integrator-led project where the customer wants to hire a regional Gold partner	The Ignition integrator network is large and battle-tested. Ours is "email me."
Vision panel HMIs on legacy hardware	Vision (Java) still works on hardware no other vendor will touch.
Custom Perspective views with 50+ screens	Perspective view scripting (Python via Jython) is a real superpower if you have a developer.

If three or more of those rows describe your project, close this tab. We mean it.

Where Sutrace wins

The reverse case — when Sutrace is the better answer — is when your problem isn't the screen. It's the stack.

You already have an OTel/Prometheus pipeline for software, and the OT side is currently invisible to it.
You want one dashboard for plant floor + APIs + AI agents, not three.
You don't want to install a Java client to look at a tag.
You're a 5–100-person operation and a $25k+ Ignition Unlimited deployment plus an integrator is more SCADA than you need.
You're EU-resident and need data to stay in the EU by default, with a signed DPA on day one.
You want to start from a reading on a single Modbus register or OPC UA node and grow from there — without re-platforming when you add an MQTT broker or a Cloudflare uptime check.
You want pricing you can read in 60 seconds. (See /pricing.)

Protocol matrix

Protocol	Ignition	Sutrace
Modbus TCP/RTU	✅ Built-in driver	✅ Built-in
OPC UA (client + server)	✅ Native, mature	✅ Native client (Basic256Sha256, Sign+Encrypt)
MQTT Sparkplug B	⚠ Cirrus Link module (separately licensed)	✅ Native
EtherNet/IP (Allen-Bradley)	✅ Built-in	✅ Built-in (read-only by default)
BACnet/IP	⚠ Add-on module	✅ Built-in
Siemens S7	⚠ Add-on module	✅ Built-in
OTel traces / metrics	❌	✅ Native ingest
Prometheus scrape	❌	✅ Native ingest
HTTP uptime / status pages	❌	✅ Native
AI agent traces (Anthropic / OpenAI)	❌	✅ Native

The shape is the point. Ignition is the best SCADA. Sutrace covers SCADA-shaped data plus the rest of the modern stack.

Pricing

Ignition is honest about not charging per tag — that's why integrators love it. Unlimited is one server license; Maker is free for personal use. Modules (Sparkplug, mobile, vision panel etc.) are separate.

Sutrace is also honest about not charging per tag. We don't have an "Unlimited" tier because there is no other tier. One price, all protocols. See /pricing.

Migration: how teams actually move

Most "migrations" aren't migrations — they're co-existence. A typical pattern:

Keep Ignition where it works (panel HMI, the alarm runtime, the operator screens).
Point Sutrace at the same OPC UA server (most plants already have one, often via Ignition's own OPC UA module or KEPServerEX).
Sutrace gets read-only views of the same tags Ignition is showing the operator.
Sutrace adds the things Ignition doesn't have: OTel from the MES, Prometheus from the cloud, Cloudflare status, agent traces.
Now the plant manager sees "press 4 down + ERP API timing out + agent retrying" on one screen.

You don't rip out Ignition. You stop pretending Ignition is the whole story.

For more on phased modernization see our retrofit-vs-rip-and-replace post, which leans on the E Tech Group guidance on minimal-disruption upgrades and the Live Automation retrofit playbook.

FAQ

Can Sutrace replace Ignition Vision/Perspective for HMI?

No. We don't ship a screen designer and we're not planning to. If you need a runtime HMI with operator workflow, keep Ignition (or use FlowFuse Node-RED — see their HMI guide for an open option). Sutrace is observability, not HMI runtime.

Does Sutrace charge per tag?

No. Per-tag pricing is the buyer-search filter that almost every SCADA vendor still fails — see Tatsoft's top-8 SCADA roundup and our no-per-tag-pricing post.

Where does my data live?

EU. Frankfurt-region by default for all Sutrace tenants. Signed DPA on day one. No US data path unless you opt in.

Can I keep my OPC UA server (Ignition or KEPServerEX) and just point Sutrace at it?

Yes. Sutrace is an OPC UA client; we connect to whatever you already have, including Ignition's own OPC UA Module.

What about Sparkplug B?

Native. Birth/death certificates, namespace conventions, MQTT broker integration. See our Sparkplug B explainer.

Is there an integrator network?

Not yet. We're 18 months in. If you need a Gold partner with 50 ex-Rockwell engineers, Ignition wins this round.

Does Sutrace work air-gapped?

Edge agent + offline buffer; sync resumes when the network returns. Full air-gap requires our self-hosted bundle — talk to us. Most plants we serve are not air-gapped.

Can I import my Ignition tag database?

We can import an OPC UA browse tree, which is the same shape as most Ignition tag providers. We do not import Designer projects directly — those stay in Ignition.

What's the alarming story?

Threshold + rate-of-change + window-based + flat-line detection on any tag, plus the same primitives on OTel/Prom signals. Routes to PagerDuty, Slack, email, webhook. Ignition's runtime alarm pipeline (shelving, ack chains, multi-pipeline routing) is more mature; ours is simpler and faster to set up.

Can I run Sutrace alongside Ignition for a 90-day trial?

Yes. That's the recommended path. We'll send you a deploy script that connects to your existing OPC UA endpoint read-only. If after 90 days Ignition is still the better answer, you've lost nothing.

What does the edge agent actually look like?

A small Linux process — runs on a Raspberry Pi 4, a NUC, or a VM. ~200 MB RAM idle, single TLS outbound connection to the EU cloud, no inbound ports. Configured via a single YAML file that lists the OPC UA endpoints, Modbus units, MQTT brokers, and EtherNet/IP CIP targets to read. Buffers locally if the WAN drops; resumes on reconnect.