Pomerium is a tool for managing secure access to internal applications and resources.
Pomerium alternatives and similar tools
Based on the "Identity Management" category.
Alternatively, view Pomerium alternatives based on common mentions on social networks and blogs.
5.0 8.4 L3 Pomerium VS OpenIDOpenID Certified™ OpenID Connect Relying Party implementation for Apache HTTP Server 2.x
5.0 9.7 L2 Pomerium VS Sambahttps://gitlab.com/samba-team/samba is the Official GitLab mirror of https://git.samba.org/samba.git -- Merge requests should be made on GitLab (not on GitHub)
4.7 9.4 L2 Pomerium VS FreeIPAMirror of FreeIPA, an integrated security information management solution
2.5 8.6 Pomerium VS BounCABounCA is a web tool to generate self-signed SSL certificates and setup a key infrastructure
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Pomerium or a related project?
Pomerium is an identity-aware proxy that enables secure access to internal applications. Pomerium provides a standardized interface to add access control to applications regardless of whether the application itself has authorization or authentication baked-in. Pomerium gateways both internal and external requests, and can be used in situations where you'd typically reach for a VPN.
Pomerium can be used to:
- provide a single-sign-on gateway to internal applications.
- enforce dynamic access policy based on context, identity, and device identity.
- aggregate access logs and telemetry data.
- a VPN alternative.
For comprehensive docs, and tutorials see our documentation.
To run the integration tests locally, first build a local development image:
Next go to the
integration/clusters folder and pick a cluster, for example
google-single, then use docker-compose to start the cluster. We use an environment variable to specify the
dev docker image we built earlier:
cd integration/clusters/google-single env POMERIUM_TAG=dev docker-compose up -V
Once that's up and running you can run the integration tests from another terminal:
go test -count=1 -v ./integration/...
If you need to make a change to the clusters themselves, there's a
tpl folder that contains
jsonnet files. Make a change and then rebuild the clusters by running:
go run ./integration/cmd/pomerium-integration-tests/ generate-configuration
*Note that all licence references and agreements mentioned in the Pomerium README section above are relevant to that project's source code only.