# Pomerium — Business VPN & Zero Trust Access

Pomerium by Pomerium, Inc. holds a panel rating of 3/5 from 6 AI judges (category median 3/5), as of 2026-11-11. Provenance: provenance unknown; sovereignty: 3 of 6 dimensions proven.

- Vendor: Pomerium, Inc. (https://pomerium.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/pomerium
- Alternatives: https://whats-best.ai/software/business-vpn/pomerium/alternatives ([markdown](https://whats-best.ai/software/business-vpn/pomerium/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: Pomerium, Inc.
- Headquarters: Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting: Outside the EU by default; pages mention the US [S2]
- Free plan: Not stated on the vendor’s pages as of 10 Nov 2026

## The panel's verdict

Pomerium is an open-source identity-aware proxy that replaces network-wide access with named routes: HTTP and HTTPS apps open in an ordinary browser, SSH natively, other TCP and UDP services through a client, all signed in through your own identity provider with allow and deny policy per route. Its strongest area is identity and policy, scoring 7 across the board, with access and connectivity and deployment and administration close behind at 6–7; judges credited authorization logs that record why each request was allowed or denied, a documented configuration API with Terraform and Helm, and a self-hosted path in which Core and the Enterprise control plane run in your environment. Weakest are sovereignty at 4–6 and architecture and assurance at 5–6, the latter with no published independent audit, bug bounty or availability SLA found. Sovereignty spans 4–6 as judges weigh the U.S.-based hosted plane against the documented self-hosting route. Visibility and audit spans 5–7, and pricing transparency sits lowest at 2–3, with no public prices for the two named editions.

**Speaks for it:**
- Identity and policy holds at 7 across the board, on sign-in through your own OIDC provider with per-route allow and deny rules.
- Authorization logs record why each request was allowed or denied, with a documented log-field schema reaching custom headers.
- Self-hostable end to end, with Core as the self-managed data-plane engine and the Enterprise control plane in your environment.
- Administration runs as code, with a documented configuration API, Terraform support, and Helm or Docker deployment.
- An open-source core under Apache 2.0, with published pages stating plainly what the product protects and what it does not.

**Held against it:**
- No published independent audit, penetration test, bug bounty or availability SLA was found, and the SOC 2 text describes a customer's obligations rather than a certification of Pomerium.
- Long-running TCP or WebSocket connections are not terminated when the policy that allowed them becomes invalid, per the documented behavior.
- The contracting entity is Pomerium, Inc. of Beaverton, Oregon, its own servers are stated to be in the U.S., the subprocessor list is available only on request, and we found no published data processing agreement.
- Desktop clients cover Windows, macOS and Linux, and we found no public information on iOS or Android clients.
- We found no public information on log retention periods, SIEM streaming, alerting on unusual access, or MDM-based client rollout.

**Best for:**
- You need contractors or freelancers to reach specific internal HTTP and HTTPS apps from an ordinary browser, with no dedicated connector installed.
- Your platform team runs Kubernetes and wants access policy managed as code through Terraform, a documented API and Helm.
- You must keep the data plane, control plane and logs on your own servers, with identity from your own provider such as self-hosted Keycloak.
- You want every access decision explained after the fact, because the authorize logs record why each request was allowed or denied.

**Avoid if:**
- You need a managed control plane hosted outside the U.S. — Pomerium's own servers are stated to be in the U.S., and self-hosting is your own operational work.
- You must cut off live sessions the moment access is withdrawn — the documented behavior leaves long-running TCP or WebSocket connections open.
- Procurement requires third-party assurance — ask the vendor: the public pages we read do not show it
- You expect a click-through setup run by non-specialists — in every deployment model the data plane runs as a cluster in your own environment.

## 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 | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Identity, access policy & device posture | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Logs, audit trail & incident response | 2.5/5 | 3/5 | 2.5/5 | 3/5 | 3/5 | 3.5/5 |
| Deployment, API & administration | 3/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Architecture, reliability & security assurance | 2.5/5 | 3/5 | 3/5 | 3/5 | 2.5/5 | 3/5 |
| European sovereignty | 2/5 | 3/5 | 2/5 | 2.5/5 | 2.5/5 | 3/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **3/5** | **3.5/5** | **3/5** | **3.5/5** | **3/5** | **3.5/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: 3 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Outside the EU | 0/4 | [S2] |
| Hosting options | Self-hostable | 1/1 | [S4] |
| Open source | Open source (permissive) | 1/1 | [S5] |
| 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).

