Support recurring process studies, sensitivity work, troubleshooting, and reviewed model updates.
Integrations
Bring Reflux to the systems your engineers already trust.
Reflux fits around existing process simulation and collaboration environments, so teams can move from question to reviewed result without changing how they think about the work.
Connected workflow
Simulation results, engineering context, and team review in one flow.
Aspen Plus, HYSYS, Aveva Pro II, terminal workflows, Slack, and Teams.
Integrations across the engineering stack.
Reflux is designed for process engineering teams, not software hobbyists. The integration experience focuses on supported outcomes, team review, and reliable delivery.
Bring Reflux into established simulation environments used by process design teams.
Let engineers request studies, review summaries, and keep stakeholders aligned where they already communicate.
Use Reflux through the deployment pattern that fits licensing, IT policy, and engineer preference.
Connect the outputs and approvals that matter to your team in a customer-approved rollout.
A shared value pattern for every integration.
Reflux captures the engineering question, constraints, and review expectations.
The team sees what Reflux intends to do and what evidence the study should return.
After review, Reflux works through the approved customer environment.
Results arrive with assumptions, limits, caveats, and decision-ready context.
Common questions about Reflux integrations.
Reflux works with Aspen Plus today. The agent itself is simulator-agnostic: it talks to an adapter layer rather than to any one simulator directly, and that architecture is designed to extend to other process simulators. Aspen Plus is the deepest integration live now.
Yes. Aspen Plus is the simulator Reflux supports today, driven through its COM automation interface, the same interface Python and VBA scripts use. Through it, Reflux reads blocks, streams, and components, edits parameters and stream specs, builds topology, runs the solver, and reads convergence status and results.
Through a simulator-specific adapter behind a simulator-agnostic layer. For Aspen Plus, the adapter uses the COM automation interface that Aspen already exposes for scripting, so Reflux works with your existing flowsheet files. Natural-language requests become inspectable actions against that interface: read a stream, edit a parameter, run the solver, check convergence.
No. Real changes sit behind explicit review: Reflux reads the existing flowsheet and ties each proposed change to the specific block, stream, and result a reviewer needs to see. When a change is applied, Reflux reads the value back from the simulator and verifies it before reporting the write as done. Runs are gated on required-input completeness, and results pass quality gates before Reflux reports success.
No. Reflux works against your existing Aspen Plus flowsheets and meets you where you already work: Slack, Teams, a local control panel, the CLI, or an MCP client. You describe what you want in plain language, Reflux proposes specific, inspectable actions, and you review the changes before they count.
Request a demo from the Reflux site and we will walk through it on a real Aspen Plus flowsheet: reading the model, proposing a change, verifying the write, and running the solver. If your team works in a different process simulator, tell us. The adapter roadmap is shaped by what working teams ask for.
Bring your simulation stack into a reviewed workflow.
Start with one recurring study and the Reflux team will map the right integration path with you.
Talk to the team ↓