AI for chemical engineering simulation software.
NEXT 36 '26.
Waterloo Chemical Engineering, Toronto.
Intentional over transactional.
Always down to chat.
7 weeks of building in public.
The demo is live.
The stealth is over.
The DMs are open.
Scariest post I've ever hit "send" on.
Also the most important one.
Today I'm coming out of stealth.
I've been building Reflux - a natural language interface for chemical engineering simulation software.
The tools that design every oil refinery, chemical plant, ASU, and carbon capture project on earth are running on software built in the 1980s. The simulation engines are powerful. The UX is not.
Engineers spend hours manually configuring parameters, clicking through nested menus, debugging errors that say "simulation did not converge" with zero context on why.
Reflux sits on top of these tools and lets you talk to them.
Type what you want. The system builds the flowsheet, configures the parameters, and runs the simulation. If it fails, it diagnoses why and iterates.
The engineer stays in control. The tedious manual setup goes away.
I'm a chemical engineer. I trained on this software. I know exactly which parts make you want to scream. I'm building the thing I wish I had.
Looking for design partners - engineers who want to shape this. DMs open.
@JustJerry121 depends on the ask - same way that Cursor, CC or Codex would approach a prompt, Reflux does the same. logically. if you want it to troubleshoot errors - it does. if you want it to build - it does. if the build has an error, it keeps the human out of the loop - and fixes it.
@linkdude2209@X woah this is really cool - I'll have to make a few site improvements thanks man. I'm a chemical engineer by trade and I experienced the problem first-hand for 5 years, so I'm building what I wish I had. Target is to go to market and be used in industry.