APIs exist per product rather than as one platform: COM/ActiveX automation on Aspen Plus and HYSYS, SQLplus and a Process Data REST API on the IP.21 historian, and the AIoT Hub Web API. There is no developer portal or OAuth; most surfaces lean on Windows auth and license servers.
AspenTech scores F on Supergood's API Report Card. APIs exist per product rather than as one platform: COM/ActiveX automation on Aspen Plus and HYSYS, SQLplus and a Process Data REST API on the IP.21 historian, and the AIoT Hub Web API. There is no developer portal or OAuth; most surfaces lean on Windows auth and license servers.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
AspenTech (Aspen Technology, Inc., NASDAQ: AZPN until Emerson's March 2025 take-private at $265/share) is the dominant industrial process software vendor for asset-intensive process industries.
Vertical (Airtable): misc, AspenTech does not map cleanly to any Sanity-listed vertical; it is industrial process software / asset optimization for asset-intensive process industries (oil & gas upstream/midstream/downstream, refining, petrochemicals, specialty chemicals, polymers, pharmaceuticals/biopharma, food & beverage process, pulp & paper, metals & mining, power generation, electric T&D utilities, EPCs). Process engineers at refineries, chemical plants, and EPCs build steady-state and dynamic flowsheet models of distillation columns, reactors, heat exchangers, compressors, and full process units in Aspen Plus and Aspen HYSYS, sizing equipment, evaluating yield, energy and emissions trade-offs, and producing Aspen Capital Cost Estimator (Icarus) capex estimates that feed FEED packages.
9/10, in the process industries, AspenTech is effectively the default.
Yes, AspenTech is the operational system of record for the most commercially sensitive datasets at a refinery, chemical plant, upstream asset, or electric utility.
AspenTech is one of the oldest commercial industrial software companies in continuous operation.
The COM/ActiveX Automation Interface for Aspen Plus and HYSYS is 'not especially well documented' and integrators report 'you have to do a lot of digging' to discover object-model methods and required call sequences. Windows-only COM dependency makes Plus/HYSYS integration brittle for cross-platform (Linux/Mac) data science workflows; teams routinely run a dedicated Windows VM just to host the Aspen automation server. Full sourced list under Sources below.
Common alternatives include AVEVA (PRO/II, SimSci Dynsim, PI System / OSIsoft), Honeywell Process Solutions (UniSim Design, Experion PKS, Profit Controller, Forge APM), Siemens Digital Industries (gPROMS, COMOS, SIMATIC PCS 7/neo, XHQ), Schneider Electric (EcoStruxure, AVEVA partnership), Emerson DeltaV / Ovation (now sister-product to AspenTech under Emerson), Yokogawa (CENTUM VP, Exaquantum historian). Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
AspenTech has partial MCP support. Several community MCP servers wrap Aspen Plus process simulation through COM automation, with GitHub activity in 2026. AspenTech publishes no official MCP server and none of these projects are vendor endorsed.
Partially. MCP support for AspenTech exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.