---
title: "The first Controller"
slug: "the-first-controller-v6-5"
updated: 2025-10-31T18:21:29Z
published: 2025-10-31T18:21:24Z
canonical: "support.appgate.com/the-first-controller-v6-5"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.appgate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The first Controller

The first Appliance in any Appgate SDP Collective must be a Controller. Until you have the Controller, there is no admin UI. Appliance configuration can be done in several ways depending on the appliance option used:

| ***Hosted instances*** | The form you fill out for a hosted [ZTP](/v1/docs/about-appgate-ztp) instance has all the required data fields, so the appliance is pre-configured and will appear as the first Controller. A second [HA Controller](/v1/docs/controllers) will be automatically provisioned and joined to the Collective. This is the simplest way to get your Controller(s) up and running. |
| --- | --- |
| ***Cloud instances*** | Cloud instances use templates that can be customized by the vendor or generalized by Cloud provider: - The template can include the required data fields, in which case the instance can be pre-configured so it appears as the first Controller. - The template can also include a data field for the seed file, in which case it will then boot up into the function specified in the seed file. - If the instance boots up unseeded, then it can be configured as if it were a physical machine. |
| ***Virtual machines ***** | VMs typically need an ISO image specified when creating an appliance. - Certain VM types allow the seed file to be specified at the same time, in which case the VM will boot up into the function specified in the seed file. - If the VM boots up unseeded, then it can be configured as if it were a physical machine. |
| ***Physical machines ***** | These will boot up unseeded. You can either [run cz-setup](/v1/docs/configure-using-cz-setup) to make a Controller, or upload a [seed file](/v1/docs/managing-appliance-defining-a-new-appliance#export-seed-fileiso) to configure the function specified. |

** These may require an [Appliance installation](/v1/docs/appliance-installation) to create a new Appgate SDP appliance.

The diagram below shows the options for creating new appliances of any type. After cz-setup is used for the first time to create the Controller, then additional appliances can be created using a seed file. There are hyperlinks in the diagram that take you to that point in the process.

![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/hmfile_hash_e533bbd8.png?sv=2026-02-06&spr=https&st=2026-10-27T06%3A54%3A53Z&se=2026-10-27T07%3A54%3A53Z&sr=c&sp=r&sig=2X8IkppEXHfpjyYAgHbhnqTtjnj%2FmJ9JpHJ8JxubqlQ%3D)

The virtual or physical instance on which the system is running. Each appliance is a stateless, configurable machine that can operate as a single function or a combination of functions.

Appgate SDP (Software Defined Perimeter) is a security solution that provides secure access to resources based on user identity and context, leveraging a zero trust security model.

The Controller is the central management appliance in the Appgate ZTNA system, responsible for user authentication, policy distribution, and overall system administration.