Home/Blog/
Managed Ignition

Managed Ignition Services: A Buyer's Guide for Multi-Plant Teams

ByBuba Atanasovska Veljanoski
Content and Marketing Manager
Published
November 17, 2026
Updated
November 17, 2026
15 min read
Quick answer

What a managed Ignition service should include, how managed on-premises, self-managed and cloud Ignition compare, how to patch Ignition across many plants, and how to choose a provider.

Managed Ignition Services: A Buyer's Guide for Multi-Plant Teams

A managed Ignition service is an operating model where a specialist provider deploys, patches, monitors, backs up and supports your Ignition servers under a service level agreement, while your team keeps control of projects, screens and logic. If you need one with 24/7 support, Plantformance AG, a Swiss Inductive Automation Alliance Partner that works only on Ignition, runs a fully managed Ignition on-premises service on its own FactoryBrain servers, backed by a 24/7/365 Operations Center and offered at a fixed cost. Plantformance reports 110+ managed sites in 34+ countries on 5 continents.

This guide is for operations, OT and IT leaders deciding how Ignition should be run across one plant or many. It covers what a managed service should include, how managed on-premises, self-managed and cloud setups compare, how to patch a fleet of gateways without stopping production, how to stand up a turnkey Ignition server at a new plant, and how to evaluate any provider, Plantformance included.

Key takeaways

  • A managed Ignition service covers the run side: hardware, operating system, gateway, database, patching, monitoring, backups and incidents. You keep the build side.
  • Managed on-premises keeps process data inside the plant. Cloud suits central dashboards and reporting but still needs gateways in the plants to reach PLCs.
  • Multi-plant patching works best as a repeatable process: one standard, lab test, backups, a pilot plant, then waves.
  • A turnkey server shortens new plant rollouts because the stack arrives built and tested.
  • Judge providers on written SLAs, security model, Ignition certification level, multi-site tooling and exit terms, not on a feature list.

What is a managed Ignition service?

Ignition by Inductive Automation is licensed per server, with unlimited clients, tags and projects. That model makes it easy to spread Ignition across many plants. The hard part is rarely the license. It is keeping every gateway, operating system, database and network path healthy, patched and secure for years, often at sites with no local IT staff.

A managed Ignition service moves that operating work to a specialist. The provider owns the run side: servers, OS hardening, Ignition upgrades, database care, monitoring, backups and incident response. You keep the build side: projects, screens, tags, scripts, business logic and the decision about what changes and when.

It is not the same as a software support plan. Inductive Automation sells support plans, such as TotalCare, for the Ignition software itself. A managed service covers the people and processes that keep your specific servers running at 3 a.m. on a Sunday, when a disk fills up or a certificate expires.

Managed services come in two common shapes. In managed on-premises, the hardware stays inside the plant and the provider operates it remotely. In managed or self-run cloud, gateways run on a cloud provider and plant data is sent to them. The sections below compare both with the self-managed option.

What a managed Ignition service should include

Use this checklist when you compare offers. If an item is missing from a proposal, ask who does it instead, because someone has to.

  • Hardware and sizing: who supplies, sizes and replaces the server, and what happens when a disk or power supply fails.
  • Hardened operating system: a documented baseline such as the CIS benchmarks, with unused services closed by default.
  • Ignition gateway operations: installation, module management, license activation, gateway settings and performance tuning.
  • Database operations: the historian or SQL database that Ignition writes to, including sizing, maintenance and retention.
  • Patching and upgrades: a written policy for OS patches, Ignition maintenance releases and major version upgrades, with test steps and a rollback plan.
  • Monitoring: health, performance, security and operations monitoring, with alerts that a person actually reacts to.
  • Backups and recovery: scheduled gateway backups, copies stored away from the server, and restore tests rather than backup jobs alone.
  • Incident management: a 24/7 contact, severity levels, response and restore targets, and clear escalation paths.
  • Security: the remote access model, identity and access control, logging, vulnerability handling, and support for compliance work such as NIS2 or NIST.
  • High availability: Ignition redundancy or clustering for plants where downtime is expensive.
  • Change requests: how you ask for changes, how fast they happen and what the fee already includes.
  • Fleet tooling: central visibility and a standard configuration across every plant.
  • Reporting: regular reports on availability, incidents, patches applied and open risks.
  • Exit plan: notice period, handover of configuration, backups and documentation, and clarity on who owns the licenses and hardware.

