Back to Tech landscape

Keycloak

Backend

Open-source identity and access management

Official documentation (opens in a new tab)

Overview

Keycloak provides OIDC and SAML identity when clients or products need a portable IdP—Factory templates default to Microsoft Entra ID and OpenIddict for .NET-native auth servers.

Factory templates and SaaS platform programs standardize on .NET 10, Clean Architecture, and Azure-native services—so generated solutions inherit consistent security, observability, and upgrade paths instead of one-off frameworks.

When a client estate or integration boundary calls for this technology, we wire it with explicit ownership, contract tests, and telemetry—without diluting the Factory baseline your long-term platform depends on.

Planning a backend on Azure with predictable releases? Our stack choices are documented, template-backed, and ready to extend—talk to us about mapping your domain to a production-grade .NET platform.

Why we use it:

  • Realm per tenant or environment
  • Client scopes aligned with API audiences
  • Brute-force and session policies
  • Federation to Entra or LDAP documented
  • Aligns with ASP.NET Core hosting and OpenAPI contracts in our templates
  • Observability hooks for Application Insights and OpenTelemetry
  • Clear Factory default versus client-specific adoption boundaries

Ready to work with us?

Let's discuss how our team can help achieve your digital goals