> For the complete documentation index, see [llms.txt](https://documentation.grax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.grax.com/technology/operate/updates-and-availability.md).

# Updates and Availability

GRAX updates itself every weekday, so keep the application online to stay on the current release.

{% hint style="danger" %}
Automatic updates can't be disabled.
{% endhint %}

## How Updates Work

* Every weekday, the GRAX Application checks in with `hq.grax.com` for the latest version. If a newer version exists, the app downloads it, installs it in place over the previous version, and restarts.
* Data operations (backup, archive, restore) in progress aren't harmed by the download or restart. The app resumes processing tasks when it comes back online.
* The app also performs a version and update check on every boot, which prevents it from reverting to an older version.
* To update immediately, press the **Update Now** button on the General Settings page. The app checks `hq.grax.com` and replaces the running app if necessary.

{% hint style="warning" %}
On platforms like Heroku or Docker, an application can be configured to always boot from a pre-selected image or slug. If GRAX updates itself on disk, the running version is then newer than the image or slug. GRAX's internal schema management means that reverting to an older version can be fatal to an app and require manual intervention. Updating on boot keeps the code on the latest release, and if that update fails, the app isn't allowed to boot an old version.
{% endhint %}

## Staying Online

An offline application doesn't receive updates and drifts from the current release for as long as it stays down. Extended drift may leave the application unable to function when it returns, at which point it must be redeployed and reimplemented.

Instance replacements, reboots, and short outages are expected and handled normally; prolonged downtime is the risk. Contact [GRAX Support](https://documentation.grax.com/support/get-support) before shutting down a GRAX Application for an extended maintenance window, migration, or infrastructure freeze.

## Frequently Asked Questions

<details>

<summary><strong>Can I control the update schedule?</strong></summary>

No. You can't customize the update schedule or perform an unattended software rollback. Weekday updates are how GRAX ships security, performance, and reliability fixes to every environment, so customers don't manage update schedules or maintenance windows themselves.

</details>

<details>

<summary><strong>Can I pin a GRAX version on a self-managed deployment?</strong></summary>

No. Self-managed deployments give you control over where your data goes and who has access to the infrastructure, but GRAX maintains control over its own development, testing, and release process.

</details>

<details>

<summary><strong>What if an update breaks GRAX?</strong></summary>

If your production GRAX environment is completely offline for login or backups, open a "Critical Production Issue" at <https://www.grax.com/help/>. This opens a priority support case that GRAX tracks to resolution.

GRAX monitors live environments proactively, so a release defect should be detected, fixed, and delivered to your environment without any action on your part. While you wait for GRAX Support and your next automatic update, review your own infrastructure logs and metrics for underlying causes such as a full disk or a database in read-only mode.

</details>