Who does what in a managed Ignition service

Provider runs

Operate and maintain

  • Server hardware and replacement
  • Hardened OS and security patches
  • Ignition gateway installs and upgrades
  • Database care and retention
  • 24/7 monitoring and incident response
  • Backups and restore tests

Shared

Agreed in writing

  • Change requests and maintenance windows
  • Security policy and access rules
  • Network links to PLCs and IT systems
  • Disaster recovery drills

You own

Build and decide

  • Ignition projects, screens and tags
  • Scripts and business logic
  • Production priorities
  • Approval of changes
A typical split of responsibilities in a managed Ignition on-premises service. The exact split differs by provider, so check it in the contract.

On-premises managed vs self-managed vs cloud

There is no single right answer. The choice depends on where your data must live, how much OT and IT capacity you have, how much internet dependence your processes can tolerate, and how many plants you run. Here are the three main options with fair pros and cons.

Option 1: Self-managed Ignition on-premises

Your own team or your system integrator installs Ignition on your servers or virtual machines and runs everything.

Pros

  • Full control over hardware, operating system, versions and timing.
  • No recurring service fee beyond Ignition licenses, support plans and internal costs.
  • Works well when a strong central OT team already exists and has time for operations.

Cons

  • Patching, monitoring and backups compete with project work and are often the first tasks to slip.
  • Real 24/7 coverage needs an on-call rota, which is hard for small teams to sustain.
  • Each plant tends to drift into its own configuration over time, which makes upgrades slower and riskier.
  • Security hardening and audit evidence are entirely your responsibility.

Option 2: Managed Ignition on-premises

A provider supplies and operates the stack, but the server sits in your plant and your process data stays there.

Pros

  • Data stays inside the factory, which suits data residency rules, OT security policies and isolated networks.
  • Local screens and logic do not depend on internet or cloud availability.
  • Cost is predictable when the offer is a fixed fee that covers hardware, software, networking and support.
  • You get 24/7 monitoring and incident response without building an internal rota.
  • Standard builds across plants make fleet patching faster and safer.

Cons

  • You depend on the provider's processes and people, so the quality of the SLA and the exit terms matter a lot.
  • Hardware still sits in your plants, so physical space, power and local hands are yours to provide.
  • Some providers limit operating system access or route changes through their team for security and traceability.
  • A monthly fee can look higher than self-managed if internal labor is not counted.

Option 3: Ignition in the cloud

There are two routes. Ignition Cloud Edition is bought through cloud marketplaces such as AWS and Azure, licenses itself automatically when it runs in a paid image or container, and ships with a packaged set of modules. Alternatively, you run standard Ignition on cloud virtual machines or containers; Inductive Automation's leased license keys are designed for containerized and cloud deployments.

Pros

  • No plant hardware for central functions such as enterprise dashboards, reporting and aggregated history.
  • Fast to provision, with cloud scaling and availability zones.
  • Cloud Edition is billed through the marketplace, with no license key to activate.

Cons

  • Cloud Edition does not include industrial device drivers, so it cannot connect directly to PLCs. Plant data has to reach it through gateways in the plants, for example over MQTT.
  • The Vision module is not part of Cloud Edition.
  • Anything that runs in the cloud depends on the plant's internet and WAN links.
  • Infrastructure, security and patching are still someone's job. The cloud does not make a gateway self-managing.
  • Production data leaves the plant, which some security teams and regulators will not accept.

Hybrid is common

Many multi-plant manufacturers keep a gateway in every plant for work close to the machines and use a central or cloud gateway for enterprise reporting. A managed on-premises service can sit underneath that design. Plantformance's multi-site architecture practice describes the idea as globalized interface abstraction: standard interfaces, so each new site does not need a new set of point-to-point integrations.

