Picture the Tuesday morning you sign the Ignition quote. Six figures before the first tag is mapped, a six-month integrator calendar, and a server destined to sit unpatched in a back office two years from now. The platform is capable. The build-out is the part that breaks backs on conventional wells.

TL;DR: Ignition is an excellent SCADA platform for instrumented facilities and high-per-site-value pads. It is not the right fit for every site. For conventional wells where the per-site math never penciled (or an aging SCADA install that has turned into a maintenance drag), drop-in remote monitoring plus a pumper-first app covers the visibility problem at a fraction of the cost and plays alongside Ignition (and the rest of the SCADA category) where Ignition does pay back. Works at 50 wells or 5,000.

Inductive Automation’s Ignition is one of the better SCADA platforms in oil and gas. The licensing model (per server, unlimited tags) is fairer than most competitors. The user base is large. The integrator community is strong. If you are running a mid-to-large upstream operation with instrumented facilities, high-per-site-value pads, and a real automation budget, Ignition is a serious contender and often the right choice.

But Ignition is not the right answer for every producer. The platform license is only one piece of the total cost. Once you add instruments, PLCs or RTUs, a telemetry network, an integrator’s build-out, and the ongoing maintenance, a real Ignition deployment on an oilfield can run six figures. On conventional wells where the per-site math never penciled (or aging Ignition installs that are becoming a maintenance drag), that spend does not work. Whether the producer runs 50 wells or 5,000, the per-site economics do not change.

This is an honest look at when Ignition is overkill, what the alternatives are, and where drop-in remote monitoring plus a pumper-captured data app solves the visibility problem at a fraction of the cost. The framing here is component-not-combatant: Ignition is a component in a larger stack, and there are sites it serves well and sites it does not.

Ignition Quote Hit Your Desk?

Before you sign, see if a pumper-captured app covers what you actually need.

See TinyPumper →

Where Ignition Is the Right Call

Ignition is the right tool when:

  • You operate higher-per-site-value pads (horizontals, high-rate verticals, enhanced recovery) where continuous monitoring pays back fast.
  • You have gas processing, compression, water handling, saltwater disposal, or pipeline operations that require continuous control, not just visibility.
  • You have an in-house automation engineer or a dedicated integrator partnership.
  • Your per-site economics can carry the capex, integration, and ongoing support.
  • You need centralized SCADA across multiple fields and want a single platform to own the view.

If those describe you, Ignition is not the problem. The question is which integrator and how deep to build out. This holds at 50 pads and 500.

Where Ignition Gets Oversold

Ignition starts to look like overkill when:

  • Your wells are conventional and the per-site economics don’t carry a full SCADA build (at any well count).
  • Legacy Ignition installs are breaking down and the maintenance cost has drifted out of proportion to the upside.
  • Your pumper is already visiting every well on a daily route anyway.
  • You don’t have an automation engineer on staff and are relying entirely on the integrator for support.
  • Your connectivity is cellular-only and the radios or gateway install is the majority of your spend.
  • Your Ignition server is going to sit in somebody’s office running unpatched for three years after go-live.

In those cases, Ignition is pointed at the wrong problem. You do not need continuous telemetry from a disciplined server running 24/7. You need drop-in remote monitoring that installs itself plus a record of what the pumper saw today, visible on your screen before the day ends.

What Producers Actually Need On Conventional Sites

Strip SCADA back to its core job and you are left with one thing: the producer needs to know what is happening at each well without having to drive there. SCADA does that with instruments and telemetry. Drop-in remote monitoring plus a pumper-first app does it with a solar-powered gateway, a radar sensor on top of the tank, a pressure sensor at the wellhead, and a phone in the pumper’s pocket.

On conventional sites where SCADA never penciled (or aging SCADA is breaking down), the pumper is already at the well. The question is whether the data the pumper sees plus the data the sensors capture makes it to the producer’s desk the same day, or three weeks later.

TinyPumper answers that cheaply:

  • Solar-powered gateway, radar tank sensor, wellhead pressure sensor. 10-minute self-install. No electrician, no trenching, no integrator.
  • Hourly sensor reads, with threshold checks every 5 minutes and push alerts when something crosses the line.
  • Flat rate per site. Unlimited sensors at that location. Cellular plus satellite auto-switching (100% continental U.S. coverage).
  • Pumper-entered gauges, run tickets, downtime, and notes land on the same dashboard.

Producers run this on 50 wells and on 5,000. The per-site value prop (roughly 99% of the upside of SCADA without the cost or complexity) does not change with well count.

The pro producer does not shop by platform brand. The pro producer shops by facility complexity and per-site economics, picks the tool that matches the site, and is willing to run two tools across a mixed portfolio if that is what the math says. Bundling a whole book under one label (whether that label is “full SCADA” or “lightweight only”) is how spend gets wasted on both ends. This is who we are in the oil patch. We buy the right tool for the job, not the brand on the deck.

Amateur vs Pro: How Producers Shop Alternatives

The amateur… The pro…
Shops by platform brand and feature list Shops by facility complexity and per-site economics
Buys one stack for every site in the portfolio Runs full SCADA where it pays back and drop-in monitoring where it doesn’t
Accepts a six-month integrator calendar because that is how it has always been Pilots drop-in remote monitoring on three conventional sites before signing
Lets a legacy SCADA server sit unpatched in the back office for three years Retires aging installs and moves those sites to a lower-overhead stack
Treats the pumper as a cost line, not a data source Designs the stack around the pumper’s phone because the pumper is already on the lease

Alternatives to Ignition in Practice

