Someone to run Keycloak, without moving it out of your cloud
Grootan monitors, patches, tunes and supports your Keycloak, so your team can get back to the product.
Sound familiar?
Which of these sounds like your team?
It runs, but whose job is it?
Keycloak has no named owner on your team.
A single point of failure
Your apps all rely on it for sign-in, so a Keycloak outage is an outage everywhere.
Security releases pile up
Applying them keeps losing out to feature work.
Load you didn't plan for
Your user numbers have outgrown the settings Keycloak was first tuned with.
If one colleague leaves
The only person who knows the setup takes that knowledge with them.
Your data, your infrastructure
Your security or compliance rules keep identity data off third-party servers.
Process
How we work
- 01
Learn your setup
Before we touch anything, we write up how your Keycloak is built and why.
- 02
Close the obvious gaps
Alerts, tested backups and current patches come first.
- 03
Day-to-day running
Upgrades, performance work and your team's questions all come to us.
- 04
Look back and adjust
At set check-ins with your team, we decide what to change next.
Specifics
Technical details
- Alerts fire when health checks fail, metrics drift or logins start failing
- Keycloak upgrades and security fixes are rolled out on a plan, and your extensions are rebuilt and retested each time
- When one node isn't enough, we run a cluster on VMs or Kubernetes, with a shared cache and database
- Load tests show where the bottleneck is, whether the database, the cache or the JVM, and we tune that layer
- We back up the database and realm configuration, and prove the backups work by restoring them
- Outages, change requests and how-do-I questions all go through the same ticket system
- Your SLA states how quickly we must react to each kind of issue
Options
Flexible to fit you
- We answer when your team gets stuckorWe take over running it entirely
- Keycloak lives in a cloud account you ownorKeycloak lives in your data centre
- A lone Keycloak serverorSeveral nodes working as a cluster
Measurement
What we measure
- Hours Keycloak is up and serving logins
- How long you wait before an engineer picks up a ticket
- Security fixes released but not yet applied
- How quickly users get through the login screen
FAQ
Questions we hear
Where does the money go with Keycloak?
Not on licences, since it is open source. You pay for the people and infrastructure that keep it running.
Does Keycloak end up on Grootan's servers?
No. It stays in your cloud account or data centre and we work on it there, which keeps the data under your control.
What about the extensions we wrote ourselves?
They are included. No Keycloak upgrade goes live until they pass on it.
How is support priced?
The scope of the service and the complexity of your setup set the price, and our first call is where we go through both.
Let us take Keycloak off your team's list
Related
More Keycloak services
- Upgrading and Migrating KeycloakUpgrade Keycloak with a tested rollback
- Identity Provider MigrationLeave Auth0, Okta or Azure AD B2C safely
- Custom Keycloak DevelopmentBranded login screens and custom extensions
- Keycloak Security AuditA risk-ranked review of your setup
- Keycloak Multi-TenancyServe many customers from one deployment