1. 4SO
  2. Products
  3. Enterprise WordPress

Managed WordPress platform

4SO Enterprise WordPress

Every site is a managed resource, from creation to recovery.

Turns WordPress from a standalone installation into a Platform Resource; Identity, Infrastructure, Storage, MySQL, Valkey, Edge, Observability, Capacity, recovery and Security sit under one Product Control Plane.

  • Self-contained
  • API-first
  • Multi-tenant
  • Backup / PITR
4SO Enterprise WordPress flow: Provision, Publish, Scale, Protect, Recover.
Who it is for
Organizations with many WordPress sites that want to run all of them to one standard of security, backup and capacity.
What it does
Site creation, domain and TLS, clone and staging, backup and point-in-time recovery (PITR), capacity and safe updates, all under role-based access.
Where it runs
Self-hosted on RKE2 with a three-node production core, MySQL, Valkey and built-in observability; extends to multiple regions.
SAFE UPDATE · PROMOTE / ROLLBACKUpdating a site on a canary first, then on the live site
01

The live site keeps serving while the update request is recorded and checked for compatibility.

01Problem

Enterprise WordPress is not a CMS; it is a platform lifecycle.

When Site, Domain, Storage, Database, Cache, Update, Security and Backup are operated with separate tools, every site becomes an operational island. This product turns them into manageable resources in a self-hosted PaaS.

  1. 01

    A Site needs organizational context

    Organization, Project, Role and Site define access boundaries and Ownership from the start.

  2. 02

    Site infrastructure is part of the product

    Storage, MySQL, Valkey, Edge and Observability are managed as Platform services.

  3. 03

    Recovery should not be an emergency runbook

    Backup, PITR, Clone, Staging and Resume are product-owned, traceable paths.

  4. 04

    Updates require Preflight and Verification

    Content or runtime changes are made with a clear Impact, Generation and Result.

02Capabilities

Every layer of a WordPress Platform, in one product model.

The focus is the site lifecycle: creation, Domain binding, capacity, Update, recovery, Security and day-to-day operations.

  1. 01

    Site Management

    Create, Suspend/Resume, Clone, Staging and the lifecycle of every Site.

  2. 02

    Organization, Project and RBAC

    User and Operator access on product-owned boundaries.

  3. 03

    Storage Platform

    Storage lifecycle and Policy for site Data and backups.

  4. 04

    Database and Cache

    Data services under the Platform lifecycle and capacity.

  5. 05

    Domain, TLS and Edge

    Domain Binding, HTTPS and Edge policy within the Site management path.

  6. 06

    Observability and APM-lite

    Health, Metrics, Logs and operations from the Site's point of view.

  7. 07

    Capacity and Scaling

    Capacity Policy and Scale decisions matched to the workload.

  8. 08

    Recovery, Access and Security

    Backup/PITR, Access grant, Security policy and Safe Update.

4SO

Panel, API and AI/MCP are not three separate decision authorities. All of them work on the same Product RBAC and Durable Operations, so no interface can bypass the lifecycle.

03Deployment model

The Production core starts at three nodes and grows as a Platform.

The WordPress runtime sits on a self-hosted Foundation; sites are built on the same Platform, and Capacity or Region expand without changing the user model.

ProfileFoundationSite runtimeUse
Production Core3 nodesSites on Platform ServicesEnterprise baseline with infrastructure HA
Scale-outCore + added nodesBroader Site CapacityMore capacity without building a separate Platform
Staging / CloneSame product authoritySeparate environments for Test/recoveryChange testing, Clone and controlled transfer
Multi-regionProduct-defined regionsPlacement and Edge matched to the RegionSite distribution and recovery across multiple failure domains
04Lifecycle

From Create to recovery, a Site is a live Resource.

The lifecycle covers Setup, Domain, Capacity, Update, Backup, recovery and Security, not just the initial WordPress installation.

  1. 01PreparationPreflight
  2. 02Create SiteCreate
  3. 03Domain and TLSBind
  4. 04OperationOperate
  5. 05CapacityScale
  6. 06Safe UpdateUpdate
  7. 07MonitoringObserve
05Profiles

Site, recovery and Platform each have a defined process.

Users do not need to manage Kubernetes details or the underlying services for day-to-day work.

  • Site Operations

    Day-to-day work for each Site.

    • Create / suspend / resume
    • Domain / TLS
    • Health / operations summary
  • Safe Update

    Controlled change of Managed Content and the runtime.

    • Preflight
    • Schedule / campaign
    • Verification / recovery
  • Recovery

    Recovery and creation of an environment separate from Production.

    • Backup / PITR
    • Clone
    • Staging / promotion workflow
  • Capacity

    Resource management based on Policy and Usage.

    • Capacity policy
    • Workload profile
    • Scaling decisions
  • Edge & Security

    The Site's public boundary and security policy.

    • Domain binding
    • Edge policy
    • Security posture
  • Access & AI

    Human and agentic access under the same RBAC.

    • Access grants
    • Delegated MCP
    • No direct shell/SQL authority