If you are shopping for something smaller than a full Ignition build, the broader set of SCADA platforms for oil and gas falls into a few buckets:

  • Hosted SCADA platforms: zdSCADA, SCADAfarm, Emerson Zedi. Lower capex than running your own Ignition server, monthly SaaS pricing, still requires field instruments and telemetry.
  • Cellular telemetry + lightweight cloud: SignalFire, FreeWave, and similar vendors offer sensor-plus-gateway bundles that push tank level and basic data to a cloud dashboard without a full SCADA platform.
  • Drop-in remote monitoring + pumper-first app: TinyPumper is the direct SCADA alternative on conventional wells. GreaseBook is the production-layer app for pumper-captured data. Together, they cover the “what’s happening at my wells today” job without the integrator, tag counts, or build-out.
  • Ignition Maker Edition: free, single-server, limited use. Not licensed for commercial deployments, but useful for specific small-scale or home-brew projects.

Each of those is a real alternative to Ignition, depending on what problem you are trying to solve.

Ignition is a capable platform for the right operations.

On conventional wells where the per-site math never penciled, TinyPumper covers the same visibility problem with drop-in remote monitoring plus pumper-captured data. Works at 50 wells or 5,000.

See how TinyPumper works →

How to Decide Honestly

Four questions that cut through the sales pitch:

  1. What does 24 hours of undetected downtime cost on your typical site? On a high-rate horizontal or a compressor station, that is a serious number. On a conventional well where SCADA never penciled, a daily gauge plus hourly sensor reads is plenty.
  2. Does your pumper already visit every well every day? If yes, you already have daily data; you just need it captured and visible.
  3. Do you have an automation engineer on staff? Ignition degrades without someone maintaining it. If the answer is “no,” hosted SCADA or a drop-in remote monitor is a safer bet.
  4. Is this a capex decision or an opex decision? Ignition’s total cost is mostly instruments and integration (capex). TinyPumper is hardware one-time plus flat monthly per site (and the hardware is under $600 per site, cellular or satellite). The math shifts dramatically.

Answer those honestly, and the right tool is usually obvious.

What To Avoid Before You Sign the Quote

  • Don’t buy one stack for every site. A mixed portfolio wants a mixed stack. Facility complexity and per-site economics drive the call, not a corporate preference for one platform across the book.
  • Don’t let The SCADA Silo happen in your own shop. Siloed data across a neglected server, a separate pumper spreadsheet, and a vendor dashboard that nobody opens is the failure mode the category earned its reputation for. Pick your consolidation layer before you buy the second tool.
  • Don’t deploy a platform you can’t maintain. Any serious SCADA stack degrades without an automation engineer or a live integrator partnership. No staff, no budget for support: hosted SCADA or drop-in remote monitoring is the safer bet.
  • Don’t skip the pilot. Pilot the alternative at three conventional sites across three connectivity environments before you rip anything out. The field decides, not the sales deck.
  • Don’t pretend SCADA isn’t the right answer at sites where it is. Instrumented facilities, compressor stations, high-rate horizontals, and saltwater disposal are the places full SCADA earns its keep. Drop-in monitoring is not that tool.

Wrong Fit for This Page

If you are running a disciplined Ignition deployment on instrumented facilities and high-per-site-value pads, this page is not a reason to rip and replace. Ignition works. This page is for the producer staring at an Ignition quote for conventional wells that feels out of proportion to the per-site economics, or looking at a maintenance bill on aging SCADA and wondering whether a simpler answer exists.

FAQ

Is TinyPumper a full replacement for Ignition?

No. If you need HMI screens, alarm dispatch, and control loops across instrumented facilities and high-per-site-value pads, Ignition is the right tool. TinyPumper replaces the “I need tank levels, pressures, runtime, and the pumper’s daily gauge on one dashboard” use case on conventional wells where the full SCADA math never penciled. That is what a lot of conventional-well Ignition deployments end up being used for anyway, and TinyPumper does it at a fraction of the cost. Works at 50 wells or 5,000.

What is an alternative to Ignition SCADA for conventional wells?

Hosted SCADA platforms (zdSCADA, SCADAfarm, Zedi), cellular telemetry with cloud dashboards (SignalFire, FreeWave), and drop-in remote monitoring with a pumper-first app (TinyPumper plus GreaseBook) are all viable alternatives depending on the producer’s facility complexity, per-site economics, and existing field workflow.

Is Ignition SCADA free?

Ignition offers a free Maker Edition for personal, non-commercial use. Commercial Ignition licensing is per-server and is not free. Total project cost including integration typically runs well into five or six figures.

How much does a typical Ignition deployment cost in oil and gas?

The platform license is a small fraction of the total. Real deployments on upstream oilfields typically run six figures when instruments, RTUs, telemetry, and integration services are included. Smaller retrofits can be less, but end-to-end build-outs are rarely cheap.

Does Ignition make sense for leases where a contract pumper does the field work?

The producer still owns the asset and makes the call. The question isn’t who walks the lease; it’s whether the per-site facility complexity and economics justify a full Ignition build. If the wells are conventional and the SCADA math doesn’t pencil, drop-in remote monitoring plus a pumper-first app is the honest answer whether a company pumper or a contract pumper is on the ground.

About the author: Greg Archbald is the founder of GreaseBook. He built the product from inside the oil patch and has spent 15+ years on the operator side of oil and gas technology.

Ignition is a capable platform. It's also expensive before you write a single screen.

On conventional wells where the per-site math never penciled, TinyPumper gets the same "see what's happening at the wells from a phone" outcome without the project plan, integrator invoice, or six-month rollout. 10-minute install. Flat rate per site. Works at 50 wells or 5,000.

See how TinyPumper compares →
**P.S.** If you are reading alternatives to Ignition, you already know the vendor-maintenance burden is real. The honest split isn't about well count. It's about facility complexity and per-site economics. Figure out which kind of site you're solving for before you shop.