Who builds Keymate

Keymate exists so that access is decided by policy and enforced on every request. You can prove it to your auditor. All of it runs on infrastructure you control.

• Authorization comes first.

  Access rules in application code cannot be reviewed or approved outside engineering, or proved to an auditor. Keymate keeps them as policies outside the code and decides every request against them. Why Keymate makes the full case.

• Self-hosted, with nothing reported back.

  Keymate runs on Kubernetes, wherever yours runs, including air-gapped networks (Enterprise). The product reports nothing back to us. None of your users, policies or audit evidence is sent to Keymate Inc.

• Built on Keycloak.

  Keymate builds its identity foundation on Keycloak, the CNCF open-source IAM project, instead of replacing it. If you run Keycloak today, your realms, clients and flows come with you into Keymate. They are not rebuilt.

Keymate is not open source. It has a free edition under its own license, Community, with every module for up to 100 registered users. Keycloak, underneath it, is open source.

Keymate engineers contribute fixes and features to Keycloak itself, because Keymate depends on the same project our customers run. Every merged pull request and every issue we opened is public in the Keycloak repository. The contributions page lists each one with a link. Its count comes straight from the repository.

• Candidates.

  Open roles and how to apply are on our careers page.

• Journalists.

  Logos, the brand name and brand colors are in the press kit. Send press questions to info@keymate.io.

On the contact page, choose a topic: demo and sales, support, partnership, careers or something else.