Technical reference

Architecture, workflows and operations in detail

For engineers who want to know how the product works underneath: components, boundaries, failure behavior and the operations it runs.

06Architecture

A Site is operated on top of a set of Platform Services.

The Control Plane holds Intent, RBAC and Operations; the Infrastructure, Storage, Data, Edge and recovery layers execute change, and the Site runtime shows the result.

  1. EXPERIENCE
    User / Operator / API / MCPMultiple interfaces on one product authority and Permission Model.
  2. AUTHORITY
    Organization / Project / SiteRBAC, Durable Operations, Audit and Generation.
  3. PLATFORM
    Infrastructure · Storage · MySQL · Valkey · Edge · ObservabilityThe services beneath a Site, under the Platform's own lifecycle.
  4. SITE RUNTIME
    WordPress SitesThe actual Site runtime, Domain, Health and observed state.
LayerComponent / PlaneResponsibilityOperational behavior
FoundationRKE2Self-hosted platform runtime and node lifecycleThe Platform is built and verified before any Site
IdentityKeycloak / OIDC + Product RBACDelegated identity and Organization/Project/Site authorizationThe identity provider does not replace the Product permission model
Data PlaneMySQL + ValkeyPersistent site data and cache/session accelerationData services have their own lifecycle and capacity
Storage / EdgePlatform storage + Domain/TLS/Edge planesPersistent content, public binding and request edgeDomain and storage are part of the Site lifecycle
ObservabilityVictoriaMetrics · Loki · Alloy · GrafanaMetrics, logs and operator visibilitySite health is built from telemetry and runtime read-back
RecoveryBackup · PITR · Clone · StagingPoint-in-time recovery, isolated verification and promotionRestore is a product workflow, not an emergency command
TECH

Install Authority. Production installation starts from a sealed artifact and operator-owned intent; before bootstrap, Remote Doctor assesses every target without mutation.

StageAuthority / ComponentBehavior
Artifact admissionTrusted SHA256 + sealed release preparerThe hash is checked before extraction, and exact archive/tree parity is verified again after extraction.
Operator intentNormalized install configNode/IP/role/data-device, URLs and SSH host-key fingerprints are explicit; the installer guesses none of them.
Remote admissionRead-only Remote DoctorThe independent SSH fingerprint and target readiness are confirmed before bootstrap/runtime mutation; TOFU is not accepted.
FoundationRKE2 → Authority/Identity → StorageThe Platform foundation is built and read back before Site services.
Data / EdgeMySQL → Valkey → Edge → WordPressData, cache and public edge are part of the same Platform lifecycle.
Day-2 planesObservability → Capacity → Recovery → Access → SecurityInstallation is complete only when the operational planes are also available after runtime.
Operator handoffCredential-free handoff metadataThe Panel/Identity URL and the owner-only credential path are handed off; no password/token is printed in the handoff or logs.
07Workflows and failure

Every change is one traceable chain, from request to verified result.

A Site mutation is bound to a specific generation through an Idempotency-Key and request fingerprint; DR, Plan Migration, Runtime Transition and Recovery lifecycles can fence general Site changes.

  1. 01IntentREQUESTED
  2. 02DispatchOUTBOX PENDING
  3. 03ReconcileRUNNING
  4. 04ObserveGENERATION READ-BACK
  5. 05SuccessCOMPLETED
CANARY BRANCH

Safe Update with Promote / Rollback

Staging and Canary prove the change path before Cutover.

UPDATE INTENT
↓
STAGING + CANARY
↓
HEALTH
PASS?
PROMOTE
↙ ↘
ROLLBACK
A Canary failure never reaches Cutover, and rollback authority must be valid.
RECOVERY FORK

PITR in an isolated environment

Restore first builds Clone/Staging, then Promote or Abort.

RECOVERY POINT
↓
RESTORE + REPLAY
↓
CLONE / STAGING
↓
APP
VERIFY
PROMOTE
↙ ↘
ABORT
Active Recovery fences overlapping lifecycles.
GENERATION LOOP

Intent ↔ Observed Generation

A Site is Ready only when generation and dependencies converge.

