Keycloak themes, extensions and custom login flows
Keycloak adapted to your brand and your processes, built to survive upgrades.
Which of these sounds like your company?
Off-brand login pages
Login and account pages don't look like your product.
A missing login step
You need a check or flow Keycloak doesn't offer.
Users in another system
Accounts live in a database or legacy system.
Extra data in tokens
Your apps need customer or tenant IDs in the token.
Login events unmonitored
Security teams can't see login activity.
Customisations block upgrades
Old extensions keep you on an old version.
Don't see your challenge? Let's discuss your use case.
Book a call →How we work on your use case
Pick the challenge that matters most. We take it from there.
- 01
Define
what Keycloak must do differently
- 02
Build
themes or extensions, separate from core
- 03
Test
with your apps and new Keycloak versions
- 04
Hand over
documented, or maintained by us
Technical details
- Login, account, email and admin themes with FreeMarker or React (Keycloakify), responsive and accessible
- custom authenticators and login flows
- User Storage SPI for databases, APIs and legacy systems
- token mappers for extra claims
- event listeners streaming to SIEM or logging tools
- extensions versioned and tested against each Keycloak release
Flexible to fit you
FreeMarker or React-based themes
Configure first, extend only where needed
Users federated, or migrated
Works with your current Keycloak version
Your team maintains it, or we do
Measured on the KPIs you set
You choose what success means. We measure it from day one.
Login success rate
Login page load time
Upgrades without code changes
Login-related support tickets
FAQ
Yes, for login, account console and emails, responsive and accessible.
They can. We keep them separate from core and test them against each release.
Yes, through user federation, without copying them.
It depends on the complexity and scope of your project. We discuss it in the first call.
