Skip to content

Upgrade On Demand โ€‹

Our Upgrade On Demand feature allows you to easily upgrade your Keycloak SaaS deployment to a newer version directly from your dashboard.

Need Assistance? โ€‹

If you prefer our support team to handle the upgrade process or assist you at any step, please don't hesitate to contact usโ€”we're always here to help!

Who Can Use This Feature? โ€‹

Deployments without Custom Extensions โ€‹

  • You can safely and confidently use the Upgrade Self-Service feature.

Deployments with Custom Extensions โ€‹

  • Ensure your extensions are compatible with your chosen target Keycloak version.
  • If compatibility is unclear or adjustments are necessary, contact our support team to help manage your extensions.

Free Plan Users โ€‹

Free plan users are currently not able to initiate upgrades themselves, as these deployments run on a shared instance.

But donโ€™t worryโ€”our team works diligently to keep all shared instances up to date with the latest stable Keycloak versions, so you always benefit from the newest features and security updates without lifting a finger.

How the Upgrade Works โ€‹

Upgrading your deployment is straightforward:

  1. Go to your Deployment page.
  2. Select the Pilot tab within your deployment.
  3. Click the Upgrade tab within Pilot.
  4. Choose your desired Target Version.
  5. Specify when you'd like the upgrade to occur:
    • As Soon As Possible (immediate upgrade).
    • During your next scheduled maintenance window.
  6. Click Next Steps.
  7. Review and consent to the upgrade terms (an automatic backup is always performed).
  8. Click Apply to initiate the upgrade.

Once completed, your deployment will run on the selected Keycloak version.

Downtime Information โ€‹

We aim for the upgrade process to be as seamless as possible. However, certain Keycloak upgrades may require brief downtime, especially when a cluster restart is necessary.

Refer to the table below to identify target versions that may involve downtime:

Target VersionDowntime Required?
21Yes
21.1Yes
22Yes
23Yes
24Yes
25Yes
26Yes
26.1No
26.2No

Important: If your upgrade spans multiple versions and any intermediate version requires downtime, your upgrade will also involve downtimeโ€”even if the final version typically doesn't require it. For example, upgrading directly from version 21 to 26.1 will incur downtime because intermediate versions (22, 23, 24, and 25) require downtime.

Version Jumping โ€‹

You have full flexibility to upgrade directly to your desired version. There's no requirement to incrementally upgrade one version at a time!


If you have further questions or special scenarios, please reach out to our support team.