Softwr

Manufacturing · head to head

AVEVA System Platform vs Rootstock

AVEVA System Platform logo

AVEVA System Platform

Manufacturing

Supervisory HMI and SCADA platform, formerly sold as Wonderware System Platform

From
On request
Rated
-
Full reviewWebsite
Rootstock logo

Rootstock

ERP

Manufacturing ERP built natively on the Salesforce platform

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: AVEVA System Platform wonderware is no longer a name you can buy; if you have inherited documentation, purchase orders or job specifications that say Wonderware, everything has to be re-mapped to AVEVA product names before you can quote it.; Rootstock every Rootstock user also needs a paid Salesforce platform licence, so the true cost is two subscriptions stacked; third-party estimates put a fully loaded seat around 200 to 500 US dollars per user per month, which is far above the Rootstock line item alone.
  • They diverge on capability: AVEVA System Platform covers ArchestrA object model, Rootstock covers Native Salesforce architecture.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which AVEVA System Platform and Rootstock actually diverge.

Attributes where AVEVA System Platform and Rootstock differ
AttributeAVEVA System PlatformRootstock
PlatformsWindowsWeb, Salesforce Platform, iOS, Android
CategoryManufacturingERP

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in AVEVA System Platform

  • ArchestrA object model
  • InTouch HMI
  • AVEVA Historian
  • Redundancy
  • Situational awareness graphics
  • OMI
  • Alarm management
  • Connectivity

Only in Rootstock

  • Native Salesforce architecture
  • Production and work orders
  • Materials and MRP
  • Inventory management
  • Order to cash
  • Project accounting
  • Financials
  • Quality and compliance

What people use each for

The jobs each tool is most often brought in to do.

AVEVA System Platform

  • A multi-site food manufacturer standardising operator screens across plants that run different PLC brandsnot Rootstock
  • A water utility with a decade of ArchestrA templates where rewriting to another platform cannot be justifiednot Rootstock
  • A pharmaceutical line needing ISA-88 batch recipe handling above existing Rockwell and Siemens controllersnot Rootstock
  • A plant modernising legacy InTouch applications without discarding the existing screens and scriptsnot Rootstock

Rootstock

  • A discrete manufacturer already running Salesforce Sales Cloud that wants configured quotes to become works orders without an integration layer between two systemsnot AVEVA System Platform
  • An engineer-to-order equipment maker that needs project cost tracking and CRM opportunity data in one database for margin reportingnot AVEVA System Platform
  • A medical device supplier that needs lot and serial traceability under the same security and audit model as its customer recordsnot AVEVA System Platform
  • A manufacturer replacing an on-premise ERP whose IT team wants to stop maintaining servers and standardise administration on a platform it already supportsnot AVEVA System Platform

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

AVEVA System Platform

  • Wonderware is no longer a name you can buy; if you have inherited documentation, purchase orders or job specifications that say Wonderware, everything has to be re-mapped to AVEVA product names before you can quote it.
  • AVEVA Flex converts licensing to a recurring subscription draw-down, so organisations that budgeted for a perpetual licence with a support percentage face a materially different cost model at renewal.
  • It is Windows only, and version compatibility between System Platform, Historian and InTouch is tight, so upgrades are coordinated projects rather than incremental patches.
  • The ArchestrA object model has a steep learning curve and small systems end up paying for structure they do not need, which is why integrators often deploy standalone InTouch instead.
  • Licence enforcement counts I/O aggressively and unexpected tag growth during commissioning can trigger a mid-project licence purchase at list price.

Rootstock

  • Every Rootstock user also needs a paid Salesforce platform licence, so the true cost is two subscriptions stacked; third-party estimates put a fully loaded seat around 200 to 500 US dollars per user per month, which is far above the Rootstock line item alone.
  • Rootstock publishes no pricing whatsoever, so budget-setting depends on reseller and analyst figures rather than vendor rates, and there is no public benchmark to test a quote against.
  • Building on Salesforce means inheriting Salesforce governor limits and API constraints, which surface as batch size and data volume ceilings in high-transaction manufacturing that a purpose-built ERP would not hit.
  • Your ERP is now hostage to another vendors commercial decisions: Salesforce list price rises, edition changes or licence policy shifts flow straight into your ERP running cost with no alternative supplier.
  • Implementation is a serious project, commonly quoted in the tens to hundreds of thousands of dollars and measured in months, and the partner pool that genuinely knows both manufacturing and Salesforce-native ERP is small, which lengthens timelines and raises day rates.

