Managed Application Platform
4SO Enterprise WordPress
A managed WordPress platform on self-owned infrastructure with RKE2, database, cache, storage, edge and a unified operator and user experience.
- RKE2
- Managed runtime
- Backup & recovery
- Access
- Operator UX
The problem
Problem
A platform-grade WordPress service must coordinate clusters, stateful services, backup, domains, access and upgrades without making users operate every runtime detail.
Why It Is Hard
A simple UX must not hide reliability and recovery; stateful components and edge services have different lifecycles that need coordination in one workflow.
The decision
Leadership / Architecture Role
Selected RKE2 and a product-owned control plane to reduce complexity, defined node lifecycle and kept console operations API-first.
Key Decisions
Avoid bringing OKD and complex bare-metal subsystems into this product, remove internal authoritative DNS and keep runtime independent from an external workflow engine.
The architecture
Architecture
RKE2 runtime with a product-owned API and control plane; database, cache, object storage, TLS/WAF and backup are composed capabilities with explicit owners.
Failure & Recovery Model
Backup and restore, node lifecycle and application recovery need explicit paths, and the console shows observed state only.
Security / Authority Model
RBAC, audit, domain and TLS verification, secret handling and tenant boundaries are part of the product surface from the start.
The value
Product Experience
Cluster and stateful-service complexity sits behind a simpler site-lifecycle journey while operator and customer views remain task-oriented.
Value Created
Multiple infrastructure capabilities become a managed application service, moving daily operations away from SSH and fragmented knowledge.
The boundaries
Trade-offs
RKE2 is preferred over a more complex distribution to keep the operational surface smaller, which means some capabilities remain product-owned.
What Was Intentionally Excluded
A heavy build plane, internal authoritative DNS, runtime dependency on Tekton or Argo Workflows and complexity without direct value are intentionally excluded.
Truth boundary
Current Truth / Limitations
The product surface shows observed data only; unavailable telemetry or runtime state is never replaced with fabricated values.
designed → source implemented → runtime tested → production certified
Each level is claimed separately; a lower level never implies a higher one.
Start a conversation
If technology should move your organization forward rather than hold it back, let’s talk.
The first conversation is about your problem, not about me: where you are stuck, what is at stake and whether I am the right person to solve it.
Bring the problem