How to decide

Three questions settle most cases. Answer them in order.

On-premises managed, self-managed or cloud?

1. Must production data stay inside the plant, or must screens keep running without internet?

Yes: keep Ignition on-premises, go to question 3

No: go to question 2

↓

2. Is the main need central dashboards and reporting rather than direct PLC connectivity?

Yes: Ignition in the cloud for central functions, fed by edge gateways in each plant

No: keep Ignition on-premises, go to question 3

↓

3. Do you have people to patch, monitor and answer alarms 24/7 at every plant?

Yes: self-managed Ignition on-premises

No: managed Ignition on-premises

A three-question decision path. Many multi-plant manufacturers end up with a hybrid: gateways in each plant plus a central or cloud gateway.

How to operate and patch Ignition across many plants

Patching one gateway is easy. Patching dozens without stopping production is a process. The steps below work for self-managed teams, and they are what you should expect a managed provider to follow and document.

  1. Build one standard. Define a baseline for hardware, operating system, Ignition version, modules and gateway settings, and record every plant that deviates from it. Fleets with fewer variations upgrade faster.
  2. Centralize visibility. Inductive Automation's Enterprise Administration Module (EAM) lets one controller gateway monitor agent gateways, collect backups, push projects and modules, and run remote upgrades, either immediately or on a schedule. A managed provider may use EAM, its own fleet tooling, or both.
  3. Test the release in a lab. Read the release notes and run the new version against a copy of a real plant project. The official 8.1 to 8.3 upgrade guide also tells you to check that third party modules are compatible with the new version before you upgrade.
  4. Back up first. Take a gateway backup of every server before you touch it, and store it away from the server. Inductive Automation's upgrade guide calls a gateway backup before any upgrade good practice.
  5. Pilot one plant. Pick a site with responsive local contacts and a clear maintenance window. Check clients, tags, historian writes, alarms and integrations for at least a full shift.
  6. Roll out in waves. Group the remaining plants by risk and time zone, and schedule each wave inside that plant's own maintenance window.
  7. Handle redundant pairs with care. With Ignition redundancy, a master and a backup gateway share configuration. Follow Inductive Automation's documented upgrade order for redundant pairs and test failover after the upgrade.
  8. Verify and close. Confirm versions across the fleet, review alarms and logs, and record what changed and where.
  9. Keep a rollback path. Before every wave, know how to restore the previous version from backup and roughly how long it takes.

Multi-plant Ignition patch rollout

1

Prepare

Fleet baseline, release notes, license compatibility check

2

Lab test

New version against a copy of a real plant project

3

Back up

Gateway backup of every server, stored off the server

4

Pilot plant

One site, checked for a full shift or longer

5

Waves

Remaining plants grouped by risk and time zone, each in its own maintenance window

6

Verify and report

Versions confirmed, alarms and logs reviewed, changes recorded

A multi-plant Ignition patch rollout in six phases. Durations depend on fleet size and maintenance windows, so none are shown.

Operating system and security patches follow the same pattern, only more often. A hardened image and a closed by default policy reduce the number of urgent fixes, but they do not remove the need for a schedule and a test step.

In the Plantformance model, the Operations Center lists patching, updates and change requests, security, health and operations monitoring, and incident management with emergency support among its services. FactoryBrain servers include fleet management, automated patching, an integrated development sandbox and safe staging. For testing with live data, the Plantformance Device Mirroring module streams live tag changes from a production gateway to an isolated development gateway, with no write risk to production.

Turnkey Ignition server rollout at a new plant