Pricing, plan by plan

AVEVA System Platform

On request
  • AVEVA System Platform$undefined/year
    • Licensed by I/O count, client count and platform nodes
    • Sold through AVEVA Flex subscription token pool or legacy perpetual licence
    • Legacy perpetual licences carry an annual customer FIRST support fee

Rootstock

On request
  • Rootstock Cloud ERP$undefined/year
    • Manufacturing, inventory and supply chain modules
    • Runs as a managed package on the Salesforce Platform
    • Salesforce platform licences purchased separately for every user

Which should you pick?

Choose AVEVA System Platform if

  • You need archestra object model.
  • You work on Windows.
  • You also want intouch hmi.
AVEVA System Platform review

Choose Rootstock if

  • You need native salesforce architecture.
  • You work on Web, Salesforce Platform, iOS, Android.
  • You also want production and work orders.
Rootstock review

Questions people ask

Is AVEVA System Platform or Rootstock better?
Neither clearly leads. AVEVA System Platform starts at On request and Rootstock at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, AVEVA System Platform or Rootstock?
AVEVA System Platform starts at On request and Rootstock at On request.
Does AVEVA System Platform or Rootstock run on more platforms?
AVEVA System Platform runs on Windows. Rootstock runs on Web, Salesforce Platform, iOS, Android.
What is AVEVA System Platform best used for?
AVEVA System Platform is most often used for a multi-site food manufacturer standardising operator screens across plants that run different plc brands, a water utility with a decade of archestra templates where rewriting to another platform cannot be justified, a pharmaceutical line needing isa-88 batch recipe handling above existing rockwell and siemens controllers, a plant modernising legacy intouch applications without discarding the existing screens and scripts. Of those, a multi-site food manufacturer standardising operator screens across plants that run different plc brands and a water utility with a decade of archestra templates where rewriting to another platform cannot be justified are not what Rootstock is typically brought in for.
What can AVEVA System Platform do that Rootstock cannot?
AVEVA System Platform covers ArchestrA object model, InTouch HMI, AVEVA Historian, Redundancy. Rootstock covers Native Salesforce architecture, Production and work orders, Materials and MRP, Inventory management.

Answered from the vendors’ own pages

AVEVA System Platform: Is Wonderware still sold?

No. The brand was retired; buy AVEVA System Platform, AVEVA InTouch HMI, AVEVA Historian or AVEVA Plant SCADA instead.

Rootstock: Do I need Salesforce to run Rootstock?

Yes, and it is not optional. Rootstock is a managed package on the Salesforce Platform and every user requires a Salesforce licence in addition to the Rootstock subscription.

AVEVA System Platform: Can I still buy a perpetual licence?

AVEVA steers new business to Flex subscriptions. Perpetual is increasingly restricted to existing agreements and renewals.

Rootstock: What does Rootstock actually cost?

Rootstock does not publish rates. Third-party estimates put the ERP subscription at roughly 150 to 300 US dollars per user per month before Salesforce licences, with implementation quoted separately.

AVEVA System Platform: Do my old InTouch applications still run?

Yes, legacy InTouch applications are supported in System Platform, though the older graphics do not gain the newer situational-awareness features without rework.

Rootstock: Is it suitable for process manufacturing?

It is built for discrete manufacturing. Recipe and batch-driven process manufacturers are a poor fit and should look elsewhere.

AVEVA System Platform: What is AVEVA Flex?

A subscription credit pool you draw against for any AVEVA product, which trades a fixed licence for a recurring balance you must keep topped up.

Rootstock: Has Rootstock been acquired?

No. Rootstock remains independent and was itself the acquirer, buying Salesforce-native applications firm Ascent Solutions in March 2026.

Share

Related pages

More on AVEVA System Platform

More on Rootstock

Keep looking

Other head to heads