Companies that use Keycloak

Source: Analysis of job postings that mention Keycloak (using the Bloomberry Jobs API)

My analysis shows that Keycloak purchasing decisions are split between engineering leadership and platform teams. Directors of IT (7%) and Directors of Software Engineering (7%) are the primary buyers, focused on strategic priorities like building scalable identity platforms, reducing technical debt, and enabling secure multi-cloud deployments. VPs of Engineering (6%) appear in roles overseeing platform engineering and trust infrastructure, indicating that identity and access management is now considered foundational to business operations rather than a side concern.

The day-to-day users are overwhelmingly Backend Engineers (33%) and DevOps Engineers or SREs (26%). These practitioners are integrating Keycloak into microservices architectures, implementing OAuth2 and OIDC flows, managing authentication for containerized applications on Kubernetes, and building CI/CD pipelines that include identity services. They work hands-on with Spring Boot, Docker, AWS, and PostgreSQL, treating Keycloak as infrastructure code rather than a standalone product.

The job descriptions reveal companies are solving three core problems. First, they need "identity first security" and "Zero Trust environments where identity is the new perimeter." Second, they want to "eliminate friction" and enable employees to be "productive on Day 1." Third, they are building "AI-native products" and need secure authentication for ML pipelines and inference services. The consistent emphasis on air-gapped environments, multi-tenant architectures, and sovereign infrastructure suggests organizations are prioritizing control and compliance alongside developer experience.

Source: Analysis of Linkedin bios of 4,208 companies that use Keycloak

I noticed that Keycloak users span an incredibly diverse range of industries, but they share a common thread: they're building digital platforms that handle sensitive data and user access. These companies are creating financial services platforms (payment processors, fintech apps, mortgage lenders), developing software products (SaaS platforms, AI tools, e-learning systems), or digitizing traditional operations (utilities, government procurement, healthcare clinics). What unites them isn't what industry they're in, but that they're putting systems online that require secure authentication and identity management.

These companies skew toward the smaller and mid-sized range. Most have under 200 employees, with a significant cluster in the 11-50 range. Very few show venture funding, and when they do, it's typically seed or early-stage amounts. This suggests they're either bootstrapped companies achieving sustainable growth or established small-to-medium businesses undergoing digital transformation rather than high-growth startups burning through capital. The mix includes both newer companies (founded 2015-2020) and surprisingly mature ones that have been around for decades.

Source: Analysis of tech stacks from 4,208 companies that use Keycloak

I noticed that companies using Keycloak are heavily infrastructure-focused organizations with sophisticated self-hosted and internal tooling requirements. The presence of self-hosted Sentry, Grafana, and Zabbix tells me these are teams that prefer running their own infrastructure rather than relying solely on managed services. They're likely mid-market to enterprise B2B companies or technology organizations that need granular control over their authentication layer, often for compliance, customization, or cost reasons.

The pairing of Keycloak with Microsoft Entra ID is particularly revealing. These companies aren't choosing between identity solutions but instead building federated identity systems that bridge their internal applications with enterprise customer requirements. This suggests they sell to other businesses that demand SSO integration. The combination with Argo CD and self-hosted monitoring tools paints a picture of organizations practicing GitOps and running Kubernetes environments where Keycloak handles authentication for multiple microservices. Cloudflare Tunnels appearing frequently makes sense too, as these teams need secure ways to expose self-hosted services without complex VPN setups.

The full stack reveals engineering-led organizations in growth or mature stages. These aren't early-stage startups using off-the-shelf auth solutions. They're companies that have reached sufficient scale to justify the operational overhead of running Keycloak and its associated monitoring infrastructure. The presence of Grafana and Zabbix suggests dedicated platform or DevOps teams. This is product-led growth territory where the technical buying committee has significant influence, and where demonstration of technical capabilities matters more than traditional sales pitches.