Reflux for Vendors
Give your simulator a natural-language front end.
Reflux drives simulation software through its own automation interface. Partner with us and your users get an agent that speaks your package, without you standing up an AI team.
Nothing to start. Embed it, co-sell it or refer it, and your licence stays the gate.
Why partner
Every licensee is a Reflux user waiting to happen.
They already have the seat, the licence and the cases. What they do not have is an agent that can drive your package and show its work.
- Days, not quarters. Where the automation interface is documented, most of the effort goes into verifying variable paths on a real seat.
- Your licence stays the gate. Reflux drives a licensed, installed seat and never bypasses it. Every Reflux user is your customer first.
- A front end, not a rival solver. Where you already ship an assistant, Reflux can sit beside it or call it.
Three ways to partner
Pick the shape that fits your roadmap.
Every one starts with the same adapter.
- Embed
Ship Reflux inside your suite as the natural-language layer. Your brand in front, your seat underneath.
- Co-sell
Run a short pilot with two or three shared clients, one month, read-only first. Joint go-to-market from there.
- Refer
Point users who ask for AI at Reflux and stay out of the build entirely.
Questions vendors ask
Do you compete with the AI features on our own roadmap?
Reflux is a front end and an orchestration layer, not a replacement for your solver. Where you already ship an assistant, Reflux can sit beside it or call it. Where you do not, Reflux is the fastest way to have one.
What does it cost us?
Nothing to start. Partnership terms depend on the shape: embed, co-sell or refer. A pilot with shared clients is priced as a fixed monthly number so nobody carries per-token exposure while they evaluate.
Which packages already have adapters?
Aspen Plus is available to the public today, and several other adapters are in use with partners. We do not list partners' packages here. Tell us what you ship and we will say where it sits.
What about our clients' confidential data?
Two configurations, named in the pilot agreement: an open-weight model running inside the client's own environment, or an enterprise API with no data retention. Client cases are never used to train anything.
Does it need our GUI, or just the API?
Either. Where a package exposes a documented API, Reflux talks to that. Where the useful surface is the desktop application itself, Reflux drives the running application.
Bring one workflow your users repeat.
Thirty minutes with whoever built your automation interface is usually enough to say whether the adapter is days or weeks.