Skip to main content
Keeping InteraOne up to date ensures you receive the latest features, performance improvements, security patches, and bug fixes.
Always back up your production data before performing an upgrade.

​
Upgrade Process

1

Backup your data

Before upgrading, back up all persistent services:
  • MongoDB
  • MinIO
  • Qdrant
  • Redis (recommended)
This allows you to roll back safely if necessary.
2

Pull the latest release

Navigate to your installation directory.
Or upgrade to a specific release.
3

Review new environment variables

Some releases introduce new configuration values.Compare your current configuration with the latest:
  • docker/.env.example
  • apps/*/.env.example
Add any newly introduced variables to your existing configuration.
Never overwrite your existing .env files. Merge new variables into your current configuration instead.
4

Pull the latest Docker images

5

Restart InteraOne

Docker Compose recreates only the services that have changed while preserving your persistent data.
6

Verify the deployment

Check running containers.
Verify the Gateway.
Expected response:

​
Post-upgrade Checklist

  • I can access the Console.
  • Users can log in successfully.
  • The AI Agent responds correctly.
  • The Web Widget loads normally.
  • Background workers are processing jobs.
  • File uploads work correctly.
  • Knowledge search returns results.

​
Rollback

If an upgrade does not behave as expected:
  1. Restore your backups.
  2. Checkout the previous release.
  1. Restart the platform.

​
Best Practices

Back Up First

Always create backups before upgrading production deployments.

Read Release Notes

Review release notes for breaking changes and migration steps.

Upgrade Gradually

Upgrade one release at a time instead of skipping multiple major versions.

Test First

Validate upgrades in a staging environment before updating production.

​
Need Help?

If you encounter issues during an upgrade:
  • Review the container logs in Dozzle.
  • Verify your environment variables.
  • Check the Gateway health endpoint.
  • Open a GitHub issue if the problem persists.
Last modified on July 18, 2026