octoplant: AMDT's Platform for Automation Backup, Version Control and Recovery

octoplant is the software platform from AMDT (AUVESY-MDT) that automatically backs up, versions and restores the programs and configurations of industrial devices: PLCs, HMIs, robots, CNC machines, drives, SCADA projects and network equipment. AMDT describes it as its “production resilience and OT security platform” that works “across all major automation vendors” (about octoplant). In plant terms, it answers two questions that most sites cannot answer quickly: what is actually running in this device, and can we put the right version back?

octoplant was launched in 2022 as the successor to AUVESY’s versiondog and MDT Software’s AutoSave. This page covers what the platform does, how its workflow operates, what it covers, how it is sold and deployed, and what a buyer should check. The feature pages below it go deeper.

What octoplant does

AMDT positions octoplant as the “operational control layer” beneath octovision, its newer intelligence layer. The feature set, in AMDT’s own names, with what each means on the plant floor:

Feature	What it does	What it changes for a plant
Automated device backup	Scheduled jobs pull programs and configurations from devices	A current copy exists without anyone remembering to make one
Version control	Every backup and check-in becomes a numbered, retrievable version	You can see what a controller held last month, not only today
Smart Compare	Compares version against version, or stored against live; shown as graph, table or text	Differences are found in minutes rather than by reading code line by line
Change detection	Flags planned, accidental or unauthorized changes	Undocumented edits surface before they cause the next breakdown
Change management	Roles and approval workflows around versions	A defined path from “edited” to “approved”
Disaster recovery	Restores by pattern or per device	Recovery time after a failure or attack is bounded by a known-good copy
Centralized OT repository	One store for every device’s versions	The program no longer lives on a laptop or with an integrator who has left
Alerts and notifications	Notifies people when a job finds a difference or fails	Drift becomes an event someone acts on
Audit trails	Records “who changed what, when, where, and why”	Evidence for auditors and for incident investigations

Source: AMDT, about octoplant, as of October 2026. octoplant.com groups the same capabilities differently, under headings such as Threat Protection, Instant Recovery, Versioning and Compliance Management, and adds OT security and vulnerability management that scores CVEs with asset context.

The most important feature is the least visible one. Scheduled jobs that upload from the device and compare against the approved version are what turn a backup archive into a control. NIST’s OT security guide asks for exactly this pairing: backups of “configuration files, and programs at regular intervals,” and it asks that “backup procedures are included in configuration or change management processes” (NIST SP 800-82 Rev. 3). A repository full of versions is useful; a repository that tells you the device no longer matches it is what prevents the two-day breakdown.

The octoplant approved-version workflow

octoplant is built around one idea: every device has an approved version, and everything else is measured against it. AMDT describes the cycle in four steps: teams “check out the latest approved version, make changes in their familiar engineering tools, then create and check in a new version,” while “in the background, octoplant runs scheduled jobs across your OT environment” (AMDT).

An illustrative scenario. A night-shift technician changes a timer preset online to get a filler running again and goes home. Nothing is checked in. At 03:00 the scheduled job uploads the controller, Smart Compare finds one changed value against the approved version, and the controls lead sees an alert in the morning. The change is either approved and checked in as a new version, or reversed. Without the job, the difference would have surfaced months later, during the next download, as an unexplained fault.

The workflow asks something of people. Engineers and contractors must check out before editing and check in afterwards. The platform can detect when they do not, but it cannot make the discipline happen. We cover that cycle in check-in and check-out and the comparison itself in Smart Compare.

Who uses octoplant in a plant, and for what

AMDT names controls engineers, maintenance teams, OT security leads, quality and validation staff and plant managers among its audiences. Each uses the same repository for a different job:

Role	What they use it for	What they get
Controls engineer	Check-out, check-in and compare before a download	Confidence that the offline project matches the device
Maintenance technician	Restoring a program after a hardware swap at night	A known-good file without calling the integrator
OT security lead	Alerts on unexpected changes and firmware data for CVE work	Evidence of what changed, and when
Quality and validation	Audit trail for change control	Records an auditor can follow
Plant manager	Backup coverage and job status across lines	A measure of recovery risk, not a guess

The roles conflict in one place: alerts. If nobody decides whose job it is to answer a difference, every role assumes another one will.

What it covers

