Application hosting

Hosting Keycloak

Keycloak provides identity and access management. Production deployments need a supported Java runtime, a production database, TLS, and a configured hostname; hardware sizing depends on load.

Min vCPU
Depends on workload
Min memory
Depends on workload
Min storage
Depends on workload

Must have

Hard prerequisites

No universal server-size prerequisite is published. Check the exact release and configuration before you deploy.

Recommended

Documented guidance

No further general recommendations are published for this version.

Capacity depends on your workload

Keycloak does not publish one universal host size. Account volume, login rate, sessions, and clustering determine capacity; use load-specific sizing.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Official container image
  • Bare-metal or virtual-machine installation

The host must provide

Runtime

Java
Supported OpenJDK 17, 21, or 25 in current documentation
Database
Production-grade supported database; development file database is unsuitable for production
Transport
TLS and configured public hostname for production mode

Storage

Persistent data

Persistent database storage, logs, backups, and optional cluster data need sizing for the actual identity workload. A universal disk minimum is not documented.

Step by step

Keycloak deployment outline

  1. Choose supported runtime and database

    Check the Keycloak supported-configurations guide for the intended release and database version.

    Official instructions
  2. Configure production transport

    Set the public hostname, TLS, a production database, and appropriate reverse-proxy boundaries before starting in production mode.

    Official instructions
  3. Validate readiness and recovery

    Use the documented readiness endpoint, restrict administration, and test database backup recovery.

    Official instructions

Security

Before you go public

  • Use TLS for all identity traffic.
  • Restrict administrative endpoints and protect bootstrap credentials.
  • Use a production database and test recovery before handling real accounts.

Cost

Beyond the server price

  • Budget for database, backups, TLS termination, monitoring, and capacity for peak login traffic.
  • High availability adds multiple instances and shared infrastructure.

Matching plans

Plans with published evidence

DigitalOcean

CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB

2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
  • Dedicated CPU
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

DigitalOcean

General Purpose Droplet · 2 Dedicated vCPU / 8 GB

2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
  • Dedicated vCPU (100% allocatio...
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-medium · 2 vCPU / 4 GB

2vCPU
4 GBRAM
—Storage
—Transfer
  • Shared vCPU (1.00 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-small · 2 vCPU / 2 GB

2vCPU
2 GBRAM
—Storage
—Transfer
  • Shared vCPU (0.50 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX13 (Germany and Finland)

2vCPU
8 GBRAM
80 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX23 (Germany and Finland)

4vCPU
16 GBRAM
160 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX33 (Germany and Finland)

8vCPU
32 GBRAM
240 GBStorage
30 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX43 (Germany and Finland)

16vCPU
64 GBRAM
360 GBStorage
40 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX53 (Germany and Finland)

32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX63 (Germany and Finland)

48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX11 (US locations)

2vCPU
2 GBRAM
40 GBStorage
1 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX12 (Germany and Finland)

1vCPU
2 GBRAM
40 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.