Pomerium Proxy

Pomerium is an identity- and context-aware reverse proxy that provides secure, clientless access to internal web applications and services without a corporate…

  • Network Services
  • Security
Pomerium is an identity- and context-aware reverse proxy that provides secure, clientless access to internal web applications and services without a corporate VPN. It continuously verifies user identity and enforces access policies before granting entry, making it a practical zero-trust option for homelab and small-team remote access.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 16 days ago
Popular
745,090 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
5,090
Open issues
167
Last commit
2026-11-05
Latest release
v0.34.0
License
Apache-2.0
Activity
steady

Checked 16 days ago - source: GitHub (pomerium/pomerium)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Kubernetes install needs kubectl access Run the kubectl apply command from a machine with kubectl (the Kubernetes command-line tool) able to reach your cluster, because if it cannot, the install never starts. The command follows the evergreen main branch, which can change, so check whether a stable release is available before relying on it. source
  • Set TLS, secrets, and config first Set the CERTIFICATE, CERTIFICATE_KEY, and COOKIE_SECRET environment variables and mount your config file to /pomerium/config.yaml before starting Docker Compose. Pomerium needs these for TLS (HTTPS) and secure cookies, so missing or default values can stop it from starting or make sign-in unsafe. source
  • Allow the web ports you use The Docker example maps port 443 for Pomerium and 8443 for the example mutual-TLS service, so make sure those ports are reachable from your browser or firewall. If the ports are blocked, Pomerium may be running but you will not be able to open its HTTPS pages. source

Fetched 53 days ago - each note links to its source

Alternatives (1)

  • pocket-id - A simple OIDC provider that allows users to authenticate with their passkeys to your services.

Checked 39 days ago - source: AlternativeTo

Common questions

Which environment variables and config file must be in place before starting the Pomerium Docker example?

Set CERTIFICATE, CERTIFICATE_KEY, and COOKIE_SECRET and mount the config file to /pomerium/config.yaml before starting Docker Compose. Missing or default values can stop Pomerium from starting or make sign-in unsafe.

What can prevent the Pomerium Kubernetes install command from starting?

Run kubectl apply from a machine with kubectl able to reach the cluster, because if it cannot, the install never starts. The command follows the main branch, so check whether a stable release is available before relying on it.

Can Pomerium secure a self-hosted Open WebUI installation?

Yes, Pomerium can run Open WebUI behind it with SSO and trusted-header identity.

What route-facing feature did Pomerium v0.29.0 add?

It includes a built-in routes portal page for the proxy.

What authentication issue can occur with a self-hosted authenticate service using Google?

After about one hour, when the Google access token expires, the authenticate service may not reauthenticate the user and can redirect back with the same access token.

Answers sourced from discuss.pomerium.com, github.com, github.com, groups.google.com, www.pomerium.com

Community

Collected 48 days ago - public community threads