Skip to main content

WordPress

Managed WordPress is a project service with persistent uploads, plugins and themes, a dedicated database on a MariaDB service, and an HTTPS address. It is available to paid organizations.

Create a site​

Open Services → Create Service → WordPress. Enter a service name, site title and administrator email. Choose an existing MariaDB service in the project, or create one with the site. SailOps reserves a separate database and database user for this WordPress instance; other applications on the MariaDB service keep their own data.

Select compute and content storage. WordPress runs one instance and needs at least 500 mCPU and 1 GiB of memory. Content storage starts at 1 GiB and can grow. The MariaDB volume is separate. The site stays private during installation and receives its HTTPS address when it is ready.

The selected database and storage class are fixed after creation. Change the site title and administrator email in WordPress itself. Use Edit to change compute, grow content storage or configure backups.

Administrator and application access​

Open Credentials to reveal the initial administrator password once. Store it before leaving the page. Reset password changes that account's password and returns the replacement once. If the original account has been deleted or no longer has administrator privileges, SailOps refuses the reset; it does not recreate the account.

Manage content, plugins, themes and users in the WordPress dashboard. SailOps manages the WordPress core version; dashboard and automatic core updates are disabled. Only versions offered in the service catalog are accepted.

A connection from a container or Job exposes WORDPRESS_URL and WORDPRESS_INTERNAL_URL. It does not expose administrator passwords or MariaDB credentials. The internal address is for applications in the project; the public address remains WordPress's canonical URL.

Stop, restart and project suspension​

Stop withdraws public access and stops WordPress and its scheduled tasks. Files and database data remain. Start restores access after the site is ready. Restart briefly interrupts the site without changing its files or database.

Project suspension also pauses backup and restore work before stopping MariaDB. Resume starts the database first. A site that you had already stopped stays stopped. An interrupted restore may fail safely with its new site remaining private: delete that target and restore again from the protected source backup.

Backups and restoration​

The Backups tab captures the site's dedicated SQL database and its content files as one restore point. A MariaDB-only backup does not contain WordPress uploads, plugins or themes.

A backup briefly takes the site offline to keep its files and database consistent. After capture, the site returns to its previous running or stopped state. Failed capture does not produce a usable restore point.

In Edit → Backups, enable an automated schedule in UTC and choose retention from 1 to 30 days. Scheduling is disabled by default; the default retention is seven days. Retention changes apply to new backups. Existing backups keep their expiration dates. Manual backups use the same retention policy. Expired backups are removed automatically, except while an active restoration or upgrade uses them. A service can retain up to 200 backup records.

Choose Restore on a ready backup and enter a new service name. The restored site gets a new content volume, dedicated database, HTTPS address and administrator password. The source site remains unchanged. Links stored in WordPress are rewritten for the new address, including serialized values. Reveal the new password in the restored site's Credentials tab.

The console restores with the source service's current resource shape and MariaDB service. The API can select another existing MariaDB service in the same project and a different flavor or storage size. Target storage cannot be smaller than the backed-up content volume.

Supported database contents

Site backups currently refuse SQL views, routines, triggers and scheduled database events. They do not report an incomplete dump as a successful backup. The combined backup allocation is limited to 4 TiB.

Managed core upgrades​

Open Version to see the installed and currently offered core versions. An upgrade first takes a fresh paired backup, then keeps the site private while updating the pinned runtime and database schema. After verification, a running site reopens and a stopped site stays stopped. Check plugin and theme compatibility before confirming the maintenance interruption.

The recovery backup remains protected until the upgrade completes. If migration fails, the site stays private and Version identifies the protected backup. Restore that backup into a new service from Backups, verify it, and then delete the failed service. A runtime image rollback alone cannot recover the database. Legacy versions are available for paired recovery, but cannot be selected when creating a new empty site.

The update API and services_wordpress_update accept a supported newer version with the current revision. Submit version changes separately from resource or backup-policy changes. Read the service's upgrade field for its phase and recovery backup ID. Capture failure before migration resumes the original site; its failed backup is visible in Backups, and the upgrade can be requested again.

Custom domains​

Create the site on its platform address, then open Domains. Configure your hostname on an existing project Gateway with an HTTPS listener and a ready certificate. Point the hostname's DNS to that Gateway. Publish this TXT record:

  • Name: _sailops-wordpress.<your-hostname>
  • Value: sailops-wordpress=<WordPress-product-ID> (shown in the console)

Choose the hostname and Gateway, then confirm Verify and change domain. SailOps checks ownership, DNS, certificate and global hostname availability before accepting the change. Gateway usage and the recovery backup are billed separately.

The operation takes a fresh paired backup, closes access, updates serialized internal links and publishes the new canonical address after verification. A stopped site remains stopped. Use platform address performs the same safe operation in reverse. Detach the custom domain before changing its Gateway or listener. A failed change stays private; restore its protected backup into a new site from Backups. Third-party settings outside WordPress, such as OAuth redirects or external DNS, remain your responsibility.

The update API and services_wordpress_update accept customDomain with hostname and gateway, separately from version or resource changes. Set both strings to empty to return to the platform URL. Omit the field to preserve the binding. The read-only domainChange describes progress and recovery backup. New and restored sites need their own product-specific DNS proof.

API and automation​

The project Public API exposes WordPress under /api/v1/services/wordpress. For a service named site:

Method and path suffixOperation
GET /site/backupsList restore points and expiration
POST /site/backupsRequest a paired backup
DELETE /site/backups/{backupId}Request permanent backup deletion
POST /site/backups/{backupId}/restoreRestore with a body such as {"name":"site-copy"}

Mutations are asynchronous: inspect service and backup status for completion. Concurrent changes are refused while another operation is pending. Stacks accept a backup policy with enabled, schedule and retentionDays. MCP provides services_wordpress_backups_list, services_wordpress_backups_create, services_wordpress_backups_delete and services_wordpress_backups_restore.

Deletion and billing​

Deleting a WordPress service permanently removes its site files, retained backups and dedicated database. Deletion is refused while a restoration uses one of its backups. The MariaDB service remains unless it was created with the site, has no other dependents and you explicitly choose to delete it too.

WordPress compute, content storage and the MariaDB service are billed separately. Stopping WordPress stops its compute billing; retained storage and MariaDB remain billed. Backup and restore Jobs, temporary volumes and retained snapshots also contribute to usage. See usage tracking.

Logs, Observability and Alerts show runtime health and resource usage. Application content and user activity are managed in WordPress.