
What Is a Realm in Keycloak? What Lives Inside One
A Keycloak realm is an isolated tenant with its own users, clients and signing keys. What a realm holds, what…

Keycloak resource requirements: a 2 GB memory limit, 2 vCPU and PostgreSQL cover a homelab. Official sizing math and an N100 compose file.
Read the article →
A Keycloak realm is an isolated tenant with its own users, clients and signing keys. What a realm holds, what…

authentik vs Keycloak for a single mini-PC: footprint, forward auth, LDAP, realms, backups and licensing comp…

Why Keycloak returns 403 behind a proxy, rejects redirect URIs, and issues tokens with the wrong issuer, and …

Learn Keycloak's RAM and hardware requirements: 1250 MB per-pod baseline, heap at 70% of the container limit,…

A protocol, architecture and footprint comparison of three self-hosted identity servers, and the deployment s…

A Keycloak realm is an isolated tenant with its own users, roles, clients and signing keys. Learn when to use…
Four guides, in the order the questions usually arrive: how to structure a realm, why nothing works behind the proxy, how much memory the thing actually needs, and whether Keycloak is the right choice at all.
Turn a peak session count into an Infinispan cache footprint, a per-node JVM heap, the container limit that heap needs, and a node count. Every constant it uses is listed on the page. Runs in the browser, no signup.
Open the calculator