AI-powered process simulation

Describe your flowsheet.
We'll build it in Aspen.

AEX translates plain-English process descriptions into working Aspen Plus simulations — building streams, blocks, and thermodynamic parameters automatically. Your proprietary process data stays on your machine; only structural descriptions are sent externally for parsing.

Get early access See how it works ↓
AEX — live session
you describe
"Feed goes into COL1. COL1's bottoms go into COL2. COL2's distillate is the final product."
→
Claude extracts structure
"blocks": [
  { "id": "COL1", "type": "RadFrac" },
  { "id": "COL2", "type": "RadFrac" }
],
"streams": [
  FEED → COL1,
  COL1.bottoms → COL2,
  COL2.distillate → PRODUCT
]
→
Aspen .bkp built
✓ COL1 created (RadFrac)
✓ COL2 created (RadFrac)
✓ Stream S1 connected
✓ FEED configured
✓ Saved to .bkp
→ Open in Aspen Plus
Flowsheet — live build preview
FEED Material MIX Mixer HX-1 Heater COL1 RadFrac COL2 RadFrac PRODUCT Distillate BOTTOMS Recycle S-FEED S1 S2 S3 D1 REC
initializing…
Zero hallucination on process data
Proprietary data never leaves your machine
Works with Aspen Plus V14+
Windows COM automation
Built for process engineers
What it does

Every feature built for engineers

No prompt engineering, no simulation guesswork. Describe what you want and review what gets built.

💬
Plain-English parsing
Describe block connections in your own words. Claude extracts the topology — no special syntax required.
🔒
Your data stays local
All proprietary process data and files remain on your machine. Only structural descriptions are sent externally for AI parsing — full on-premise/local inference is on our near-term roadmap.
🛡️
No hallucinated numbers
Flow rates, pressures, stage counts — all entered by you via form fields. AI never touches critical process values.
⚙️
Direct Aspen automation
Uses Aspen Plus's COM interface to build blocks, connect streams, and set parameters — all programmatically.
📄
Ready-to-run .bkp files
Output is a native Aspen Plus backup file. Open it, review it, and run it — no manual setup needed.
🖥️
Streamlit UI
A clean, local web app with fields for every parameter. No command line, no config files.
🔗
Multi-column support
Build flowsheets with multiple distillation columns, inter-column streams, and split product outputs.
⚠️
Why AI handles structure, not numbers
Process simulation requires exact numerical inputs. A wrong flow rate or pressure can send a simulation in the wrong direction — or worse, give a plausible-looking wrong answer. AEX uses AI only for what it's good at: understanding relationships and layout. Every numerical value comes directly from you. And because only structural descriptions are sent externally for parsing — never your actual process data or files — your proprietary information stays on your machine throughout.
How it works

Two ways to build your simulation

Start from scratch with a new flowsheet, or load an existing .bkp and modify it — same plain-English workflow either way.

new .bkp Build from scratch
1
Enter your numbers
Fill in components, feed flow rate, pressure, and stage counts directly in the form. These values go straight to Aspen — the AI never sees them.
hallucination-free zone
2
Describe the structure
Write how your blocks connect in plain English. "COL1's bottoms feed into COL2" is enough. Claude extracts the block list and stream connections using a structured tool call.
claude-sonnet-4-6
3
Build and open in Aspen
Click build. AEX creates all blocks, wires every stream, sets stage counts and feed conditions, and saves a .bkp file ready to open in Aspen Plus.
Aspen Plus V14 COM API
edit .bkp Modify an existing file
1
Load your .bkp file
Point AEX at an existing Aspen Plus backup file. The COM interface opens it and reads the current block and stream topology — no manual re-entry needed.
reads existing topology
2
Describe what to change
Tell it what to add, remove, or reconnect. "Add a flash drum between HX-1 and COL1" or "Replace COL2 with a liquid–liquid extractor." Claude resolves the edit against the existing structure.
diff-aware parsing
3
Save the modified .bkp
Only the changed blocks and streams are touched. Everything else in your file — convergence settings, property methods, design specs — is preserved exactly as you left it.
non-destructive edits

Ready to stop clicking through Aspen?
Start describing instead.

Currently in early access for process engineers. Windows + Aspen Plus V14 required.

Request early access