**Compliance**
- CCPA: yes [S2]
- Dispute resolution: yes [S2]
- Ftc enforcement: yes [S2]
- GDPR transfer basis: EU-U.S. Privacy Shield · Swiss-U.S. Privacy Shield · GDPR [S2]
- Pomerium supports SOC 2: Pomerium used by a company with SOC 2 Type 2 compliance obligations; page does not claim Pomerium itself is certified [S3]
- Privacy shield: yes [S2]
- Rights recognized: EU-U.S. Privacy Shield · Swiss-U.S. Privacy Shield · CCPA · GDPR [S2]
- Trust center: yes [S1]

**Data**
- Agg deidentified disclosure: yes [S2]
- Profiling: no [S2]
- Retention: Personal information kept only as long as necessary; deleted or anonymized after statutory period [S2]
- Sale of data: no [S2]
- User collection: Name, email, username, company name, credit card details, phone number collected from users [S2]
- Visitor collection: IP address, cookie information, browser info collected from visitors [S2]

**Hosting**
- Server location: US [S2]

**Integrations**
- Cli install channels: binaries · RPM/DEB packages · Homebrew · Docker · source build [S7]
- Components: clientless access · tunnel-free · verification before execution · context-aware access [S5]
- Keycloak oidc support: Keycloak (and generic OIDC providers) supported as identity provider [S9]
- Prerequisites docker compose: Docker and Docker Compose required for the guide [S9]

**Legal**
- Address: 9450 Southwest Gemini Drive, Beaverton, OR 97008, United States [S2]
- API license: Apache License 2.0 [S13]
- Children age: 13 [S2]
- Company name: Pomerium, Inc. · 2026 [S14]
- Copyright: 2026 [S2]
- Copyright: Pomerium [S10]
- Entity: 2026 · Pomerium, Inc. [S1]
- Entity: Pomerium, Inc. [S15]
- Entity name: Pomerium, Inc. [S2]
- Entity name: Pomerium, Inc. [S1]
- Entity name: Pomerium, Inc. [S2]
- Entity name: Pomerium, Inc. [S3]
- Entity name: Pomerium, Inc. [S6]
- Entity name: Pomerium, Inc. [S8]
- Entity name: Pomerium, Inc. [S14]
- Entity name: Pomerium, Inc. [S15]
- Policy last updated: February 18, 2025 [S2]
- Privacy contact email: privacy@pomerium.com [S2]
- Processor role exclusion: yes [S2]
- Rights response time: 30 [S2]
- Security contact: security@pomerium.com [S2]

**Pricing**
- Plans named: Pomerium Zero · Pomerium Enterprise · yes [S1]

