Keycloak upgrades and migration
Upgrade or move Keycloak without breaking a single login.
Which of these sounds like your company?
Several versions behind
Every skipped version adds changes to handle at once.
Custom extensions and themes
Custom code may break on the new version.
Still on WildFly
The old distribution needs a new configuration setup.
Moving infrastructure
Keycloak has to move to Kubernetes or a new cloud.
No room for downtime
Logins must keep working during the switch.
No way back
Nobody knows how to roll back if something fails.
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
Check your setup
versions, extensions and integrations
- 02
Plan the path
step by step, with risks named
- 03
Rehearse
the full switch in a parallel environment
- 04
Switch
with rollback ready
Technical details
- Release and upgrade notes checked for every major version in between
- WildFly-based setups moved to the Quarkus-based distribution
- schema migration on a copy first with tested backup and restore
- custom SPIs, themes and authentication flows rebuilt and tested
- every OIDC and SAML client plus LDAP or Active Directory tested
- container images, Kubernetes manifests or Operator, cluster and cache settings, monitoring and health checks
Flexible to fit you
In place, or in a parallel environment
One jump, or step by step
Your own deployment, or the Keycloak Operator
On-premises, Kubernetes or cloud
We run it afterwards, or hand it over to you
Measured on the KPIs you set
You choose what success means. We measure it from day one.
Login success rate
Errors per application
Downtime at switch-over
Data lost (none)
FAQ
Often yes. The more you skip, the more changes land at once. We decide after the first check.
Often, with a parallel environment or rolling updates where your setup supports them.
Yes, including configuration for the Quarkus-based setup.
It depends on the complexity and scope of your project. We discuss it in the first call.
