What's the difference between self-hosted Keycloak and Cloud-IAM?
The answer depends on the size of your Ops team as well as its level of maturity on DevOps practices.
To get your self-hosted Keycloak running you need to consider:
- Installation
- Configuration management
- Supervision and alerting
- Backups
- Patch Management
- Upgrade management, each new version must be qualified
- Security hardening and infrastructure updates
When our Cloud-IAM expert team setup self-hosted Keycloak clusters for our consulting clients, it can take between 20 and 25 days of work, which we often see spread over a 2 months period (minimum) in order to setup 2 environments (staging and production).
This estimate includes knowledge transfer and it ends when the consulting client starts to connect its applications to the production IAM.
With Cloud-IAM you get a battle tested, production ready Keycloak cluster in 1 hour.
To get your self-hosted Keycloak running you need to consider:
- Installation
- Configuration management
- Supervision and alerting
- Backups
- Patch Management
- Upgrade management, each new version must be qualified
- Security hardening and infrastructure updates
When our Cloud-IAM expert team setup self-hosted Keycloak clusters for our consulting clients, it can take between 20 and 25 days of work, which we often see spread over a 2 months period (minimum) in order to setup 2 environments (staging and production).
This estimate includes knowledge transfer and it ends when the consulting client starts to connect its applications to the production IAM.
With Cloud-IAM you get a battle tested, production ready Keycloak cluster in 1 hour.
Updated on: 19/11/2021
Thank you!