This section provides information about the configuration needed for core appliances and their surrounding network environment to deploy a new Collective.
The distributed architecture underpinning Appgate SDP provides the flexibility to deploy appliances where required. As a result, you can control access across your distributed network while meeting business requirements for compliance, security, monitoring, and reporting. The Sites and tunnels section has several examples of different architectures you might utilize when deploying Appgate SDP.
Appgate SDP also offers numerous HA mechanisms ensuring access can be maintained at all times.
.png?sv=2022-11-02&spr=https&st=2026-04-17T01%3A22%3A23Z&se=2026-04-17T01%3A33%3A23Z&sr=c&sp=r&sig=aGnPKpBUsDB2BKg4IMo0%2FSOAJa0wtQg1iryQrzLL%2B%2B0%3D)
Each Appliance is a stateless machine and can be configured to deliver different functions: Controller, Gateway, LogServer, LogForwarder, Metrics Aggregator, Portal, or Connector.
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 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.
The Controller is the central management appliance in the Appgate ZTNA system, responsible for user authentication, policy distribution, and overall system administration.
An appliance that acts as an enforcement point, controlling user access to protected resources.
A web-based interface that allows users to access resources without requiring a standalone Client. It serves as a reverse proxy for user traffic.
A component that extends connectivity to remote sites and unmanaged resources without requiring the use of a standalone Client.