Updates happen when you decide

How releases are delivered

• Each release is a new Windows installer. It upgrades the existing installation in place and keeps your data, settings, and backups.
• AtlasOA installations run from source (Windows service mode) update with an included update script that copies new program files, keeps a copy of the replaced files, and never touches the database, uploads, or settings.
• Atlas K-12 applies any database structure changes automatically when it starts.
• Air-gapped Atlas K-12 sites bring installers in on removable media.
• Every release is listed with its date and changes in the public changelog, with security fixes described where disclosure is appropriate.

Security fixes

• Our target is to release a fix for a confirmed critical vulnerability within 7 calendar days and for a high-severity vulnerability within 30 days. Other fixes ship in regular releases.
• Security fixes are delivered as new full releases. You install them the same way as any other update.
• A formal supported-versions and end-of-life policy has not been published yet. Plan to stay on the current release.

Verifying an installer

Installers are not code-signed yet, so Windows may show an unknown-publisher warning. Compare the file's SHA-256 hash with the value we provide before running it:

Get-FileHash .\AtlasOA_Setup.exe -Algorithm SHA256

Upgrade procedure

1. Read the release notes.
2. Back up the data folder, or take a virtual machine snapshot. See Backup.
3. Stop the application or its Windows service.
4. Run the new installer as an administrator.
5. Start the application, sign in, and check the audit log and a few key screens.

Rolling back

There is no one-click downgrade. To roll back, restore the virtual machine snapshot, or reinstall the previous installer and restore the data folder you backed up before upgrading. Keep the previous installer until you are satisfied with the new release.