> 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/plan-execution-and-runtime-setup.md).
# Plan execution and runtime setup
The browser is the place where you configure work. The execution environment must also be able to reach the systems, files, and dependencies used by that work.
Autom Center is the central platform component; Mate Agent is an execution component. Identify the host and agent assignment used by your deployment, including its access to target systems.
### Choose the topology
Choose a deployment pattern that fits your connectivity and operating requirements:
| Pattern | Component placement |
| ----------- | ---------------------------------------------------------------------------------- |
| Cloud | Autom Center and execution components are hosted in the cloud service |
| Hybrid | Autom Center is cloud-hosted and a Mate Agent is placed in customer infrastructure |
| On-premises | Autom Center and Mate Agent are installed in customer-managed infrastructure |
The appropriate choice depends on target-system reachability, operational ownership, and the required integrations. A cloud application and an internal directory may require different connectivity arrangements.
### Prepare the environment
Before installation or assignment, confirm:
* The supported component versions and installation package for your product release.
* The operating system, capacity, and dependencies required for the actual workload.
* DNS, certificates, and network paths between platform, execution host, and target applications.
* The identity under which scripts or desktop actions execute.
* Required local files, interpreters, packages, and modules.
* The owner for updates, monitoring, backup, and recovery.
Use the deployment-specific network requirements supplied for your environment. Do not copy historical port or operating-system values into a new installation without checking their applicability.
### Inspect a Mate Agent
Open **Manage → Mate Agents**. Under **My Mates**, the agent card shows its version, **Agent User**, **Time Zone**, and **Created At**, together with **Mate Details** and **View Metrics** controls. A default assignment is labelled **Default Device**.
Record which execution component the flow or deployment actually uses. If several are available, check the selected or default assignment and its access to the target system. Compare the agent's Time Zone with host and browser time when validating schedules.
### Read resource metrics correctly
Select **View Metrics**. The available ranges are **Latest**, **1H**, **3H**, **6H**, **12H**, **24H**, **3D**, and **7D**. Choose 1H or a wider range for trend charts.
**Latest is the most recently saved metric snapshot, not a real-time reading.** Check **Recorded at** before interpreting CPU, RAM, or active-operation values, even where a field label says “Current”.
Gateway is the primary analysis service in the metrics view. Check individual Agent Services for Active or Inactive states, especially the service used by a failing action. Correlate the saved snapshot with the relevant execution log.
### Verify after installation or update
Confirm the reported component versions and connection status. Run a controlled read-only task against a known test target. Inspect the execution record and returned value, then test any required script or file dependency on the execution host.
Test each required connector, network path and credential as part of service readiness.
For an update, record the starting versions, the approved update path, the maintenance window, and the recovery plan. Validate the same small test after the update before returning dependent operational work to normal service. Obtain the current release-specific installation instructions from the environment administrator or ****.
