For the last several months, one question has come up in nearly every technical conversation we've had with manufacturers, IT teams, and integration partners: "Is your platform containerized?" Here's a clear answer. PTI has been container-native from day one Prompt-to-Insights, our intelligence layer for industrial data, was built on a containerized architecture from its first release. Every service — ingestion, the natural-language engine, dashboards, distribution — runs in its own isolated container. That's how it ships, how it deploys, and how it runs in customer environments today. There's no "container version" of PTI coming later. It's already there. The Core Platform completes the shift on 1 July 2026 The Itanta Analytics Core Platform — the data backbone that connects PLCs, SCADA, historians, MES, and databases across some of the most demanding manufacturing environments — has years of production deployments behind it. With v7.00.00.05, releasing 1 July 2026, the Core Platform completes its transition to a fully containerized architecture. Every service in the platform — Connect, Collect, Analyze, Visualize, Distribute — will run in its own isolated container, on Linux-based images that align with how enterprise IT already deploys production workloads. This isn't us adopting containers. It's us bringing the Core Platform onto the same modern foundation that PTI has used since launch — so both products share one deployment standard. Why it matters technically Containerization isn't a checkbox. It changes how the platform behaves in production: - Service isolation. A failure in one component stays contained. Dashboards keep running while a connector restarts. - Cleaner upgrades. Services update independently. Rollbacks are minutes, not maintenance windows. - Deployment portability. The same images run on bare-metal Linux servers, virtualized environments, private cloud, or air-gapped on-prem setups. - Security alignment. IT teams can scan, sign, and govern container images using the tooling they already have. No new processes to invent. - Orchestration-ready. Works inside Kubernetes, OpenShift, or simpler Docker-based deployments depending on what the customer environment supports. For OT architects and platform engineers evaluating Itanta, this means the platform fits inside your deployment standards rather than asking you to bend around ours. Why this is a strategic moment for Itanta We could have shipped containerization quietly as a release note. We're talking about it openly because it signals something larger about where Itanta is going. Manufacturing software has a reputation problem — monolithic installers, weekend-long upgrades, IT and OT fighting over deployment standards. We don't think that has to be the norm. PTI was built container-native because that's what modern industrial software should look like. With v7.00.00.05, the Core Platform meets the same bar. This is also the foundation for what comes next: faster release cycles, easier multi-site rollouts, cleaner partner integrations, and deployment topologies that scale with customer ambition rather than constraining it. This started with you asking We didn't prioritize this work because containerization is a trend. We prioritized it because customers and partners told us — directly, repeatedly — that it's what they need to deploy Itanta confidently across more sites, more lines, and more teams. That's how most of what we ship gets built. Connectors, dashboards, workflows, deployment models — they almost always start with someone in the field telling us where the friction is. We listen. We build. We ship. If you've asked us the Docker question over the last year: thank you. This release is partly your release.