User Guide

System Requirements

This page lists the browser, deployment, service, agent, network, license, and credential requirements AlloyScan needs in order to run.

Supported browsers

The AlloyScan web UI supports the latest two stable releases of the following browsers.

Browser Notes
Microsoft Edge Latest two stable releases
Google Chrome Latest two stable releases
Mozilla Firefox Latest two stable releases
Apple Safari Latest two stable releases

Mobile browsers (Safari on iOS, Chrome and Edge on Android) are in beta. The primary AlloyScan experience is desktop.

AlloyScan platform

AlloyScan is delivered as SaaS (*.alloyservice.com) and as on-premise deployments. The frontend and backend services are hosted by Alloy Software for SaaS or by you for on-premise. End-user requirements stop at a supported browser.

Audit Service

The Audit Service is the lightweight Windows service that performs agentless scan and audit from inside your network.

Requirement Value
Operating system (production) Windows Server 2016 or later
Operating system (evaluation) Windows 10 or later
.NET runtime .NET Framework 4.8.1 or later
PowerShell PowerShell 5.1
Network Outbound HTTPS (TCP 443) to the AlloyScan instance
Local storage Local disk for the encrypted credentials pool

Audit Agent

The Audit Agent is the optional per-endpoint service installed on devices that do not stay on the internal network.

Operating system family Supported versions
Windows Windows 10 or later, Windows Server 2016 or later
macOS macOS X 10.7 or later
Linux Debian-derived and Red-Hat-derived distributions

The agent requires only outbound TCP 443 (HTTPS). No inbound firewall rules are required on the endpoint.

Network requirements

Firewalls must allow outbound HTTPS from Audit Services and Audit Agents to the AlloyScan instance. For agentless scan and audit, the Audit Service host must also be able to reach each target over the ports required for that platform and operation.

See Required Ports Reference for the complete port matrix and conditional Windows requirements.

License and quotas

Quotas are set at the instance level on the License and propagate to each Site through per-site Max caps.

Quota Notes
Nodes (audited devices) Hard cap; instance value can be Unlimited
Users Hard cap; instance value can be Unlimited
Audits per month Soft cap; resets on the recharge day
API transactions per month Soft cap; resets on the recharge day

Per-site caps appear on Admin Center > Site Settings > Limits and usage. A per-site Max = 0 means "no per-site cap — inherit from the instance value".

Credential storage

Credentials used by the Audit Service (Windows, Linux and macOS, Hypervisor, SNMP, AWS, Azure, Google) are stored encrypted on the Audit Service host. Credentials never leave the local network. The form does not expose stored secrets — you replace a password by entering a new one.