> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/administration-and-runtimes/system-requirements.md).

# System requirements and installation planning

Prepare a host that can run the selected Autom Mate release and the work assigned to it. Complete this checklist before downloading packages or opening firewall rules.

Dublin package availability — 13 October 2026: the Dublin on-premises installer is not yet available. Use this page to plan the environment; obtain the released package and its supported requirements from <support@autommate.com> before scheduling an on-premises installation or upgrade.

## Before you start

Have the deployment topology, target release, installation package and its supported platform requirements available. Use the package for the intended component: Autom Center and Mate Agent are separate installations. For a managed cloud workspace, focus on browser access, application connections and any customer-managed Agents.

## Build the installation record

| Item             | What to record                                                       |
| ---------------- | -------------------------------------------------------------------- |
| Release          | Target Center version, Agent version and their supported combination |
| Topology         | Cloud, hybrid or on-premises; host names and environment purpose     |
| Operating system | Supported edition, version and patch level for each component        |
| Capacity         | CPU, available memory, free disk and expected workload               |
| Storage          | Installation, temporary files, application data and log locations    |
| Dependencies     | Required database/logging components and supported versions          |
| Identity         | Installation account and service execution account                   |
| Network          | DNS names, certificate names, approved paths and proxy configuration |
| Operations       | Backup owner, update window, recovery procedure and monitoring owner |

Use the release-specific support matrix as the source for numeric minimums. Historic 4.2.0 installer requirements are not a Dublin 6.0.0 sizing recommendation.

## Size for the work

Estimate the number of overlapping executions, payload sizes and local processing steps. File conversion, OCR, database work and custom scripts have different resource needs. List the local interpreters, packages and modules used by those steps. Include the target application's own limits in the plan.

Start with an isolated representative workload and inspect **Manage → Mate Agents → View Metrics**. Compare memory, CPU and individual Agent Service readings over a suitable time range. Check **Recorded at**: **Latest** is the last saved snapshot. See [runtime metrics](/userguide/administration-and-runtimes/plan-execution-and-runtime-setup.md).

Keep licence entitlements and execution capacity separate. An unlimited-Hyperflow entitlement does not guarantee unlimited concurrent execution.

## Validate the host

1. Confirm that the operating system and component versions match the installation package's requirements.
2. Check that the installation and service accounts can access the intended directories. Keep application data and backup locations documented.
3. Verify DNS resolution, certificate trust and the [approved network paths](/userguide/administration-and-runtimes/network-and-connectivity.md) from the hosts that will use them.
4. Confirm free disk for installation, expected working data and logs, including the planned retention period.
5. Verify dependencies needed by the initial test flow. A package present on an administrator's laptop is not necessarily available to the runtime service account.
6. Record the backup and recovery checkpoint before changing an existing host.

## Expected result

The installation record identifies an approved package, compatible host, working connection paths and an owner for each dependency. Continue with [Autom Center installation](/userguide/administration-and-runtimes/install-autom-center.md) or [Mate Agent installation](/userguide/administration-and-runtimes/install-mate-agent.md).

If the package's required OS or component compatibility is missing, resolve that specific item before installation. Send the target topology and versions to **<support@autommate.com>**; a numeric value copied from an older release can hide an incompatible setup.