Service type
App service
App service
Keycloak service
Self-hosted Keycloak identity service for application authentication and single sign-on, with linked PostgreSQL storage.
Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.
Overview
Technical profile and packaging
This page shows how Keycloak is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.
Versions
26.8
Source repository
Public Helm chart
Ports and protocols
8080/HTTP, 9000/HTTP
Labels
keycloak, identity, authentication
Stacks
Use it inside ready-made stacks or your own
These public stacks already include Keycloak as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.
Runtime wiring
Reuse connectivity, storage, and runtime defaults
This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.
Endpoints
8080/HTTP, 9000/HTTP
Technical domains
HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.
Service links
These links define which other services can connect to Keycloak when it is used inside a stack.
postgres
Eligible linked services