Which of these sounds like your company?
Nobody owns it
Keycloak runs, but no one is responsible for it.
Login outages
When Keycloak fails, every connected application fails.
Updates keep slipping
Security patches wait for someone with time.
Growing user numbers
Performance needs tuning as you grow.
Knowledge in one head
Only one person knows how it's set up.
Must stay in your cloud
Third-party hosting isn't an option.
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
Take over
review and document your setup
- 02
Stabilise
monitoring, backups and patches in place
- 03
Run
updates, tuning and support
- 04
Improve
regular reviews with your team
Technical details
- Health checks, metrics and login monitoring with alerts
- planned version updates and security patches for Keycloak and extensions
- clustered Keycloak with shared caches and database on Kubernetes or virtual machines
- database, cache and JVM tuning with load tests
- database and configuration backups with restore tests
- one ticket channel for incidents, changes and questions
Flexible to fit you
Support only, or full operations
Your infrastructure, your cloud or on-premises
Single instance, or cluster
Response times agreed in your SLA
Your custom extensions included
Measured on the KPIs you set
You choose what success means. We measure it from day one.
Uptime
Time to respond
Patch level
Login response time
FAQ
Yes, Keycloak is open source with no licence fees. Costs come from running and supporting it.
We operate it in your infrastructure or cloud account, so you keep control of the data.
Yes, including tests for each new Keycloak version.
It depends on the complexity and scope of your project. We discuss it in the first call.