**Product**
- Academy exists: yes [S14]
- Access log config options: Array of string · See Access Fields and Defaults · ACCESS_LOG_FIELDS · access_log_fields [S11]
- Access log custom headers: headers.{CustomHeaderName} allows logging arbitrary request headers, e.g. headers.user-agent [S11]
- Access log fields defaults: if access_log_fields is not defined, all default fields are logged [S11]
- Access log fields setting: access_log_fields config setting controls which fields are included in per-request access logs emitted with message http-request [S11]
- Access log ip field: ip · xff_num_trusted_hops set appropriately · no [S11]
- Access log query field warning: query · may contain sensitive information · yes · no [S11]
- Access log request ID field: request-id · unique request identifier assigned by Pomerium · yes [S11]
- Access log terraform support: yes [S11]
- Access logs: yes [S3]
- Agentic access: Agentic access management: prevents agent secret leakage, unauthorized tool calls, and overprivileged access [S1]
- Allow any authenticated user: yes [S9]
- API purpose: API for managing Pomerium configuration. [S13]
- API resources: KeyPair · Policy · Route · ServiceAccount · Settings [S13]
- API version: v0.32.5-rc.1 [S13]
- Auth proxy: yes [S3]
- Authenticate authorize access: Authenticate with existing identity provider · Authorize on every request · Access with governance and logged access decisions [S1]
- Authenticate via identity provider: users sign in through your identity provider [S4]
- Authorization policies: email · group membership [S7]
- Authorize log keys: allow · allow-why-false · allow-why-true · deny · deny-why-false · deny-why-true · databroker_server_version · databroker_record_version [S10]
- Boundary publishing principle: yes [S6]
- Certificate name filters: attribute=value · yes [S7]
- Cli client cert auth: macOS · Windows [S7]
- Cli listen stdin stdout: yes [S7]
- Cli service account auth: yes [S7]
- Clientless access: VPN replacement; access internal apps without client software or layer 4 networking [S1]
- Clientless access: yes [S4]
- Clientless browser http: Browser-based clientless access supports HTTP and HTTPS applications [S6]
- Clientless limitations: no [S6]
- Connection logging: yes [S7]
- Connection reevaluation: Long-lived connection behavior on identity, policy, or device state changes must be defined [S6]
- Continuous reevaluation: yes [S8]
- Core self managed: Pomerium Core is the self-managed server / data-plane engine [S4]
- Databroker postgres: postgres [S10]
- Databroker version audit: databroker version numbers allow determining data used for policy evaluation [S10]
- Deployment requirement: The deployment must restrict direct upstream access and cover every required protocol and administration path [S15]
- Description: identity and context-aware reverse proxy for clientless access to internal apps without a VPN [S5]
- Desktop advanced settings: yes [S7]
- Desktop os support: Windows · macOS · Linux [S7]
- Desktop route tags: yes [S7]
- Desktop TLS verification toggle: yes [S7]
- Device posture definition: Device posture is the current security state of a device. [S8]
- Encryption e2e: yes [S7]
- Enterprise features: Enterprise Console · Enterprise API · centralized configuration · namespaces and RBAC · audit and deployment history · directory sync · external data · service accounts · sessions · metrics [S4]
- Enterprise fleetdm posture: client certificate linking request to Fleet host · yes · FleetDM host data · vulnerability data · policy results [S8]
- Enterprise self hosted control plane: yes [S4]
- Environments: cloud · on-prem · hybrid [S4]
- Helm deployment: yes [S3]
- Hosted version: Pomerium Zero · yes [S5]
- Identity aware proxy: Identity-aware proxy securing private apps with identity, context, and policy on every request [S1]
- Identity aware routes: Pomerium can replace broad network entry with named identity-aware routes [S15]
- Implicit trust limits: Pomerium does not remove implicit trust inside an application, cloud account, cluster, service mesh, or network path that bypasses its routes [S15]
- Infrastructure agnostic: yes [S1]
- Integrations google groups: integrates with Google Groups for fine-grained access control [S3]
- Kubernetes: yes [S1]
- Languages: 91.9 · 0.5 · 6.2 [S5]
- Log view journalctl: logs viewable via journalctl for system daemon installs [S10]
- Mtls support: yes [S7]
- Multi cloud support: GCP · Azure · AWS · on-premise · hybrid [S3]
- Multiplayer support: yes [S1]
- Open source: yes [S3]
- Open source identity aware proxy: open source identity-aware proxy based on BeyondCorp and zero trust [S4]
- Pass identity headers: yes [S9]
- Planned enterprise features: dynamic access policy · secret-management integration · device-context authorization · audit log dashboard [S3]
- Platform editions: Pomerium Zero · Pomerium Enterprise [S15]
- Platform editions: Pomerium Zero · Pomerium Enterprise [S14]
- Policy as code: yes [S1]
- Policy combines identity device data: Pomerium combines identity claims, device identity, and external data in route policy evaluation [S8]
- Policy validated at connection: no [S7]
- Pomerium protected protocols: documented native path · client-assisted paths · browser routes [S6]
- Posture compliance not proof of health: compliant posture does not prove device is uncompromised [S8]
- Posture limitations: stale · incomplete · forged · incorrectly linked [S8]
- Posture signals: device identity · management state · operating-system version · encryption · screen lock · endpoint protection · known vulnerabilities [S8]
- Ppl behavior: Pomerium Policy Language allow/deny rule semantics [S10]
- Protocol client requirements: ordinary SSH client with trusted CA · usually require a local connector or protocol-specific integration [S6]
- Protocols secured: SSH, RDP, MySQL, Redis, DNS and other TCP/UDP services [S7]
- Repo activity: 176 · 4683 · 297 [S5]
- Request level authorization: yes [S4]
- Residual risks: yes [S6]
- Review ratings: 4.8/5 · G2 [S1]
- Scoped access: yes [S1]
- Security boundary: Pomerium can protect route access, transport connections, identity assertions, and decision evidence within its documented boundary; upstream application and surrounding system determine confidentiality, integrity, availability, accountabi… [S14]
- Session duration tied to pomerium session: yes [S7]
- Short lived sessions: yes [S1]
- Slack integration: Slack agent collaboration with per-user permission and context separation [S1]
- Ssh recording: yes [S1]
- SSO: yes [S7]
- Strict policy failure mode: strict posture policy can block legitimate users on provider failure [S8]
- Tcp listen default: 127.0.0.1:0 [S7]
- Tcp proxy chaining: yes [S7]
- Tcp route port selection: 443 · yes [S7]
- Tcp route syntax: tcp:// · tcp+https:// [S7]
- Tcp udp audit: yes [S7]
- Topics: aigateway · beyondcorp · gateway · go · iam · identity · identity-aware-proxy · pomerium · reverse-proxy · vpn · zero-trust [S5]
- Trust center: yes [S14]
- Two factor auth: yes [S2]
- Udp connect udp: CONNECT-UDP [S7]
- Udp route syntax: udp:// · udp+https:// [S7]
- Udp support version: yes · v0.29 [S7]
- Unified control plane: HTTP · TCP · UDP [S7]
- User claims in jwt: yes [S9]
- Verbose logging: verbose logging for auditing, managing, troubleshooting [S10]
- VPN replacement: yes [S7]
- Webauthn device identity limits: no · yes [S8]
- Zero managed control plane: Pomerium Zero is the managed control plane for Core clusters [S4]

