Ignition 2027

Ignition 2027 is in public beta. Here is what is actually useful.

Inductive Automation's next major release is available to try now, with general availability aimed at February 2027. This page is a plain-English look at what's new, what's optional, and what we would and wouldn't put on a running line yet. Onsite in California's Central Valley, remote support nationwide.

By Hunt Integrative Solutions LLC (HIS Controls), a Gold Certified Ignition integrator. Updated . We'll revise this page when Ignition 2027 reaches general availability. This is our independent take, not an official Inductive Automation page.

Where things stand

  • Public beta now: 2027.2.0-beta1, released November 3, 2026.
  • General availability: targeted for February 2027.
  • Ignition 8.3: supported through September 2030.
  • Beta is for non-production systems only. Beta questions go to Inductive Automation's Early Access forum, not their Support team.

Status and timeline

Ignition is moving to a yearly major release, with a long-term support (LTS) version you can standardize on. Here's how the first one is rolling out.

  1. September 23, 2026
    Ignition 2027 previewed at ICC 2026.
  2. November 3, 2026
    Public beta starts, with a new beta build about every two weeks. Use it on a non-production system.
  3. February 2027 (target)
    General availability. This is the earliest point we'd talk about a production cutover.
  4. Q1 2028
    A version becomes long-term support a year after release. The next LTS is 2027.15.0-LTS.

Ignition 8.3 stays supported through September 2030, so there's no rush to leave a stable 8.3 system.

What's useful on the plant floor

Ignition 2027 is a big release. These are the four areas we think matter most to plants running production every day, in the order we'd look at them.

Historian redundancy and backups

This is the "we lost history when the server died" problem.

  • Core Historian can sync history to a backup node
  • Fail over without a gap in history
  • Scheduled historian backups, set up from the Gateway web page
  • Does not require the new Enterprise Historian

New Perspective charts and Workstation keyboards

Better trends and touchscreens without extra add-ons.

  • Sixteen new chart components, including radar and Sankey
  • Inductive Automation says existing projects won't break on upgrade
  • Power Chart 1.5 with better tag browsing and pen setup
  • Native on-screen keyboards in Perspective Workstation

Catalyst Core: optional Designer help

AI comes in two optional modules, not baked into the platform. You can ignore both.

  • Catalyst Core is included with Ignition at no additional cost
  • Help with scripts, expressions, SQL, and building UDTs
  • Plain-language health summaries on Gateway pages
  • Bring your own model: ChatGPT, Claude, Gemini, or self-hosted Ollama for an air-gapped plant. The plant pays its own AI provider.
  • Every AI action needs explicit human approval, and an AI change can be rolled back

Everyday engineering improvements

Smaller changes that save real time and close real gaps.

  • Tag import and export with Excel
  • REST APIs for tags and history
  • OPC UA connection redundancy and a Beckhoff ADS driver
  • An audit log that keeps the previous value of tag writes
  • More than one identity provider on a Gateway
  • EU Cyber Resilience Act readiness

What to treat carefully

Some of the biggest headlines are the parts we'd be slowest to put on a running line.

Catalyst Agent

Agents that work through chat or run on their own, an AI chat component for Perspective, and Model Context Protocol (MCP) support.

  • Inductive Automation hasn't published a price
  • Their developers have warned that the AI programming interfaces are still changing
  • We'd treat it as a pilot only, not something to build a line around yet

Enterprise Historian

Built on TimescaleDB for Ignition (made with Tiger Data, sold and supported by Inductive Automation) and aimed at large-scale operations.

  • The published benchmark shows about 10 times faster ingest, about 10 times less storage, and a much faster one-year query, run on 2.1 billion points at 10,000 tags
  • Inductive Automation says results depend on hardware and workload
  • Most smaller plants will still be fine on Core or SQL Historian
  • Requires Ignition 2027; Inductive Automation hasn't committed to bringing it to 8.3
  • Pricing hasn't been published

Multi-site and cloud tools

Multi-site Gateway management, Ansible automation, and a native AWS connector are real improvements, but they matter mainly to larger or multi-site operations. If that's you, we're glad to talk through them. If not, they're safe to skip for now.

How we'd approach an upgrade

No surprises on a running line. Here's the order we'd follow.

  1. Stable on 8.3? Stay there.
    If the plant is running well and you want a long support window, 8.3 is supported through September 2030.
  2. Evaluate on a test Gateway.
    To try 2027, stand up a separate, non-production Gateway and keep production on 8.3.
  3. Wait for general availability.
    Don't promise a production cutover during the beta. Plan the move once 2027 is released.

Inductive Automation expects the move from 8.3 to 2027 to be a straightforward upgrade, and says now is the time to start planning. We agree with planning now. We'd still test on your own projects before touching production.

How we can help

  • Decide whether to stay on 8.3 or stand up a 2027 test system
  • Build a non-production test Gateway from a copy of your projects
  • Check backups and historian setup before any upgrade
  • A free controls health check onsite in California's Central Valley, or a free remote review anywhere else in the U.S.

Planning your next Ignition move?

Tell us what you're running and we'll help you decide whether to stay on 8.3 or test 2027. Free health check onsite in California's Central Valley, or a free remote review anywhere else in the U.S.