> 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/deployment-options.md).

# Cloud, hybrid and on-premises deployment

Choose where **Autom Center** and **Mate Agent** run before planning the installation. The same components can be placed differently to meet connectivity and operational requirements.

These diagrams show component placement. Lines represent the logical relationship between components, not firewall direction or a claim that all data stays inside a boundary. Use [network planning](/userguide/administration-and-runtimes/network-and-connectivity.md) for the connections.

## Cloud

Autom Center and the execution runtime are hosted in the Autom Mate cloud service. Your team configures automations and application access without installing these components in its own infrastructure.

```mermaid
flowchart LR
    U["Your users<br/>Web browser"] --> C
    subgraph AM["Autom Mate cloud"]
        C["Autom Center<br/>Build and operate"] --> R["Mate Agent<br/>Execute"]
    end
    R --> T["Connected systems<br/>Reachable through configured connections"]
    style AM fill:#e8f3ff,stroke:#2463a6
```

Choose this pattern when the cloud runtime can reach the required systems and the service's hosting arrangements fit your requirements. Application credentials, permissions and integration configuration still need to be set up.

## Hybrid

Autom Center remains cloud-hosted. A Mate Agent runs in infrastructure managed by your organization: an on-premises server or your own cloud environment.

```mermaid
flowchart LR
    U["Your users<br/>Web browser"] --> C
    subgraph AM["Autom Mate cloud"]
        C["Autom Center<br/>Build and operate"]
    end
    subgraph CU["Customer-managed infrastructure"]
        R["Mate Agent<br/>Execute"] --> T["Internal applications<br/>Files and dependencies"]
    end
    C --- R
    R --> X["Other configured services"]
    style AM fill:#e8f3ff,stroke:#2463a6
    style CU fill:#e2f6f1,stroke:#187564
```

Choose hybrid when work needs a runtime close to internal systems or local dependencies while retaining a cloud management platform. Plan the Center–Agent connection and target-system access separately. Review which inputs, results and operational records move between components in your configuration.

## On-premises

Autom Center and Mate Agent run in customer-managed infrastructure. This can be local infrastructure or a customer-managed private cloud environment.

```mermaid
flowchart LR
    U["Your users<br/>Web browser"] --> C
    subgraph CU["Customer-managed infrastructure"]
        C["Autom Center<br/>Build and operate"] --> R["Mate Agent<br/>Execute"]
        R --> T["Internal applications<br/>Files and dependencies"]
    end
    R --> X["External services<br/>Only where configured"]
    style CU fill:#e2f6f1,stroke:#187564
```

Your installation plan must include the platform's required database and logging components, certificates, capacity, backup and update responsibilities. Follow the component list supplied for the release. A customer-managed installation can still use external applications or AI providers; include those connections in the data-flow review.

## Compare responsibilities

| Planning question                                | Cloud                                    | Hybrid                                                                               | On-premises                                                                                            |
| ------------------------------------------------ | ---------------------------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ |
| Where is Autom Center?                           | Autom Mate cloud                         | Autom Mate cloud                                                                     | Customer-managed infrastructure                                                                        |
| Where is the Mate Agent?                         | Cloud service                            | Customer-managed infrastructure                                                      | Customer-managed infrastructure                                                                        |
| What must the customer infrastructure team plan? | Application access and integration paths | Agent host, dependencies and connections                                             | Center, Agent, storage/logging dependencies and connections                                            |
| Where do you start?                              | Configure your workspace                 | [Install a Mate Agent](/userguide/administration-and-runtimes/install-mate-agent.md) | [Install Autom Center](/userguide/administration-and-runtimes/install-autom-center.md), then the Agent |

Agree hosting location, support boundaries and recovery responsibilities for the selected deployment. Keep this infrastructure decision separate from **service deployment**, which selects the service version and configuration used to handle requests.