OutlineWiki Keycloak OIDC Hardening & 768 MB JVM Sizing
Hostinger KVM NVMe
OutlineWiki 8GB pick (90,000 IOPS) — KVM 4 (4 vCPU / 16GB DDR5 / 200GB NVMe)
InterServer Price-Lock KVM & ZFS
Low-RTT node for outline Node.js + Hocu (19 ms CRDT sync)
UltaHost Dedicated EPYC VDS
Steady OutlineWiki secondary tier (25–100 collaborative editors)
Keycloak Quarkus requires 768 MB RAM headroom but satisfies strict enterprise MFA audits.
Regulated engineering teams already running Keycloak for GitLab, Grafana, and Kubernetes prefer reusing one realm for wiki authentication.
On OutlineWiki, we advise budgeting 768 MB for Keycloak Quarkus JVM (-Xms256m -Xmx512m plus metaspace) and enforcing PKCE S256 with WebAuthn MFA.
OutlineWiki Reference Configuration for Keycloak OIDC Token & Session Hardening
KC_HOSTNAME=sso.example.internal
KC_PROXY_HEADERS=xforwarded
KC_HTTP_ENABLED=true
JAVA_OPTS_APPEND=-Xms256m -Xmx512m -XX:MaxMetaspaceSize=160m
OutlineWiki Implementation Checklist: Keycloak OIDC Token & Session Hardening
Phase 1: Keycloak OIDC Token & Session Hardening
Cap Keycloak JVM heap at -Xmx512m with 160 MB metaspace so total container RSS stays near 768 MB.
Phase 2: Keycloak OIDC Token & Session Hardening
Enable Proof Key for Code Exchange (PKCE) Code Challenge Method S256 inside the Outline client Advanced tab.
Phase 3: Keycloak OIDC Token & Session Hardening
Set Access Token Lifespan to 5 minutes and SSO Session Idle to 8 hours for SOC 2 compliance alignment.
Phase 4: Keycloak OIDC Token & Session Hardening
Map Keycloak email_verified=true claim strictly so unverified accounts cannot auto-provision wiki seats.
OutlineWiki Infrastructure Recommendation for Keycloak OIDC Token & Session Hardening
Keep Keycloak realm database on a separate Postgres schema from Outline.
When teams combine Outline, Keycloak (768 MB), MinIO (512 MB), and PostgreSQL on a single host above 100 editors, we recommend stepping up to Hostinger KVM 4 (16 GB RAM at $19.99/mo promo) or UltaHost VDS Power for dedicated CPU isolation.
OutlineWiki Hardware Ledger: NVMe Throughput vs Base Price
Packet-to-Disk Path for outline Node.js + Hocuspocus Yjs CRDT + OIDC on OutlineWiki
[+] Key Infrastructure Pros
- Keeps outline.env buffers stable at 100 collaborative editors via 8GB compute.
- Protects 19 ms CRDT sync objectives under heavy Postgres tsvector document graph + MinIO assets writes (90,000 IOPS).
- Trims OutlineWiki 3-year infrastructure bills 70%–85% versus metered SaaS seats.
[-] Operational Constraints
- Unlocking $10.49/mo on Hostinger KVM NVMe depends on annual commitment rather than 1m billing.
- Base OS templates need outline.env tuning (WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150) before peak load.
Deploy This OutlineWiki Stack If
- DevOps squads standardizing outline Node.js + Hocuspocus Yjs CRDT + OIDC (100 collaborative editors) on KVM nodes.
- Builders needing root access to set WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150 in outline.env.
When To Choose Alternatives
- Two-day load tests where InterServer Price-Lock KVM & ZFS pay-per-hour beats annual commitments.
- Mandates requiring vendor-staffed 24/7 NOC contracts with zero SSH access.
$10.49/mo