← All guides

Managed WordPress hosting

Deploy WordPress without assembling PHP, MariaDB, storage and Kubernetes yourself

AnchorScape recognises WordPress as a complete stateful workload. It combines the application image, database, uploaded media, security profile, domain and recovery evidence in one guided hosting pipeline.

Result: A WordPress or WooCommerce site running through dev, staging and production with persistent media, managed MariaDB and a visible recovery/readiness trail.

Start a WordPress deployment

The shortest path

  1. 1From the dashboard choose A WordPress or WooCommerce site.
  2. 2Select the client application and create dev with Managed WordPress preselected.
  3. 3Choose the repository or clean source ZIP and start the deployment.
  4. 4AnchorScape detects WordPress, prepares the pinned production runtime, provisions MariaDB when required and wires the database credentials.
  5. 5Test the private dev URL, then promote the same release through staging and production.
  6. 6Add and verify the client domain; AnchorScape provisions TLS.

What the managed WordPress profile adds

  • A pinned official WordPress/PHP runtime running as a restricted, non-root workload.
  • A dedicated MySQL-compatible MariaDB service and application credentials.
  • Persistent wp-content/uploads storage that survives application releases.
  • WordPress-aware edge controls: XML-RPC disabled by default, PHP blocked in upload/cache paths and configuration files denied.
  • Dashboard file editing and modification disabled so code changes follow the release pipeline.
  • A Recreate rollout that respects single-writer persistent storage instead of mounting it into competing pods.

Backup and recovery are part of the same screen

  1. 1Open Environments → Databases → Backup & recovery.
  2. 2Create a recovery point. For WordPress it contains both the SQL database and uploaded media.
  3. 3Create a separate non-production recovery environment with the same workload and MariaDB engine.
  4. 4Select that target, type the displayed RESTORE confirmation and restore the recovery point.
  5. 5AnchorScape verifies checksums, restores both artifacts and records the successful recovery test.
  6. 6The production-readiness panel stays incomplete until deployment, MariaDB, paired backup, restore evidence, domain and off-cluster storage are all present.
A local recovery point is useful for testing but does not count as an off-cluster production backup. Configure S3-compatible object storage before accepting live customer data.

Existing sites and email

For an existing WordPress site, collect the source, database export, uploads, plugin/theme inventory, scheduled jobs and external integrations before cutover. Website hosting does not create human mailboxes: connect a mailbox provider for SMTP/IMAP, forwarding when that is sufficient, and a transactional provider for forms, password resets and WooCommerce messages.

Need help on the screen?

Open Anchorton and ask where a setting belongs. For runtime questions, open it from the deployment context so it can use the permitted status, event and log tools.