Skip to main content

Navigate Pomerium's website

Move confidently with agents

Ensure your agents never leak secrets, make unauthorized tool calls, or inherit overprivileged access – even in multiplayer agentic environments.

Pomerium does this by making sure all actions are deterministically enforced for correct context and intent outside the non-deterministic boundary.

All while staying out of your users' way and capturing compliance-ready, evidence-based logs.

A pale marble relief of a Roman authorization gate, where an official signals that entry is approved.

Trusted by the world's most innovative, security-first organizations.

Mercedes-Benz logoObsidian Security logoOpenAI logoNVIDIA logoCrusoe logoRecursion logoOptoro logoAhold Delhaize logoZendesk logoUber logoOkta logoStellenbosch University logo

Start with an identity-aware proxy

Secure private applications and infrastructure with identity, context, and policy on every request.

Explore how Pomerium works

  1. Authenticate

    Sign in with your existing identity provider.

  2. Authorize

    Evaluate identity, context, and policy on every request.

  3. Access

    Enforce governance, compliance and log access decisions based on proxy-approved requests to private applications and services.

Secure agentic access, without compromising velocity or usability

Long lived sessions, credential sharing and unscoped access. Pomerium eliminates all 3 of these, without slowing down your developers' existing workflows.

Multiplayer support

Easily and quickly collaborate with pre-existing workflows.

Sam and Alex investigate the same incident in Slack. They share the work, while Pomerium keeps each person's permissions and private context separate.

Slack#incident-api-prod

api-prod returning 5xx

Sam

@agent Which customers were hit?

Shared Slack agent

Only visible to Sam

142 accounts affected

Customer details stay in your private context.

Alex

@agent So who was affected?

Shared Slack agent

Permission denied

Viewing customer records requires customers.read access.

  1. Request access from the data owner.
  2. Retry after approval.

You can still read the incident.

Pomerium

Checks context and intent

For Sam

customers.read

Allowed

For Alex

customers.read

Blocked

Shared Slack agent

Shared incident context

api-prod returning 5xx

incident.read

Sam and Alex can both read the incident.

Sam's private context

Customer records

customers.read

Not added to Alex's context

Scoped access

Eliminate credential leakage and over-privileged agents.

During the task

Alex

Investigate why api-prod is returning 5xx.

Read-only access for this task

Pomerium checks each call

  1. Read api-prod logslogs.read
    Allowed

    Within this task's read-only access.

  2. Restart api-prodservices.restart
    Denied

    Outside this task's permissions. Request approval from the service owner.

Short-lived sessions

Pomerium automatically spins down resources once tasks are completed.

When the task ends
  1. Summary delivered

    Private reply to Alex.

  2. Runtime stopped

    Task resources shut down.

  3. Access expired

    This session can no longer read api-prod logs.

logs.readExpired

Infrastructure agnostic

Use any model provider, LLM gateway or harness with Pomerium's plug-and-play architecture.

Pomerium
  • Claude
  • OpenAI
  • LangChain
  • Google
Explore Agentic Access Management

How customers use Pomerium today

Pomerium is flexible and can be deployed wherever your workloads run. Have a different use case you want to use Pomerium with? Let us know!

Clientless access

Replace your corporate VPN. Access internal apps, services and agents without client software or layer 4 networking.

Policy as code

Easily manage your policies via Git.

Securing Kubernetes

Eliminate overprivileged kubectl access.

Airgapped SSH access and recording

Protect and monitor access to mission-sensitive workloads with SSH session recording.

No-bullshit zero trust.We have the receipts.

It's only zero trust if it does per-action authorization.Otherwise, it's just a sparkling VPN.

Use the left and right arrow keys to view each source.

  • NIST

    Zero Trust Architecture

    SP 800-207 - 2020

    least privilege per-request access decisions

    Why it matters: NIST defines one access decision for each request. Pomerium checks each protected request before it sends it upstream.

    Read SP 800-207
    NIST SP 800-207 excerpt about per-request access decisions
    Read SP 800-207

  • GOOGLE

    BeyondCorp

    A New Approach + The Access Proxy - 2014-2016

    service-level authorization ... on a per-request basis

    Why it matters: BeyondCorp puts each access decision in front of the service. Pomerium uses this proxy model for each protected request.

    Read BeyondCorp
    BeyondCorp paper excerpt about service-level authorizationBeyondCorp Access Proxy paper excerpt about per-request authorization
    Read BeyondCorp

  • THE WHITE HOUSE + CISA

    Federal Zero Trust Strategy

    OMB M-22-09 + CISA Maturity Model v2

    every request for access should be evaluated

    Why it matters: Federal guidance requires a decision for each request. Pomerium can use identity and request context in that decision.

    Read M-22-09
    OMB M-22-09 excerpt about evaluating every access requestCISA Zero Trust Maturity Model excerpt about application authorization
    Read M-22-09

  • NIST

    Application-Level Zero Trust

    SP 800-207A - 2023

    application-level action and verb

    Why it matters: NIST matches policy to an HTTP method and path. Pomerium can check both before it sends the request upstream.

    Read SP 800-207A
    NIST SP 800-207A excerpts about application actions and Layer 7 policy
    Read SP 800-207A

  • GOOGLE

    Beyond Zero

    Enterprise Security for the AI Era - 2026

    Individual actions on individual resources

    Why it matters: Beyond Zero defines one decision for each action on a resource. Pomerium can use the HTTP method and path for each protected request.

    Read Beyond Zero
    Beyond Zero paper excerpt about individual actions on resources
    Read Beyond Zero

  • POMERIUM

    Authorize each HTTP action in plain YAML

    Pomerium is proudly open source under Apache 2.0.

    Why it matters: Give a user one HTTP method and path, not the whole application. Pomerium checks the rule on each request before it reaches the application.

    Read PPL on GitHub
    Pomerium Policy Language
    allow:
  and:
    - email: alice@example.com
    - http_method: POST
    - http_path: /deploy
    Authorize before the upstream
    filters := []*...HttpFilter{
  ExtAuthzFilter(...),
  ...
}
filters = append(filters,
  HTTPRouterFilter())
    Read PPL on GitHub

THE REVIEWS ARE IN

Customers rate Pomerium highest in zero trust access

POMERIUMHighest Rated
POMERIUMEasy to Use
POMERIUMEasy to Integrate
POMERIUMFast to Deploy
POMERIUMStrong Community
POMERIUMOpen Source
4.8/5See all reviews
ContendersLeadersNicheHigh PerformersSATISFACTIONMARKET PRESENCEMicrosoft Entra Application ProxyOkta Access GatewayCloudflare AccessPACisco Duo Network GatewayZscaler Private AccessCYBERARKNTwingateTeleportTailscaleF5 BIG-IP APMstrongDMGoogle Identity-Aware ProxyHashiCorp BoundaryNGINX with OAuth2 Proxy

FEEDBACK

What Our Users Think About Pomerium

Read customer stories

Get a Personalized Demo

Schedule a Call with a Pomerium Engineer

Get a Demo