Version: 1.0

Release notes

What changed in each release, newest first. This page covers the whole 1.0 line, so it stays here as new 1.0.x releases are added.

1.0.1, 24 September 2026

Nothing changes until you choose it. Active Directory sign-in is off until you configure it, and your existing local accounts keep working exactly as they do now.
Update the centre first, then the agents. Upload the new centre in Ballast Manager (Updates), then use Settings, Agents, Update all outdated. The console marks any host still on the 1.0.0 agent as outdated until you do. The new volume actions below need the 1.0.1 agent.
Some Settings pages moved. If you go looking for one of these and it is not where you left it, see Settings below.

Operators can sign in to the console with their Active Directory account, with your groups mapped to the Administrator, Operator and Read-only roles.

Sign in as user@domain or DOMAIN\user. Nested groups count, and a person in several mapped groups gets the most privileged role.
A person in none of the mapped groups cannot sign in, and is told why.
Local accounts are tried first and remain the break-glass login. A domain controller being down never locks anyone out, and directory sign-in cannot be turned on unless a local administrator exists.
A Test button checks the bind account and each mapped group, and can try a real sign-in, without saving anything.
Signed-in directory users are re-checked every 15 minutes. Removing someone from the mapped groups, or disabling or deleting their account, signs them out. If the directory cannot be reached, sessions already open are kept. A person refused at sign-in because they are no longer in any mapped group is signed out at once.
It is included in every tier, including the free Community tier. Agents are not affected: this is the console's sign-in only.

Start with Active Directory sign-in. If your domain controllers do not offer LDAPS yet, see LDAPS on a domain controller.

Alarms is now its own page. The webhook and email settings used to sit under Authentication only because that was the first settings page built. Authentication now holds the inactivity timeout, Active Directory and the operator accounts, and each page saves only its own settings.
Ballast Manager has its own section, next to Backup, that says what Manager is for and links to it. Backup keeps a single line and the same link.
The agent service account provisioning (the script, the example command and the "already set up" tick) moved from Domain & DNS to Agents. The script and its download are unchanged. Domain & DNS is now just the DNS servers.
Fixed the breadcrumb on Settings pages. Every page other than Credentials, Authentication and ISO Library was headed "Settings > Credentials".

A runbook can be deleted from the console: right-click it in the library list or the tree, or use its menu, then Delete runbook and type its name to confirm. Deleting one also clears its run history.
Right-click Recovery runbooks in the tree for New runbook, matching the button on the library page.
The Run history and Recovery runbooks tables no longer overflow their card when a run's message is long.

A disk or volume with nothing on it (per Ballast's own VM inventory) can be emptied by right-click, on the disk row or its volume. Format volume reformats in place and keeps the drive letter. Delete volume wipes the disk back to raw and poolable. Both are refused on a cluster member and on the OS volume.
A data volume carved from spare space on the OS's own disk (D: or I: on hosts with that layout) can be formatted. The agent now reports which physical disk backs each volume and whether that disk also carries the boot or system partition, and Format checks the volume's own partition rather than the whole disk.

Public launch. The centre, Ballast Manager and the Windows agent are on the Downloads page, and the agent's source is public on GitHub.