Flamingo Raises $4.5M to Get MSPs Out of the Ticket Queue

Skip to content
Keycloak logo

Keycloak

Identity and Access Management (IAM)

Open Source
E
Enterprise
Self-hosted
OpenMSP Score
55
40
Reddit Impact Score
Github Score
2B
37KStars
9KForks
32KCommits
Apache License 2.0License
Nov 19, 2026Last commit

Alternative Vendors

Keycloak is a free, open-source identity and access management server, licensed under Apache 2.0, that adds single sign-on, multi-factor authentication and user management to applications. It started at Red Hat, with a first commit in July 2013, and has been a Cloud Native Computing Foundation (CNCF) incubating project since April 2023. Every feature ships in the one free distribution; there is no paid edition. Status as of 3 November 2026: Keycloak has been on major version 26 since October 2024 and ships a minor release every quarter. The 2026 minors were 26.5 (January), 26.6 (April), 26.7 (July) and 26.8 (1 October), and the current release is 26.8.1 from 13 October 2026. Recent additions that are now fully supported include organizations (26.0), recovery codes (26.3), passkeys in the login forms (26.4), Workflows for user and application lifecycle automation and zero-downtime patch upgrades (26.6), and a SCIM API for users and groups plus multi-cluster deployments without an external cache (26.8). Keycloak covers single sign-on and single sign-out over OpenID Connect, OAuth 2.0 and SAML 2.0. It brokers logins to external OpenID Connect, SAML and OAuth 2.0 providers and social logins, and federates users from LDAP, Active Directory and Kerberos. MFA options include OTP, recovery codes, WebAuthn security keys and passkeys, with step-up authentication for sensitive apps. Authorization Services add role-, attribute- and policy-based access control, and Fine-Grained Admin Permissions delegate admin rights over specific users, groups, clients and organizations. Themes restyle the login, account and email pages, and Java service provider interfaces (SPIs) add custom authenticators and user stores. Setup: for a first test, one Docker command starts Keycloak in development mode on port 8080 from the official image (quay.io/keycloak/keycloak:26.8.1, start-dev) with KC_BOOTSTRAP_ADMIN_USERNAME and KC_BOOTSTRAP_ADMIN_PASSWORD set. That admin is temporary and lives in the master realm, so create a permanent admin and keep the master realm for administration only. Development mode uses a built-in file database that is not for production. A production server runs the start command with TLS, a hostname, a reverse proxy and a supported database: PostgreSQL 14 to 18, MySQL 8.0 or 8.4, MariaDB 10.6 to 11.8, SQL Server 2019 or 2022, or Oracle 19c or 23. The ZIP distribution runs on Linux or Windows with OpenJDK 17, 21 or 25, and the container image uses OpenJDK 21; running kc.sh build in a Containerfile gives a faster-starting image. On Kubernetes and OpenShift, the Keycloak Operator installs through OperatorHub or kubectl, or through an experimental Operator Helm chart on Quay, and handles clustered setups and realm imports. The sizing guide starts at about 1,250 MB of RAM per instance, including caches and 10,000 sessions, plus 1 vCPU for every 15 password logins per second. Pricing, checked 3 November 2026: Keycloak has no license fee and no paid tier. Commercial support comes through the Red Hat build of Keycloak, the successor to Red Hat Single Sign-On. It is included with Red Hat Runtimes, Red Hat Application Foundations and OpenShift Container Platform subscriptions, counts against their cores, and is not sold on its own. Red Hat builds its versions from the even-numbered community minors (26.0, 26.2, 26.4, 26.6) and patches each for about 12 months. Neither the project nor Red Hat offers hosted Keycloak; third-party providers sell managed Keycloak, so check where they run it and how fast they apply patch releases. Security: the GitHub repository published 17 security advisories in 2026 as of 3 November, 12 of them rated high, including several in SAML brokering and dynamic client registration in August. Patch releases arrive every few weeks, so self-hosted instances need a regular upgrade window. AI and MCP: Keycloak can act as the OAuth 2.0 authorization server for Model Context Protocol (MCP) servers, with an MCP guide since 26.5, experimental Client ID Metadata Document support (required by MCP version 2025-11-25) since 26.6 and a Claude Code setup guide since 26.7. In 26.8, token exchange delegation (preview) lets a user give an AI agent a consent-based token that names the agent as the actor, without admin rights. For MSPs and IT teams: a realm per customer keeps each customer's users, apps, identity providers, login flows and branding separate on one server. Organizations inside a single realm suit customers that share one app: each organization can have its own members, identity providers and groups (26.6), with dedicated admin roles for delegated organization management (26.7). Keycloak can broker sign-in to a customer's Microsoft Entra ID or Google Workspace, or give your staff SSO into self-hosted RMM, PSA and documentation tools. Plan for upgrades, database backups and retesting themes and extensions after each minor release. Alternatives on OpenMSP: authentik has an MIT-licensed core plus separately licensed Enterprise code, flow-based login customization and outposts that run inside customer networks. Zitadel (AGPL-3.0) is written in Go with organizations for multi-tenancy built in, and also runs as a hosted cloud. Apereo CAS (Apache 2.0) and Gluu, built on the open-source Janssen Project, are other long-running single sign-on servers. FreeIPA (GPLv3) covers Linux identity with LDAP, Kerberos and DNS. Microsoft Entra ID and Okta are the hosted options when customers already run Microsoft 365 or want no identity servers to maintain. Outside the directory, Authelia (Apache 2.0) is a lighter forward-auth portal with OpenID Connect, configured in YAML, and Ory Kratos and Hydra (Apache 2.0) are API-first building blocks with a hosted Ory Network.
image media

