KeycloakPro

Platform · Branding & Theming

Login pages that look like your product, not a default

We design and build Keycloak themes for sign-in, account management and email — on-brand, translated, accessible, and packaged so a Keycloak upgrade doesn't quietly undo your work.

  • Login, account & email themes
  • FreeMarker or Keycloakify (React)
  • Localized and accessible

Standards & integrations

  • FreeMarker
  • Keycloakify
  • React
  • PatternFly
  • CSS custom properties
  • WCAG 2.2

Overview

Your login page is part of your product

For many users, the sign-in screen is the page of your product they see most often. Keycloak's theme system lets you change all of it — layout, copy, styling, emails — but heavy template overrides are also a common reason upgrades go wrong. We build themes that extend Keycloak's base themes instead of replacing them, so your branding stays intact release after release.

What we deliver

  • Login theme covering every authentication screen
  • Account console and email templates in your branding
  • Theme source in your repository (FreeMarker or Keycloakify)
  • Message bundles for each supported language
  • Accessibility review of login and registration flows
  • Theme packaged in your Keycloak image with an upgrade checklist

Capabilities

What Branding & Theming covers

Configured, tested and documented on upstream Keycloak — then handed over or operated by us.

  • Login and registration

    Sign-in, registration, password reset, MFA and passkey screens styled to your brand, with copy that matches your product's voice.

  • Two ways to build

    FreeMarker templates that extend Keycloak's base theme, or React components with Keycloakify when your front-end team wants to reuse its own design system.

  • Account and email themes

    An account console and transactional emails — verification, password reset, security notifications — that look like they came from you.

  • Per-realm and per-client branding

    Different themes per realm or per client, plus organization-aware branding built into the theme so B2B customers can see their own identity at sign-in.

  • Localization and RTL

    Keycloak message bundles and realm-level translation overrides for every language you support, including right-to-left layouts for languages such as Arabic and Hebrew.

  • Accessible by default

    Sufficient colour contrast, visible labels, clear error messages and full keyboard navigation, checked against WCAG guidance before each release.

How it works

From first call to production

  1. Design the flows, not just the colours

    We work from your design system to cover every screen users can reach — errors, expired links, MFA enrolment — not only the happy-path login.

  2. Build on Keycloak's base themes

    Themes extend the current base theme and override as little as possible, with previews for review across locales, browsers and screen sizes.

  3. Package and ship with the image

    The theme is built into your custom Keycloak image, versioned with it, and checked against each new Keycloak release before an upgrade goes live.

Use cases

Where teams put it to work

  • Consumer and SaaS products

    A sign-in and sign-up experience that feels native to your app, so users don't hesitate at an unfamiliar-looking page.

  • Multi-brand companies

    Separate realms or clients for each brand, each with its own login theme, all served from one Keycloak deployment.

  • International and public-sector products

    Translated pages, right-to-left support and accessible forms for products that serve many markets or have strict accessibility requirements.

FAQ

Branding & Theming questions, answered

FreeMarker or Keycloakify — which should we use?

FreeMarker is Keycloak's native templating and suits light-touch branding. Keycloakify lets a React team build themes with the tools and components it already uses, which pays off for heavily customized or multi-brand login experiences.

Will our theme survive a Keycloak upgrade?

Themes that extend a base theme and override only what they must are far more resilient than copied templates. We keep overrides minimal and review each release's template changes before you upgrade.

Can different customers see different branding?

Yes — through a theme per realm or per client, or, within a single realm, organization-aware branding built into the theme. We recommend the model that fits how your tenants are structured.

Can you customize the emails Keycloak sends?

Yes. Email themes control the HTML and plain-text versions of verification, password reset and other messages, and they're translated the same way as the login pages.

Ready to roll out Branding & Theming?

Walk us through your requirements on a free strategy call. We'll come back with an architecture, a delivery plan and a fixed scope.

Browse all products