Pomerium
changelog-20261012-68827fa7 commercialThe section your link pointed to isn't on Pomerium's page any more, so we've brought you to the top.
Pomerium is an identity-aware proxy that provides secure, clientless access to internal applications by enforcing context-based authentication and authorization policies.
https://app.example.com/dashboard?pomerium_additional_hosts=api.example.com pomerium-console -directory-provider github -url https://console.corp.example.com ssh_upstream_tunnel: true ssh_allow_direct_tcpip: true ssh_routes_portal: true ssh_upstream_tunnel: true ssh_allow_direct_tcpip: true ssh_routes_portal: true
Summary
Pomerium is a commercial secure-access proxy that brokers identity-aware access to applications, SSH servers, and now AI agent (MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.) endpoints, running as a self-hosted service in front of the infrastructure it protects. It suits platform and security teams managing access for distributed or clustered deployments rather than individual developers, offering a hosted identity provideridentity providerA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. option so smaller teams can skip standing up an external OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. provider. Recent work extends it well past traditional reverse-proxy access control: SSH support now includes reverse tunneling for NAT'd edge devices, jump-host mode, an interactive routes portal, per-key session revocation with SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. lockout, and full session recording and playback through its Enterprise Console. MCP routes get equivalent treatment, with upstream OAuth discovery, dynamic client registration, and token refresh for long-running agent sessions. With 9 releases in the window tracked, the project shows steady, active development.
Pomerium is an identity-aware proxy that provides secure, clientless access to internal applications by enforcing context-based authentication and authorization policies.
How Pomerium helps
Which SSH servers behind NAT or on isolated networks can be reached without opening inbound firewall rules?
upstream servers dial out to Pomerium over a reverse tunnel, so a policy-authorized session can reach them without any inbound path being opened
Who actually did what during a privileged SSH session last month?
every keystroke and terminal output for that connection is captured and can be replayed from the Enterprise Console, stored locally or in an S3-compatible bucket
Can a compromised user's key still get back in after a session is revoked?
a deny/revocation list rejects the blocked user on every subsequent request, and a lockout option stops SSO from silently re-authenticating them
Which AI agent sessions are still connected without forcing someone to log in again?
OAuth refresh tokens are issued and proactively renewed for MCP sessions, keeping long-running agents connected and reauthenticating upstream tokens before they expire
Which destinations is a given user actually authorized to reach when they SSH in without naming a target?
the interactive routes portal lists only the routes that user's policy allows, presented as a picker at connection time
Does a new MCP client need to be manually registered before it can connect?
dynamic client registration and client ID metadata documents let compatible clients register themselves, falling back to discovery when the server doesn't support the metadata document approach
Languages
Command line
2 commands for Pomerium, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Pomerium, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Pomerium puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
26 entries
No entries match these filters.
- October 20262
- August 20263
- July 202617
- June 20261
- April 20261
- January 20262
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.