Key Features

Admin & User Management Consoles

Comprehensive admin console for centralized management and user account console for self-service profile and security management

MFA and passkeys

OTP, recovery codes, WebAuthn security keys and passkeys, configured per realm through authentication flows, with step-up authentication.

SCIM provisioning

SCIM 2.0 API for creating and managing users and groups per realm from external systems; supported since 26.8 (October 2026).

Realms and organizations

Separate realms isolate users, clients and settings per tenant; organizations add B2B members, identity providers and groups inside one realm.

Kubernetes Operator

Official Operator through OperatorHub or kubectl, or an experimental Operator Helm chart, for clustered, highly available deployments and realm imports.

Single Sign-On (SSO)

Users authenticate once with Keycloak and gain access to multiple applications without re-entering credentials, supporting single sign-out as well

Pros and Cons

Pros

Completely Free & Open Source

Apache 2.0 license with every feature in the free distribution; no paid feature tier

Enterprise-Grade Features

SSO, MFA and passkeys, federation, fine-grained authorization and SCIM without premium tiers

Standards Compliance

Built on industry standards (OpenID Connect, OAuth 2.0, SAML) ensuring broad compatibility and interoperability

Highly Scalable

Supports clustering and high availability with the Kubernetes Operator

CNCF project with Red Hat support

CNCF incubating project since April 2023, with commercial support through the Red Hat build of Keycloak

Cons

Complex Setup & Configuration

Requires significant technical expertise to properly configure, deploy, and manage in production environments

Infrastructure Management Overhead

As self-hosted solution, requires ongoing maintenance, updates, monitoring, and infrastructure management

Learning Curve

Steep learning curve for administrators and developers due to extensive feature set and IAM complexity

Resource Intensive

Java server plus a relational database; the sizing guide starts at about 1,250 MB of RAM per instance

Frequent security patches

17 GitHub security advisories published in 2026 as of 3 November, 12 rated high, so self-hosted instances need prompt patching

Feature Comparison

Features
Cost and Licensing
Loading the comparison

Comments

No reviews yet. Be the first to share your experience with Keycloak.

Frequently Asked Questions

/vendor/keycloak