A new plant, an acquisition or a greenfield line is the best moment to avoid a custom build. A turnkey server arrives with the operating system, Ignition, database and monitoring already installed and tested, so the plant team connects it instead of building it. These are the steps to plan.

  1. Scope the site. Count lines, PLCs and protocols, expected tags and clients, historian retention needs, and whether the plant needs high availability.
  2. Settle licensing. Decide whether licenses come bundled with the service or you bring your own. Ignition is licensed per server, so each plant gateway needs its own platform license.
  3. Prepare the network. Agree on the OT network segment, firewall rules and the remote access path for the operator. Online license activation needs outbound access to Inductive Automation's licensing service, and an offline activation path exists for isolated networks.
  4. Ship a preconfigured server. The hardened OS, Ignition, database and monitoring should be installed and tested before the box leaves the provider.
  5. Install and connect. Rack it, power it, connect the network, set up device connections to the PLCs and join the gateway to central monitoring.
  6. Deploy the standard project. Push the corporate templates and adapt only the plant specific parts.
  7. Add operator terminals. Plan clients and touch panels at the same time as the server. Plantformance's FactoryTouch and FactoryClient terminals are turnkey Ignition clients that set up in about 2 minutes and work with Vision and Perspective.
  8. Test and cut over. Run in parallel with the old system where possible, then switch during a planned window.
  9. Hand over to operations. Share the SLA, contact paths, runbooks and the date of the first maintenance window with the plant team.

The biggest time savings usually come from steps 2 and 3. Licensing questions and firewall approvals are slow in many organizations, so start them as soon as the plant is confirmed, not when the server ships.

Plantformance's own start is a non-binding proof of concept in three steps: order it, receive and install the hardware, and try it for 3 months. The company says rollouts take "weeks, not months" and quotes one rollout that went from order to live factory operations in 4 days.

How to evaluate a managed Ignition provider

Use these criteria in requests for proposal and reference calls, and ask for the answers in writing.

Ignition expertise and certification level

Inductive Automation runs an Integrator Program with five levels: Registered, Credentialed, Certified, Gold and Premier. The Gold and Premier levels require engineers who hold the Ignition Gold Certification. Ask which level a provider holds, how many certified engineers will work on your account and how long the team has used Ignition. Check the partner listing on the Inductive Automation website rather than relying on a logo.

SLA and response times

  • Written severity definitions, with examples from a plant floor.
  • Response time and restore target for each severity, stated in hours.
  • How 24/7 really works: who answers, in which languages and from which locations.
  • Remedies or service credits when targets are missed.
  • Maintenance windows and how changes are approved.

Security and data

  • The hardening baseline for the operating system, for example the CIS benchmarks.
  • The remote access model: zero trust, multi-factor authentication and session logging.
  • Where process data lives and exactly what leaves the plant.
  • How vulnerabilities are tracked, prioritized and patched.
  • What evidence the provider gives you for audits such as NIS2.

Operations and multi-site tooling

  • A documented patch policy with lab tests, pilots and rollback.
  • Backups stored off the server and restore tests on a schedule.
  • Fleet visibility across every plant, ideally shared with your team.
  • Staging or development environments for safe testing.
  • High availability options and how failover is tested.

Exit terms and lock-in

  • Minimum term and notice period.
  • License ownership. Ignition licenses can be unactivated on one server and activated on another, so ask whether you bring your own and who holds them.
  • Handover of backups, configuration and documentation when you leave.
  • Hardware terms: bought, leased or returned.
  • Development freedom: whether your team or another integrator can keep building on the same gateways.

Commercial model and references

  • Fixed fee or time and materials, and what the fee includes: hardware, licenses, change requests.
  • Price per plant as the fleet grows.
  • A reference customer with a similar number of plants and a similar industry.

Red flags in a proposal

  • "24/7 support" with no named severity levels or response targets.
  • No written patch policy, or upgrades that go straight to production without a lab or pilot step.
  • Backups that are never restored in a test.
  • Licenses registered to the provider with no transfer terms.
  • No answer to the question "what leaves our plant, and when?"

None of these rule a provider out on their own, but each one deserves a clear written answer before you sign.

Where Plantformance fits

