Versions

Autessa was built with production customers at the heart of what we do. While LLMs and AI often have nondeterminism baked into model upgrades etc... we wanted to ensure that there were ways to get deterministic workflows.

Beyond that, we understand the importance of iteration. This means that we wanted to ensure that there were ways to always be able to rollback should we accidentally publish something that did not work so great in production.

Autessa Versioning

Play with the below publishing and rolling back to understand how the versioning scheme works.

The concept behind Autessa versioning is, anything you do in your sandbox, NEVER impacts a customer until you hit publish.

Then, that published version becomes the default version that can be sent to your end customers.

Should you notice an issue with the published version, you can always rollback your version to a previously released version to customers and have that change immediately take place.

Publish Agent/Tool

To publish a resource in the platform, you must have either "PUBLISH" or "ADMIN" access for the resource.

Rolling Back

In the model details page, you can see all the prior released model versions. You can browse the model to see the difference, and choose to rollback the published version to that one if you need.

You can still continue development in the sandbox and publish the draft version when it is ready for customers.