Keymate

Our contributions to Keycloak

Keymate engineers contribute fixes and features to Keycloak itself, because Keymate depends on the same project you run. Since December 2025, 5 Keymate engineers have had 22 pull requests merged into the Keycloak repository and have opened 28 issues there. Every one is listed below with its link to GitHub, so you can read the change and the review yourself.

Book a demoSee how it compares

The figures

FigureCount
Pull requests merged into keycloak/keycloak22
Pull requests open for review6
Issues opened in keycloak/keycloak28
Keymate engineers with a merged pull request or an issue5
Counted from the repository on23 October 2026

The counts come from the public Keycloak repository on GitHub at every build. How the figures are kept current explains each one.

Merged pull requests

Below is every pull request from a Keymate engineer that Keycloak's maintainers reviewed and merged, newest first. Each entry shows:

  • its title and number, linked to GitHub
  • the date it was merged
  • the Keycloak area it touches and the release it shipped in, from the area/ and release/ labels of the issue it closes, where there is one

Issues we opened

Below is every bug report and proposal a Keymate engineer has opened in Keycloak's public issue tracker. Each entry shows the issue title and number, linked to GitHub, and whether it is open or closed. Where a pull request closed it, that is shown too.

Pull requests under review

Pull requests still under review by Keycloak's maintainers are listed separately and are not counted as merged. A pull request closed without merging is not listed.

One example: composite roles on a cache miss

In issue #50369, a Keymate engineer reported a problem with composite roles. When the roles were not in Keycloak's cache, expanding them sent one database query per role in the tree. Under concurrent token and permission requests, this took most of Keycloak's CPU. The issue records measurements from a prototype fix across three workloads: database queries per second fell by 79 to 89 percent, and CPU use by 54 to 64 percent. Pull request #50370 replaced the per-role lookups with one batched query per level of the role tree. A Keycloak maintainer added caching on top of it and merged it on 30 June 2026. It shipped in Keycloak 26.7.0. Teams that move to Keymate still run this part of Keycloak.

How the figures are kept current

No count or list on this page is typed by hand. At every build, the site asks GitHub's public interface for every pull request and issue in keycloak/keycloak opened by Keymate engineers' GitHub accounts. It also checks the commit history for commits authored with a keymate.io email address. That way, a commit from an account missing from our list still shows up for review.

The counting rules:

  • Merged pull requests: pull requests merged into keycloak/keycloak by Keycloak's maintainers. A backport to an older release branch is listed under the original change and counted once.
  • Issues opened: issues a Keymate engineer opened, whether now open or closed.
  • Contributors: Keymate engineers with at least one merged pull request or one issue in the repository.
  • Not counted: reviews of other people's pull requests, comments, and pull requests closed without merging.

If GitHub cannot be reached during a build, the page keeps the previous figures and shows the date they were counted.

Further reading

  • Keycloak Authorization Services: how Keycloak's own authorization engine uses resources, scopes, policies and permissions to decide permit or deny, with links into the Keycloak source.

Questions

Does Keymate contribute to Keycloak?

Yes. Since December 2025, 5 Keymate engineers have had 22 pull requests merged into the Keycloak repository and have opened 28 issues there. Each one is listed on this page with its link to GitHub, and the figures are counted from the repository every time the site is built.

Is Keymate open source?

No. Keymate has a free edition under its own license, with every module for up to 100 registered users. Keymate is built on Keycloak, which is open source under the Apache License 2.0, and Keymate's engineers contribute changes to it upstream. Keymate vs Keycloak shows what Keymate adds.

How are Keymate's Keycloak contribution figures counted?

At every build of the site, from GitHub's public record of the keycloak/keycloak repository: pull requests merged by Keycloak's maintainers, issues opened by Keymate engineers, and the engineers behind them. Reviews and unmerged pull requests are not counted. A change copied to an older release branch (a backport) is counted once.

See what these engineers build on Keycloak.

Book a demoSee how it compares