# Appgate SDP — Business VPN & Zero Trust Access

Appgate SDP by Appgate, Inc. holds a panel rating of 3.5/5 from 6 AI judges (category median 3/5), as of 2026-11-11. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: Appgate, Inc. (https://appgate.com)
- Category: [Business VPN & Zero Trust Access](https://whats-best.ai/software/business-vpn.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/business-vpn/appgate-sdp
- Alternatives: https://whats-best.ai/software/business-vpn/appgate-sdp/alternatives ([markdown](https://whats-best.ai/software/business-vpn/appgate-sdp/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-11 · oldest source captured 2026-11-10

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Appgate, Inc.
- Headquarters: Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 10 Nov 2026

## The panel's verdict

AppGate ZTNA, Appgate's zero trust access product, was judged from its support manuals alone. Access and connectivity scored 7-8: access runs through per-resource entitlements evaluated when traffic is attempted, clients span Windows, macOS, Linux, mobile, ChromeOS, headless and Kubernetes sidecars, and the tunnel defaults to TLS 1.3 with single packet authorization and mutual TLS. Visibility and audit rests on audit logs described as a definitive record of all accesses and administrative actions, streamed to ten named destinations. Identity and policy is a flat 6: we found no public information on SCIM or automated deprovisioning, so a leaver is cut off by a hand-written stop policy. The split is architecture and assurance: the architecture is documented in depth, but the low score rests on no public information on independent audits, penetration tests, a bug bounty, a status page or an SLA. Sovereignty spans 0-7: higher scores credit customer-run appliances; the zeros are marked not rated for lack of public information. We found no prices on the pages; the only cost facts: per-user licensing and the always-on client consuming two user licenses.

**Speaks for it:**
- Access runs through per-resource entitlements, evaluated when traffic is attempted rather than per whole network.
- Clients cover Windows, macOS, Linux, mobile and ChromeOS, plus headless clients and a Kubernetes injector that adds clients to pods as sidecars.
- Audit logs are described as a definitive record of all accesses and administrative actions, streamed to ten named destinations including Splunk, Datadog and Azure Monitor.
- The admin UI runs entirely on REST APIs published as an OpenAPI v3 subset covering nearly all admin actions.
- Appliances are stateless and linearly scalable, with transparent failover that keeps established connections alive.

**Held against it:**
- We found no public information on independent security audits, penetration tests, a bug bounty, a status page or an SLA.
- We found no public information on SCIM or directory-based deprovisioning, so a leaver is cut off by a stop policy written by hand.
- We found no public information on the contracting entity, its jurisdiction, subprocessors or a data processing agreement.
- We found no public information on clientless browser access for contractors or connectors for the major clouds beyond Kubernetes.
- We found no public information on a Terraform provider, a multi-tenant console for service providers, or support channels and response times.

**Best for:**
- You need a contractor or partner to reach named hosts and ports without opening a whole network.
- Your team wants to automate administration through the REST APIs the admin console itself runs on.
- You want to run the appliances yourself so tunnels and audit logs stay on infrastructure you control.
- You need an audit trail of who accessed which resource and which administrator changed what, exported to your existing SIEM.

**Avoid if:**
- You must show an auditor an independent audit, penetration test or SLA before adoption.
- You need leavers to lose access the same day without an administrator writing a stop policy by hand.
- You plan MFA onboarding on headless always-on clients, which the documentation states is unsupported.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The IT Lead | The DevOps Engineer | The MSP Technician | The Operations Manager | The Information Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Access model & connectivity | 4/5 | 4/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Identity, access policy & device posture | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Logs, audit trail & incident response | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 4/5 | 3.5/5 |
| Deployment, API & administration | 3/5 | 3.5/5 | 3/5 | 3.5/5 | 3/5 | 3/5 |
| Architecture, reliability & security assurance | 3.5/5 | 3.5/5 | 3/5 | 3/5 | 2/5 | 3/5 |
| European sovereignty | 3/5 | 3.5/5 | n/r | n/r | n/r | n/r |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **3.5/5** | **3.5/5** | **3/5** | **3.5/5** | **3/5** | **3/5** |

### The judges

- **The IT Lead** (v1.0): Head of a three-person IT team at a 140-person mechanical engineering firm with two plants and a sales office in Vienna. The VPN still runs on the firewall, and every update of it is a weekend. Wants a client that installs through Intune and connects on its own, sign-in with Microsoft Entra so a leaver loses access the same day, the ERP and the file server reachable without opening the whole network, a fixed IP for the supplier portal, and a price per user that survives the next budget round.
- **The DevOps Engineer** (v1.0): Platform engineer at a sixty-person software company with servers at Hetzner, a Kubernetes cluster on AWS and a bastion host everyone shares a key for. Wants a mesh that reaches every server and cluster without inbound ports, access policies kept in Git and applied with Terraform, SSH access tied to the identity provider, connectors that run as containers, and a published architecture that says what the vendor's relays can see.
- **The MSP Technician** (v1.0): Senior technician at an IT service provider in Hamburg that looks after thirty clients, from tax advisers to a dental chain. Each client has its own remote access, set up by whoever was on site that year. Wants one console with a tenant per client, gateways and users added in minutes, access logs a client can be shown after an incident, billing per tenant, and prices per user that can be quoted without calling the vendor first.
- **The Operations Manager** (v1.0): Runs operations at a fifty-person consultancy where a third of the work is done by freelancers on their own laptops and the rest of the team travels to client sites. Has no IT department, only an external provider billed by the hour. Wants each freelancer to reach one project system and nothing else, access that ends with the contract, a setup a non-specialist can follow, and no call to the helpdesk from a hotel lobby.
- **The Information Security Officer** (v1.0): Information security officer at a regional energy supplier that falls under NIS2 and was asked by its auditor who could reach the control systems last year. Wants access granted per resource, not per network, device checks before a connection, every access and admin change in a log that reaches the SIEM, an independent audit of the product, and the identities and logs kept in Europe by a vendor whose subprocessors are listed.
- **The Skeptic** (v1.0): Has seen "zero trust" on a VPN that still drops every user into the whole office network, "no logs" from a vendor that keeps every connection for a year, and a remote access tool that locked out the whole company when its own control plane went down. Asks who can see the traffic and the metadata, what keeps working when the vendor is offline, whether the audit was published or only announced — and whether the network could be moved to a self-hosted server.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Integrations**
- Alwayson download URL: https://bin.appgate-sdp.com/x.y/client/Appgate-SDP-x.y.z-Installer.exe [S2]
- API admin rights inherited: admin rights configured for the API user apply to the REST APIs [S8]
- API user requirements: yes [S8]
- API version header: 22 [S8]
- Audit log example capabilities: blacklist user · revoke tokens · yes [S8]
- Controller API coverage: Controller APIs support nearly all actions available in the admin UI [S8]
- External load balancer: no [S10]
- Load balancer healthcheck: yes [S10]
- Load balancer layer limit: DNS · TCP/IP [S10]
- Openapi v3 subset: yes [S8]
- Rest API admin UI: Admin UI exclusively uses REST API calls to the Controller [S8]
- Rest API change disclaimer: REST API calls may change when a new version is released [S8]
- Rest API port: 8443 [S8]

**Legal**
- Script warranty disclaimer: none, delivered as-is [S8]

**Product**
- Active sessions: username · identity provider · client type · yes [S5]
- Alternative auth path: Alternative authentication path, e.g. OIDC fallback to LDAP [S9]
- Alwayson autoupdate: yes [S2]
- Alwayson cert path: write access to TrustedCertificatePath recommended for headless client [S2]
- Alwayson clienttype claim: yes [S2]
- Alwayson configurator: yes [S2]
- Alwayson definition: combines full client with headless client [S2]
- Alwayson executables: Appgate SDP Service runs twice (USER and SYSTEM); Service Configurator configures headless client [S2]
- Alwayson install switch: /S · /O (/ALWAYSON) [S2]
- Alwayson limitation claims: no [S2]
- Alwayson limitation licenses: 2 [S2]
- Alwayson limitation MFA: no [S2]
- Alwayson limitation same user: no [S2]
- Alwayson logs: C:\ProgramData\AppGate\ · service.log · driver.log [S2]
- Alwayson mode behavior: headless suspends on user sign-in and resumes on sign-out [S2]
- Alwayson pre signin connectivity: yes [S2]
- Alwayson token independence: yes [S2]
- Alwayson uninstall retention: no [S2]
- Alwayson upgrade full client: yes [S2]
- Alwayson use cases: remote domain join via bootable USB; remote administration entitlement; default route to capture all traffic [S2]
- App store clients: Mobile/ChromeOS clients distributed via app stores, linked from Downloads [S7]
- Assignment evaluation timing: immediately after sign-in and when tokens are renewed [S3]
- Audit logs: accesses · administrative actions · yes [S5]
- Azure monitor dce: yes · Data Collection Endpoint + Data Collection Rule [S6]
- Azure monitor transformation: DCR transformation can convert JSON logs to match target table; sample log available for testing [S6]
- Built in ha recommended: Built-in HA mechanisms recommended over external load balancer [S10]
- Client os coverage: Clients available for each supported OS and use case [S7]
- Client profiles: Client profiles seed clients to connect to Controllers; installed manually, by device policy, or in profile groups [S7]
- Client round robin: yes [S9]
- Compatibility matrix: Client compatibility matrix summarizes available clients and version differences [S7]
- Connect via local network: yes [S10]
- Controller profile dns: Controller failover via multiple A-record DNS entry for profile DNS name [S9]
- Coralogix https: yes [S6]
- Criteria combining modes: three combining modes: AND, OR, custom Boolean expression [S3]
- Cross collective ha: yes [S9]
- Custom criteria script: assignment criteria scripts supported (JavaScript) [S3]
- Daemon logs export: yes [S5]
- Datadog https: yes [S6]
- Default site ebr: New Collectives include a default Site preconfigured to use entitlement-based routing (EBR) [S10]
- Default tunnel mode: TLSv1.3 · yes [S10]
- Device controls: Admins can restrict user device control and client features via configuration controls [S7]
- Device policy conflict rule: alphabetically first policy name wins on conflicting device controls [S3]
- Dns policy conflict rule: alphabetically first policy name wins per match domain [S3]
- Dns policy fallback: identity provider DNS settings [S3]
- Elastic serverless API key: API key service required when using Elastic Cloud Serverless [S6]
- Elasticsearch auth: token-authentication · basic-authentication · API Key Service [S6]
- Elasticsearch retention: days · yes [S6]
- Entitlement access control: evaluated when traffic is attempted · yes [S3]
- Entitlement home site: Every entitlement must relate to a default Site (its home) [S10]
- Entitlement site assignment: yes [S10]
- Falcon logscale hec: HEC with ingest token · yes [S6]
- Fallback client controlled: yes [S10]
- Fallback site: 30 [S9]
- Fallback site: 30 [S10]
- Fallback site no chaining: 1 · no [S9]
- Fallback site policy control: yes [S9]
- Fallback site ram sizing: 100 · 50 [S9]
- Gateway autosuspend thresholds: see field [S9]
- Gateway weighting: Three-digit weighting factor; ratio determines distribution [S9]
- Ha builtin: Built-in HA mechanisms at multiple levels [S9]
- Headless clients: Headless clients are designed for servers requiring long-term connections with no user interaction [S7]
- Identity purpose: Identity settings define how identity is managed, including claims used to control access rights in AppGate ZTNA [S4]
- Identity sections: Identity menu sections: Client Profiles, Identity Providers, IP Pools, MFA Providers, Device Claim Scripts, User Claim Scripts, Local Users, Service Users [S4]
- Internal ha triggers: initial connection failure · high load · exhausted IP pool space · LDAP timeouts · cross-Collective · Gateway rejection · Gateway unresponsive · load-balance group failure · monitored action unhealthy · no Gateways 30 seconds -> fallback S… [S9]
- Ios site limit: 5 [S10]
- Ip pool mapping: IP Pool mapping feature in Sites supports allocation and one-to-one translation modes [S10]
- Ip pool translation: yes [S10]
- Kafka auth: SASL/SCRAM · yes [S6]
- Keepalive interval: 5 [S9]
- Kinesis aws access: AWS API access · IAM role via instance profile [S6]
- Kinesis batch size: 10000 [S6]
- Kinesis filter jmespath: JMESPath · yes [S6]
- Kubernetes injector: Kubernetes Injector injects headless clients on-demand into pods as sidecars [S7]
- Linux client types: 2 [S7]
- Load balancer limitations: External load balancers supported with limitations due to SPA and mTLS [S9]
- Local lan no hairpin: yes [S10]
- Log collection source: Sites selectable as log collection source; all Sites logged by default; option to collect from appliances never added to a Site [S6]
- Logforwarder outputs: AWS Kinesis · Datadog · Kafka · TCP · Azure Monitor · Elasticsearch/OpenSearch · Splunk · Coralogix · Falcon LogScale · Sumo Logic [S6]
- Logforwarder purpose: LogForwarder exports audit log records from the AppGate ZTNA Collective to external destinations [S6]
- Macos client types: 3 [S7]
- Mobile clients: Mobile client behaves same as desktop client in most respects [S7]
- Monitored action failover: HTTP · TCP Up [S9]
- Monitoring overview purpose: Monitoring and logs answer whether infrastructure operates as intended [S5]
- Monitoring sections: Monitoring overview · Observability · Active Sessions · Audit logs · Prometheus metric details · Daemon logs · Daemon names in logs · SNMP MIB · Collective Replication [S5]
- Multi logforwarder ha: yes [S9]
- Multi site connections: Clients can connect to multiple Sites in a single Collective at the same time [S10]
- Nearest site override: yes [S10]
- Observability format: OpenTelemetry [S5]
- Observability licensed: metrics · logs · traces · yes [S5]
- Override site: policies can set an override Site replacing entitlement Site [S3]
- Override site conflict rule: alphabetically first policy name wins [S3]
- Policy types: Access, Admin, Device, DNS, Stop [S3]
- Priority groups: two sequential failures within current group · >999 weight [S9]
- Profile group weighting: Profile groups enable cross-Collective HA with weightings [S9]
- Profile groups ha: Profile groups used for Cross-Collective high availability (HA) [S7]
- Prometheus builtin: yes [S5]
- Quic no handshake: QUIC streams packets with no handshake, no guarantee of delivery or retry [S10]
- Sdp model: Tunneled connections follow the software-defined perimeter (SDP) network model [S10]
- Session retention after failover: 5 · no [S9]
- Signin performance: policy_count/15 mS per policy · 100 · 1500 [S3]
- Site definition: Site may represent hosts in a subnet, a DMZ, a geographic location, or a business unit [S10]
- Snat stateful failover: no [S9]
- Snmp and prometheus unified: prometheus_primary_output": true} [S5]
- Source nat default: yes [S10]
- Spa mtls lb layer: TCP SPA + mTLS requires DNS or TCP/IP layer load balancer only [S9]
- Spa quic mode: SPA with QUIC requires Check UDP (and TCP) SPA mode [S10]
- Spa udp lb incompatible: no [S9]
- Splunk raw hec: RAW · yes [S6]
- Stateless appliances: yes [S9]
- Stop policy evaluation: stop policies evaluated first; evaluation ends on first match [S3]
- Stop policy scenarios: stop policies can block by OS family or GeoIP continent [S3]
- Stop policy use cases: security · block specific users/devices via ag.distinguishedName · temporary load reduction [S3]
- Sumo logic https: yes [S6]
- Supported lb configs: round-robin DNS · TCP/IP layer load balancer [S9]
- Tcp encryption: certificate uploaded in System > Trusted Certificates · yes [S6]
- Tcp format: yes [S6]
- Transparent failover: yes [S9]
- Tunnel inner protocols: TCP · UDP · GRE · ICMP · yes [S10]
- Tunnel mtu: 1500 [S10]
- Tunnel protocols: TCP · UDP [S10]
- Unhealthy report retention: 10 [S9]
- Windows client types: several [S7]
- Zero weight reserve: yes [S9]
- Ztna description: AppGate ZTNA is a network security system providing secure access to network resources through access rules called entitlements configured by the organization [S1]

## Questions

### Is Appgate SDP European?

Not determined: the vendor’s pages as captured do not say where Appgate SDP is based.

### Where does Appgate SDP store data?

Not stated on the vendor’s pages as of 10 Nov 2026.

### Does Appgate SDP have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

### What are the best alternatives to Appgate SDP?

As of 19 Nov 2026, the panel rates [Defguard (3.5/5)](https://whats-best.ai/software/business-vpn/defguard), [Firezone (3.5/5)](https://whats-best.ai/software/business-vpn/firezone) and [Tailscale (3.5/5)](https://whats-best.ai/software/business-vpn/tailscale) highest among the other 19 Business VPN & Zero Trust Access products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [Defguard](https://whats-best.ai/software/business-vpn/defguard) (EU-Made, Poland). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Appgate SDP alternatives](https://whats-best.ai/software/business-vpn/appgate-sdp/alternatives).

## What this page leaves out

- We found no public information on pricing on the pages we read (support.appgate.com/docs/client-guide-v7-0, support.appgate.com/docs/windows-always-on-client-v7-0, support.appgate.com/docs/policies-v7-0, support.appgate.com/docs/identity-v6-7, support.appgate.com/docs/monitoring-logging-and-auditing-v7-0, support.appgate.com/docs/external-log-settings-v6-7 and 4 more). If the vendor publishes it somewhere else, send us the page.
- We found no public information on compliance on the pages we read (support.appgate.com/docs/client-guide-v7-0, support.appgate.com/docs/windows-always-on-client-v7-0, support.appgate.com/docs/policies-v7-0, support.appgate.com/docs/identity-v6-7, support.appgate.com/docs/monitoring-logging-and-auditing-v7-0, support.appgate.com/docs/external-log-settings-v6-7 and 4 more). If the vendor publishes it somewhere else, send us the page.
- 3 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.

## Sources

- [S1] Access model & connectivity — found from sitemap: https://support.appgate.com/docs/client-guide-v7-0 (checked 2026-11-10)
- [S2] Access model & connectivity — found from sitemap: https://support.appgate.com/docs/windows-always-on-client-v7-0 (checked 2026-11-10)
- [S3] Identity, access policy & device posture — found from sitemap: https://support.appgate.com/docs/policies-v7-0 (checked 2026-11-10)
- [S4] Identity, access policy & device posture — found from sitemap: https://support.appgate.com/docs/identity-v6-7 (checked 2026-11-10)
- [S5] Logs, audit trail & incident response — found from sitemap: https://support.appgate.com/docs/monitoring-logging-and-auditing-v7-0 (checked 2026-11-10)
- [S6] Logs, audit trail & incident response — found from sitemap: https://support.appgate.com/docs/external-log-settings-v6-7 (checked 2026-11-10)
- [S7] Deployment, API & administration — found from sitemap: https://support.appgate.com/docs/client-deployment-and-management-v7-0 (checked 2026-11-10)
- [S8] Deployment, API & administration — found from sitemap: https://support.appgate.com/docs/rest-api-v7-0 (checked 2026-11-10)
- [S9] Architecture, reliability & security assurance — found from sitemap: https://support.appgate.com/docs/high-availability-ha-v7-0 (checked 2026-11-10)
- [S10] Architecture, reliability & security assurance — found from sitemap: https://support.appgate.com/docs/tunnel-architectures-v7-0 (checked 2026-11-10)

---

Cite as: whats-best.ai, "Appgate SDP — Business VPN & Zero Trust Access", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/business-vpn/appgate-sdp

Corrections: https://whats-best.ai/correct/1705?target=page