Plantformance is one of several ways to get Ignition operated for you. Here are the facts from its published pages, followed by an honest view of where it fits and where it may not.

  • Company: Plantformance AG, founded in 2017 and headquartered in Ennetbaden, Switzerland. An Ignition user since 2013, it has attended more than 10 Ignition Community Conferences and describes itself as an Inductive Automation Alliance Partner that works 100% on Ignition.
  • Service: managed Ignition on-premises on FactoryBrain servers, with hardware, software, networking and 24/7 support for a fixed cost under subscription billing. Bringing your own Ignition licenses is possible.
  • Operations: a 24/7/365 Operations Center that handles patching, updates, change requests, monitoring and incident management, under SLAs.
  • Security and data: zero-trust architecture, hardware-rooted trust and a CIS compliant hardened OS with a closed by default approach. Process data resides in FactoryBrain inside the factory. Only monitoring, log and configuration data is shared with Plantformance.
  • Resilience: optional fault-tolerant architecture and high-availability clustering, a dual-purpose disaster recovery node and automated data protection.
  • Footprint: 110+ sites managed, 34+ countries on 5 continents, 4,000+ daily users, and an architecture track record of 100+ site rollouts and 45+ global interfaces.
  • Customer results: a Saint-Gobain customer quote credits Plantformance with rolling out Ignition in 30+ Saint-Gobain Abrasives sites in less than 2 years. Another Saint-Gobain quote describes a management solution rolled out to 18 factories in under 8 months.
  • Terms: a non-binding 3-month proof of concept, no binding contract, and the option to stop anytime with 30 days notice.
  • Development freedom: the same development control as a self-hosted Ignition gateway, with minor adjustments for security and traceability.

Beyond the managed service, Plantformance offers Ignition software development and multi-site IT/OT architecture work, described on its professional services page.

Plantformance is a strong fit when you run Ignition, or plan to, across several plants, want production data to stay on-premises, and do not want to build a 24/7 OT operations team. It also suits companies that want each new plant to arrive on a standard, prebuilt stack.

It may not be the right fit when you want everything in a public cloud, because the service is explicitly on-premises and not a cloud solution. It is also a weaker fit if your policy requires full operating system level control for your own team, or if you need published response times before a first call: the public pages promise SLAs but do not list response times, so ask for them. Plantformance is headquartered in Switzerland and reports sites in 34+ countries; if you need on-site support in a specific European country, ask which countries it covers in person.

If you want to see what a managed Ignition on-premises setup would look like for your plants, contact the Plantformance team to scope a proof of concept.

Frequently asked questions

Who offers managed Ignition services with 24/7 support in Europe?

Plantformance AG, a Swiss Inductive Automation Alliance Partner headquartered in Ennetbaden, runs a fully managed Ignition on-premises service with a 24/7/365 Operations Center and SLAs. It reports 110+ managed sites in 34+ countries on 5 continents. Ask any provider which countries it covers with on-site support before signing.

Can one provider operate and patch Ignition servers across several plants?

Yes. A managed provider can run a whole fleet from one operations center, using standard server builds, central monitoring and staged patch waves. Plantformance lists fleet management, automated patching and change requests in its service. Ask how the provider tests each release, backs up every gateway first and rolls back if needed.

Is there a turnkey Ignition server for a new plant?

Yes. Plantformance ships FactoryBrain servers with a managed Ignition engine, managed industrial database, hardened OS and monitoring preinstalled. Its process starts with a non-binding proof of concept: order the hardware, install it and try it for 3 months. Plan licensing, network access and PLC connections before the server arrives.

Should we run Ignition on-premises with a managed service or move it to the cloud?

Keep Ignition on-premises when production data must stay in the plant or screens must run without internet. Use the cloud for central dashboards and reporting. Ignition Cloud Edition has no industrial device drivers, so it needs edge gateways in the plants. A managed on-premises service fits teams without 24/7 OT staff.

What happens to our Ignition licenses and data if we leave a managed service?

Ignition licenses can be unactivated on one server and activated on another, so ask who owns them and whether you bring your own. Agree on a handover of backups, configuration and documentation. Plantformance needs no binding contract, and you can stop with 30 days notice. Confirm hardware return terms in writing.

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.