Skip to main content
For:Site IT
For installation, sign-in, and update walkthroughs with screenshots, see Getting started with AitriumOS. This page summarizes the IT-relevant facts; for the full set of IT steps, start with the IT setup checklist.

​
System requirements

  • Windows 11 (and Windows 10), 64-bit (x64).
  • Microsoft Edge WebView2 runtime — included with Windows 11; otherwise provisioned automatically, per-user, during setup.
  • Normal operation requires no local administrator rights under either installer below.

​
Installer options

To satisfy a strict “no administrator privileges” requirement for self-installation, use the per-user NSIS installer. Aitrium can also set NSIS as the default for your sites — contact [email protected].
Download the current release after signing in at app.aitriumos.com → Downloads. (Specific version binaries and their hashes can be provided for change-control purposes — see Build integrity & validation.)

​
Firewall and endpoint-security rules

Where endpoint-security products or per-application firewall rules control which programs may connect, allow the AitriumOS executable, NewLeaf.exe: This matters most for the SFTP transfer to the investigator. It connects directly from the workstation and cannot use a web proxy, so a rule that blocks the program blocks the transfer even when the port is open. AitriumOS reports this case as Blocked by a firewall or Blocked from connecting. See Data flows & residency for the destinations and Upload connection troubleshooting for how to validate the connection.

​
Updates

  • Integrity. Every update package is cryptographically signed and verified before it is applied; a package that fails verification is rejected. Windows binaries are code-signed; macOS binaries are signed and notarized.
  • Distribution. Updates are delivered over HTTPS from Google Cloud Storage.
  • Delivery depends on how the application was installed:
    • Per-user (NSIS): the user is notified in-app when a new version is available and applies the update in their own context.
    • Per-machine (MSI), centrally deployed: version management is handled by your IT team through your deployment tooling.
  • Scope. Updates deliver fixes, improvements, and features; they do not change the security posture described in this section.