**Subprocessors**
- Disclosure method: Subprocessor list available on request via privacy@pomerium.com [S2]

**Support**
- API contact email: support@pomerium.com [S13]
- Community channels: Discuss forum · GitHub issues · pomerium-announce [S4]
- Demo available: yes [S1]
- Docs resources: Documentation, resources, blog, Zero Trust Academy, customer stories available [S1]
- Status page: yes [S14]

2 more facts on the canonical page: https://whats-best.ai/software/business-vpn/pomerium

## Questions

### Is Pomerium European?

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

### Where does Pomerium store data?

Pomerium stores customer data outside the EU by default, per [the vendor’s page captured 10 Nov 2026](https://whats-best.ai/evidence/23330). The vendor’s pages mention the US as hosting location, per [the vendor’s page captured 10 Nov 2026](https://whats-best.ai/evidence/23330).

### Does Pomerium have a free plan?

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

### What are the best alternatives to Pomerium?

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: [Pomerium alternatives](https://whats-best.ai/software/business-vpn/pomerium/alternatives).

## What this page leaves out

- 7 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 integrations 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 compliance 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] Vendor page: https://pomerium.com (checked 2026-11-10)
- [S2] Privacy policy — found from the homepage: https://www.pomerium.com/privacy-policy (checked 2026-11-10)
- [S3] Security / trust page — found from the homepage: https://www.pomerium.com/customer-stories/obsidian-security (checked 2026-11-10)
- [S4] Self-hosting / on-premises installation docs — found from the homepage: https://www.pomerium.com/docs (checked 2026-11-10)
- [S5] Code repository (open-source licence) — found from the homepage: https://github.com/pomerium/pomerium (checked 2026-11-10)
- [S6] Access model & connectivity — found from sitemap: https://www.pomerium.com/learn/clientless-zero-trust-access (checked 2026-11-10)
- [S7] Access model & connectivity — found from sitemap: https://www.pomerium.com/docs/deploy/clients (checked 2026-11-10)
- [S8] Identity, access policy & device posture — found from sitemap: https://www.pomerium.com/learn/device-posture (checked 2026-11-10)
- [S9] Identity, access policy & device posture — found from sitemap: https://www.pomerium.com/docs/integrations/user-identity/oidc (checked 2026-11-10)
- [S10] Logs, audit trail & incident response — found from sitemap: https://www.pomerium.com/docs/capabilities/audit-logs (checked 2026-11-10)
- [S11] Logs, audit trail & incident response — found from sitemap: https://www.pomerium.com/docs/reference/access-log-fields (checked 2026-11-10)
- [S12] Deployment, API & administration — found from sitemap: https://www.pomerium.com/docs/deploy/terraform (checked 2026-11-10)
- [S13] Deployment, API & administration — found from sitemap: https://www.pomerium.com/docs/api/pomerium-api (checked 2026-11-10)
- [S14] Architecture, reliability & security assurance — found from sitemap: https://www.pomerium.com/learn/security-properties (checked 2026-11-10)
- [S15] Architecture, reliability & security assurance — found from sitemap: https://www.pomerium.com/learn/implicit-trust-zone (checked 2026-11-10)

---

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

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