Frequently answered question

Can I change models after I start using one?

Q: Can I change models after I start using one?

Customers typically see ROI within the first 3 months through time savings, improved decision quality, and reduced costs. Our team can work with you to calculate potential ROI based on your specific use cases during a personalized demo.

Answer

Yes — and on elvex, switching models is a configuration change, not a migration project.

‍

Because elvex is model-agnostic, your agents, workflows, and data connections aren't built on top of any single AI model. They're built on elvex. The model is just the engine running underneath — and you can swap it without touching anything else.

In practice, this means:

Your agents stay intact: Instructions, context, data source connections, and sharing settings are all preserved when you change models. You're not rebuilding anything — you're reassigning which model handles the requests.
You can switch at any level: Change the model for a single agent, a specific workspace, or across the organization. Admins can also set model overrides that apply automatically based on team or use case.
No data loss, no workflow disruption: Historical outputs, logs, and audit trails remain unchanged. The switch is forward-looking only.

This flexibility matters more than it might seem upfront. The AI model landscape moves fast — a model that's the right choice today may not be in six months. Pricing changes, new capabilities ship, and your use cases evolve. Being able to respond to that without rebuilding your AI infrastructure is a meaningful operational advantage.

If you're evaluating models, elvex also makes side-by-side testing straightforward: run the same agent against two different models, compare outputs, and make a data-informed decision before committing.