> ## Documentation Index
> Fetch the complete documentation index at: https://help.onetsolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Updates

> Keep your applications and the platform up to date from the console

The console watches for new versions and tells you when one is available. Nothing is updated without your action, except the platform itself if you enable automatic updates.

## Application updates

Every night, the platform compares what runs on your instance with what is published upstream, on two levels:

* The catalogue definition of the application, when the project changes its recommended configuration
* The digest of each container image, which catches a new build published under the same tag

When one of them differs, the application shows an **Update available** banner listing the services concerned and the date of the last check.

<Steps>
  <Step title="Open the application">
    Go to the application page in the One Click Apps section.
  </Step>

  <Step title="Start the update">
    Select **Update** in the banner or in the actions. The task pulls the new images and recreates the containers.
  </Step>

  <Step title="Check the result">
    The application returns to the **Running** status. The update is recorded in the history.
  </Step>
</Steps>

<Note>
  Data volumes are kept during an update. A backup is still worth taking before a major version change: see [Backups](/one-click-apps/backups).
</Note>

## Platform updates

The platform follows its own release cycle. Its page shows the installed version, the latest available version and a badge when they differ.

You can update it manually from **Platform settings**, or enable **Automatic updates** to have new versions installed overnight. Your applications keep running during a platform update.