AMDT states that octoplant supports “180+ industrial device types” (amdt.com) and “160+ of the most common OT and IT vendors” (octoplant.com). The categories:

• Control: PLCs, DCS, and the engineering software projects behind them
• Visualization: HMIs and SCADA projects
• Motion and machines: robots, CNC machines, drives and field devices
• Network and IT: switches, routers, firewalls and industrial PC images
• Everything else: documents, generic files, and machines that are unnetworked or only partly networked

Treat any device list as examples, not a guarantee. The official support matrix is behind the myAMDT login, and coverage depends on the device model and the engineering software version. See supported devices for examples by category and how to verify them.

octoplant editions and deployment

AMDT publishes three editions on its pricing page but no prices (as of October 2026):

Edition	Positioning	Included devices
Core	Single sites or early-stage implementations, “without optional add-ons”	Up to 50
Plus	Growing environments, “enhanced features”	100+
Premium	Medium, large or highly regulated environments, “all-inclusive”	250+

Each licence covers one campus, jobs are unlimited, and documents do not count as devices. AMDT says devices can be added within a tier, and that moving up a tier becomes cheaper than adding devices once the count grows. The split of features between tiers is not published. Editions and licensing covers how to budget without a price list.

Deployment is mainly on-premises. The platform runs as a server with a central repository on PostgreSQL (version 17 as of release 105), desktop clients, and agents that reach devices on separated subnets. Release 105 in August 2025 added the first browser-based interface (Novotek). A hosted SaaS option for octoplant is not clearly stated by AMDT. The architecture page covers where each component sits in a segmented plant network.

Limits and open questions

An independent view should say what is not known as clearly as what is. As of October 2026:

• No published prices and no public feature split between Core, Plus and Premium.
• The device matrix is gated. You cannot confirm coverage of your exact firmware and editor versions without a myAMDT account or a conversation with AMDT or a partner.
• SaaS is unclear. Plants with no appetite for running another on-premises server should ask what hosting options exist.
• Agent behaviour is not publicly documented in detail: how agents authenticate, which ports they use, and how they behave when the server is unreachable.
• No public integrations with OT security platforms such as Claroty, Nozomi or Dragos were found. octoplant data reaches other systems through export APIs; see OTSSM and integrations.
• No IEC 62443-4-1 or 4-2 product certification was found. AMDT holds ISO/IEC 27001:2022, ISO 9001:2015 and TISAX as a company (Trust Center), and release 105 was penetration tested by Outpost24.
• Restores still need people. A tool supplies the right file. Someone with the right engineering software, licence and access still has to load it and prove the machine runs.

The general pitfalls of this class of tool apply too. Jobs configured for half the devices, alerts that nobody reads, and approved versions that nobody approves are failures of ownership, not software. They are the same failures we describe for FactoryTalk AssetCentre, and they are why the alternatives deserve a fair look before you commit.

How to evaluate octoplant

A checklist of questions to put to AMDT or a partner before buying:

• Coverage: send your device list with firmware and engineering software versions, and ask for written confirmation of upload, compare and restore for each
• Robots, drives and CNC: ask specifically, because these are the assets plants forget
• Unnetworked machines: how are they backed up, and who does it?
• Licensing: which edition fits your device count, and what defines a campus at your site?
• Architecture: where do the server and agents sit, which ports must open, and does it fit your segmentation?
• Restore test: ask to see a full restore of one of your own devices during the trial
• Audit trail: does it meet your regulatory need (21 CFR Part 11, NIS2, NERC CIP)? See compliance
• Integrations: what do the REST export API and the octovision Export API deliver to your CMDB or ticketing tool?
• Migration: if you run versiondog or AutoSave, what carries over and on what timeline? See versiondog and AutoSave
• Ownership: who in your plant will own the jobs, the alerts and the approvals?

The last question matters most. If no one can be named, start with an inventory of what you have and where the risk sits; an independent plant systems assessment produces exactly that baseline before any tool is chosen.

Deeper

• Editions and Licensing: Core, Plus and Premium, per-campus licensing, and the cost drivers to model without a price list
• Architecture: server, clients, agents, the repository and the web interface, placed across a segmented plant network
• Release History: releases 101.3, 105 and 107, what each changed, and how to handle upgrades

Related capability pages: backup and recovery, version control and change management and octovision. Back to the AMDT hub.