octoplant Pricing: Editions, Licensing and How to Budget Without a Price List

octoplant pricing is not published. As of October 2026, AMDT’s pricing page describes three editions, Core, Plus and Premium, and how the licence is counted, but gives no figures. That is normal for industrial software sold through partners, and it means a buyer has to build the budget from the cost drivers rather than from a list price. This page sets out what is public, what is not, and how to model the rest.

For what the platform does, see the parent page on octoplant; for the company behind it, the AMDT hub.

The three octoplant editions

Edition	AMDT’s description	Included devices	Likely fit
Core	“Ideal for single sites or early-stage implementations”	Up to 50	A single plant, or a pilot on one area
Plus	“Designed for growing environments, with more devices included (100+) and enhanced features”	100+	A full plant with mixed vendors
Premium	“The all-inclusive package for medium and large or highly regulated environments”	250+	Large sites, regulated industries, or a standard rolled out across a group

Source: octoplant.com/pricing, as of October 2026. The “likely fit” column is our reading, not AMDT’s.

What the tiers tell you, and what they do not. The tiers step by included device count. AMDT says that within a tier you “can always scale” by adding devices, and that once the count grows “it becomes more cost-effective to upgrade to the next tier rather than adding individual devices” (pricing). Core is offered “without optional add-ons,” Plus has “enhanced features” and Premium “the full suite of advanced capabilities,” so some capability is held back from the lower tiers. Which capability is not published. Ask for the split in writing, in particular for approval workflows, audit trail features used for regulated work, and integrations such as the export APIs.

How octoplant licensing is counted

Three rules are public:

1. Per campus. “Each license covers one campus, a physical location that may include multiple buildings on a contiguous piece of land” (octoplant.com). A site with a packaging hall across the road is probably still one campus. Two plants in different towns are two licences.
2. Per device. The edition is chosen by how many devices you back up and version: PLCs, HMIs, robots, drives, CNC machines, network devices and PCs.
3. Unlimited jobs and documents. “All editions include core functionality, unlimited jobs, and secure data storage,” with “virtually unlimited document storage at no additional cost.” Documents do not count as devices.

The unlimited jobs matter more than they look. A job is a scheduled upload and compare. If jobs were metered, plants would run them less often to save money, and the time between a change and its detection would grow. Unlimited jobs remove that trade-off: you can run nightly compares on every device at no extra licence cost.

What octoplant pricing does not publish

Item	Status as of October 2026	Why it matters
Prices for any edition	Not published	The budget has to come from a quote
Feature split between tiers	Not published	You may need Plus or Premium for a feature, not for device count
Commercial term (subscription or perpetual)	Not stated on the pricing page	Changes the five-year cost and the renewal risk
What counts as one device	Not defined publicly in detail	A PLC with a separate HMI and drives may count as several
Price of services	Not published	Implementation and validation can rival the licence
Migration credit from versiondog or AutoSave	Not published	Existing customers may have a path; ask

The device-definition question is the one that changes quotes. On a typical packaging line, an illustrative cell might hold one PLC, two HMIs, six drives, one robot and a managed switch. Whether that is one device or eleven decides the edition. Get the counting rule in writing and apply it to your own asset list.

A worked count (illustrative, not a quote). Assume, for the sake of the arithmetic, that every backed-up item counts as one device. AMDT has not published that rule; it is the assumption to test.

Item on one illustrative packaging line	Quantity	Counted as a device?
PLC	1	Yes
HMI panels	2	Yes, if their projects are backed up
Drives with parameter sets	6	Yes, if their parameters are backed up
Robot controller	1	Yes
Managed switch	1	Yes, if its configuration is backed up
Drawings, manuals, I/O lists	Many	No: documents are not devices
Line total	11

Six such lines is 66 devices, before utilities, palletisers and the network core. That is already past Core’s 50 and into the range where AMDT itself says moving up a tier becomes the cheaper path. Under a one-device-per-line rule, the same plant would sit comfortably in Core. The counting rule moves the edition, so settle it before you compare anything else.

The cost drivers behind octoplant pricing

Without a list price, model the total cost from what drives it. The diagram shows how the pieces combine, and which of them you can know before a vendor conversation.

Five things drive the total:

• Device count. Build the list from an actual inventory, not from memory. Plants routinely undercount drives, robots, HMIs and network devices, and those are what push a site from Core into Plus.
• Number of sites. Each campus is a licence. A group standard across six plants is six licences, even if each plant is small.
• Services. AMDT lists Implementation and Commissioning, Update Service, Job Optimization, TIA Portal Integration, Image Service Integration, IQ/OQ Services and Migration and Expansion. In regulated industries, IQ/OQ (installation and operational qualification) is often required, and the validation effort can be a large share of year-one cost. See 21 CFR Part 11.
• Migration. If you run versiondog or AutoSave, moving archives and job definitions is work, even with the Project Integrator Tool added in release 107. See migration to octoplant.
• Internal effort. Someone has to own jobs, alerts and approvals. That time is a real cost, and the one most often left out of the business case.

Infrastructure is a sixth, smaller driver. octoplant runs mainly on-premises, so budget for a server, its operating system, backup of the server itself, and network changes to let it reach devices. See octoplant architecture.

Where it gets hard

Comparing quotes across tools. Competing products are packaged differently. FactoryTalk AssetCentre is an on-premises Rockwell product, Copia Automation offers cloud, data-centre or air-gapped deployment, and Software Defined Automation (SDA) is browser-based. Their licence units will not line up with a per-campus, per-device model. Normalise every quote to the same device list, the same sites, the same services and a five-year term. The alternatives page describes how the models differ.

Buying the tier for the wrong reason. A site with 45 devices may need Premium because it is regulated, not because of size. A site with 120 devices and no regulation may be well served by Plus. Decide the feature need first, then check the device count.

Growth inside the term. Device counts rise with every new line or machine. Ask how a mid-term move from Core to Plus is priced, and whether new devices delivered by OEMs are covered.

Partners quote differently. octoplant is sold through AMDT and a partner network that AMDT puts at more than 100 firms (octoplant.com). Services rates and bundles vary by partner. Two quotes for the same scope are a reasonable request.

Budgeting checklist: questions to ask

• Which edition fits our device count, and what exactly counts as one device?
• Which features are in Core, Plus and Premium? Please list them.
• Is the licence a subscription or perpetual, and what does renewal cover?
• How is our site layout counted in campuses?
• What does a mid-term upgrade between editions cost?
• What services are included, and which are quoted separately (implementation, IQ/OQ, migration, training)?
• If we run versiondog or AutoSave today, is there a migration path or credit?
• What server and network infrastructure must we provide?
• Who supports us locally: AMDT directly or a partner, and at what response time?

An owner-side view helps here. An owner’s engineer can build the device list, normalise competing quotes and hold the vendor to a written scope, without taking a margin on the licence. If you do not yet know your device count, a plant systems assessment produces it.

Next in this section: octoplant architecture and the release history.