Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Dex review

Free#9 of 33 in OAuth Server Software

A focused, open-source OIDC and OAuth layer for Kubernetes federation.

8.5/10Editor score
Visit Dex
Dex8.5 Visit Dex

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Dex is an open-source, self-hosted federated identity service for applications that need OpenID Connect and OAuth 2.0 authentication. It connects applications to upstream identity providers and directories through pluggable connectors, including LDAP, SAML, GitHub, Google, Microsoft, and other OIDC providers. Its strongest fit is lightweight Kubernetes OIDC federation, particularly where teams want a focused identity layer rather than a broader IAM suite. Dex can run as a container, Kubernetes workload, systemd service, or compiled binary in infrastructure controlled by the operator.

Its protocol coverage extends beyond basic login. Dex supports OAuth 2.0 authorization and token flows, client-credentials authentication for server-to-server communication, token exchange, device-code grants, and a token introspection endpoint. Custom scopes and ID-token claims support application-specific identity data, while the gRPC API enables programmatic state management. These capabilities make Dex relevant for both user authentication and machine-to-machine scenarios, with integrations spanning directory, enterprise, social, and OIDC-based identity sources.

Deployment flexibility is a practical advantage, but the self-hosted model places infrastructure and configuration responsibilities with the operator. The SAML connector also deserves caution: it is documented as unmaintained, potentially vulnerable, and under consideration for deprecation. Teams whose federation requirements center on SAML should account for that limitation when evaluating alternatives. Choose Dex for a focused, open-source OIDC and OAuth service that fits Kubernetes-oriented infrastructure; choose a broader IAM product when the requirement extends beyond its narrower verified scope.

Dex pros and cons

  • Where it wins
    • Supports OIDC, OAuth 2.0, token exchange, introspection, and device grants
    • Connects with LDAP, SAML, GitHub, Google, Microsoft, and OIDC
    • Offers container images and Kubernetes Helm deployment
  • Where it doesn't
    • Requires self-hosted deployment and operator-managed infrastructure
    • The documented SAML connector is unmaintained and may be deprecated
    • Narrower scope than full IAM suites

Dex fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update