Editorial desk
Keycloak Ops Editorial
Keycloak Ops Editorial is the publishing identity for Keycloak Ops. It is a desk, not a person: no named author, no biography, no professional certifications.
Articles published under this byline are researched from primary sources — vendor and project documentation, published standards and specifications, research papers, and measurements published by whoever took them — drafted with AI assistance, and edited against those cited sources before publication. Nothing here is based on first-hand testing in a private lab, and any figure that appears is attributed to the source it came from.
Corrections go to editor@keycloakops.com. More detail is on the about page and the editorial disclosure.
Posts (4)
- troubleshooting
Keycloak Behind a Reverse Proxy: Fix 403 and Hostname Errors
Why Keycloak returns 403 behind a proxy, rejects redirect URIs, and issues tokens with the wrong issuer, and the exact options that resolve each case.
- sizing
Keycloak Memory Usage and Heap Sizing Explained
Keycloak hardware requirements explained: RAM baselines, JVM heap and container limits, Infinispan session caches, and CPU sizing from login rates.
- comparisons
Keycloak vs authentik vs Authelia: What to Self-Host
A protocol, architecture and footprint comparison of three self-hosted identity servers, and the deployment shapes each one is actually built for.
- fundamentals
Keycloak Realms Explained: Clients, Roles and Tokens
What a Keycloak realm isolates, when to use one or several realms, and how clients, roles, scopes, sessions and tokens fit together.