TARGET
GENERATION
→
RECONCILE
↓
READ
BACK
↑
OBSERVED
GENERATION
←
DATA · CACHE
EDGE · RUNTIME
Site intent stays bound to the same Durable Operation and Generation.
Missing telemetry or dependency = unknown, not Ready.
  1. Flow 01

    Create Site

    A Site is a multi-layer resource, not just a container.

    1. Org / Project
    2. Plan / Region
    3. Storage
    4. MySQL / Valkey
    5. WordPress Runtime
    6. Observed Generation

    Failure and recoveryGeneration is not considered converged until Data/Cache/Runtime are ready.

  2. Flow 02

    Domain + TLS

    Public edge is part of the same Site's lifecycle.

    1. Domain Intent
    2. Ownership / DNS
    3. Certificate
    4. Edge Binding
    5. HTTPS Probe
    6. Activate

    Failure and recoveryInvalid TLS or DNS stops activation.

  3. Flow 03

    Safe Update

    Change is proven in staging/canary before cutover.

    1. Update Intent
    2. Compatibility
    3. Backup Checkpoint
    4. Staging
    5. Canary Verify
    6. Promote

    Failure and recoveryGeneration drift or an invalid rollback fingerprint makes the operation stale.

  4. Flow 04

    PITR / Clone

    The recovery point is first verified in an isolated environment.

    1. Select Point
    2. Recovery Fence
    3. Restore / Replay
    4. Clone / Staging
    5. App Verify
    6. Promote / Abort

    Failure and recoveryRestore never reaches Promote without App Verify.

  5. Flow 05

    Capacity / Scale

    Scale passes through telemetry and placement authority.

    1. Observe Load
    2. Policy
    3. Capacity Admit
    4. Place
    5. Scale Runtime
    6. Health Read-back

    Failure and recoveryMissing telemetry means neither healthy nor a definite need to scale.

Additional operational flows

Migration and Site deletion must also have explicit, recoverable lifecycles.

  1. Flow 06

    Plan Migration

    Plan or Runtime changes run with a checkpoint and a controlled cutover.

    1. Source / Target
    2. Compatibility
    3. Capacity Gate
    4. Backup Checkpoint
    5. Stage Target
    6. Sync / Canary
    7. Cutover Verify

    Failure and recoveryGeneration drift or a Canary failure triggers Block/Rollback of the operation, and Cutover never happens without Verification.

  2. Flow 07

    Delete Site

    Deleting a Site is a destructive action with a Fence and an ordered release of dependencies.

    1. Exact Confirmation
    2. Recovery Fence
    3. Deletion Requested
    4. Dependency Order
    5. Release Data / Edge
    6. Observed Deprovision
    7. Audit Close

    Failure and recoveryActive Recovery or Migration blocks Delete; Success is recorded only after dependency Deprovision is observed.

Action / FlowAdmission / PreconditionsExecution / LockSuccess CriterionFailure / Recovery
Create / Reconcile SiteOrg/Project/Plan/Region, generation and platform readiness must be validSite intent + Operation + Outbox + Audit are bound to one resource/generationObservedGeneration converges with TargetGeneration and data/cache/storage/application readinessA failed Operation is terminal; only explicitly resumable runtime families can move Failed→Running
Suspend / ResumeThe Site is not deleted and no DR/Recovery/Plan Migration/Runtime Transition fence is activeNew generation + durable Operation + site.reconcile outboxObserved Site state converges with the suspension intentA conflict is rejected with 409 instead of overwriting; idempotent replay returns the same request
Safe Update / Runtime TransitionValid compatibility, staging canary and rollback checkpoint/fingerprintThe target PHP/runtime transition is bound to the exact staging/backup authorityCanary/target runtime and generation verification before cutoverDrift in generation or rollback authority makes the operation stale/blocked
Backup / PITRProvable recovery point and data-plane compatibilityThe recovery request/operation passes through the same Product authorityRestored Site/Data and runtime health are confirmed before promotionActive Recovery fences other overlapping lifecycles; failure has its own recovery path
Plan MigrationSource/Target Plan and usage/capacity admissionRequested → Reconciling → Prepared → CompletedPlan cutover only after project/site dependencies are readyFailed can enter RollbackRequested → RollingBack → RollbackPrepared → RolledBack
Delete SiteconfirmSiteId must equal the exact Site ID and purgeData=true; active recovery is not allowedThe Site is suspended and DeletionRequested + durable Operation/Outbox/Audit are recordedDependencies are released and deprovisioning is observedA repeated Delete or an overlapping lifecycle does not overwrite; destructive intent is explicit and generation-bound
FLOW

* Resume is not universal. Only operation types with a durable runtime generation and a defined resume owner can move from Failed back to Running; for all others, the terminal state is immutable.

08Operations catalog

Operators work with Sites and Outcomes, not with Kubernetes components.

Instead of exposing backend entities, the Panel shows the processes needed to operate WordPress.

  • Create SiteCreate a Site in an Organization/Project and connect it to a Plan and the Platform.
  • Bind DomainDomain binding, Verification and TLS.
  • Scale CapacityChange capacity based on Policy and actual state.
  • Safe UpdatePreflight, Apply and Verification for managed changes.
  • Backup / PITRRecovery points and restoring a Site to a specific point in time.
  • Clone / StagingBuild a separate environment for Test, recovery or Promotion.
  • Access GrantLimited, revocable access to a Site.
  • Inspect & RecoverOperations timeline, Incidents and recovery from one Site Cockpit.

Run WordPress as a platform, not a collection of servers and plugins.

4SO Enterprise WordPress brings Site, Data, Edge and recovery operations together under one experience.