hostingsurge
ENSVStart building

WORDPRESS

Managed WordPress. Changed safely.

WordPress as one surface of the same AI product: your site runs managed on the platform, and AI edits it inside scoped, revocable limits — with a preview, an approval step and a rollback behind every risky change.

Start buildingSee launch pricing

In development — managed WordPress and the Hostingsurge Connector are early access, and no WordPress instance exists yet. This page describes what the platform is built to do, not a service you can use today.

Two ways in

Either let the platform run WordPress for you, or keep your site exactly where it is and connect it.

Managed

WordPress, run on the platform

Managed WordPress is provisioned through the platform’s deployment provider. The standard build is WordPress with a MySQL/MariaDB database, persistent storage, resource limits, a domain with SSL and backup hooks — sized to the site and set up for you.

  • What you see in the dashboard: WordPress, Domains, Backups, Performance, AI, Staging, Logs.
  • The infrastructure vendor is never exposed — no vendor panel, no vendor terms.
  • Everything is reachable through the Hostingsurge API and UI.
Bring your own

Connect an existing WordPress site

The Hostingsurge Connector is a dedicated plugin that connects WordPress sites hosted anywhere to Hostingsurge AI. It uses the WordPress REST API with Application Passwords, or a stronger controlled auth flow where one is required.

  • The connection is revocable at any time and carries project-specific scopes.
  • Only approved capabilities are exposed — never a general remote-code channel.
  • Your hosting, domain and database stay where they are.

In the dashboard you work with Hostingsurge concepts only:

WordPressDomainsBackupsPerformanceAIStagingLogs

What AI can read — and what it can change

The Connector exposes only approved capabilities. This is the whole surface: a listed, narrow set instead of broad access to your site, and broad arbitrary remote-code execution is explicitly avoided.

Safe by default

A defined group of low-risk operations is safe enough to run without the full gate — and is still previewed before anything reaches your live site.

  • Content edits — text, images and copy
  • New pages built from your own block patterns
  • Metadata — titles, descriptions, structured data
  • Safe block edits in existing Gutenberg content

Approved Connector scope

  • Read scopeSite metadata, pages, posts, menus, media
  • Block dataGutenberg and block structure
  • InventoryPlugins and themes, read-only
  • DiagnosticsSelected checks and health information
  • Deliberately excludedArbitrary remote code execution

Risky changes go through a gate

PHP, theme files, plugins, checkout behaviour, database schema and critical ecommerce functionality never change directly. Every one of them runs the same pipeline, in this order.

  1. SnapshotA backup is taken first, so the change always has a way back.
  2. Staging cloneThe live site is cloned to staging, so the work happens where customers are not.
  3. The change itselfAI applies the change on staging — never straight onto the live site.
  4. Syntax and static checksCode-level checks run before anything is rendered.
  5. Health testsThe site has to come up healthy after the change.
  6. Browser testsReal browser runs against the staging site, desktop first.
  7. Mobile testThe same pages are checked on a mobile viewport.
  8. Visual diffBefore-and-after screenshots are compared, so unintended changes are caught.
  9. Your approvalNothing reaches production until you approve it.
  10. Selective deploymentOnly the approved parts are deployed — not a whole-site overwrite.
  11. Post-deploy checkThe live site is checked again after deployment.
  12. Rollback on failureIf the result is not clean, the change is rolled back.

In development. This pipeline is the designed contract for the WordPress module, not a service you can use today. Managed WordPress and the Connector are early access, and the module is work item C5 in the platform’s status document — no WordPress instance exists yet.

Live business records stay authoritative

A shop is not a test fixture. The specification states one guarantee for WooCommerce in plain words, and it covers the whole module.

A live WooCommerce database is never blindly overwritten with a staging database

Staging exists to test a change, not to replace production data. Live orders and customer records keep their authority, which is why a deployment moves selected parts instead of swapping databases.

  • Orders and customers are never replaced by staging data
  • Only the approved parts of a change are deployed
  • Every deployment has a snapshot behind it

Customer vocabulary, not Git internals

  • Version historyEvery saved version of your site
  • RestoreRoll back to a version you trust
  • CompareSee what changed before you restore
  • ExportTake the files and data with you

The success criterion is deliberately small: create WordPress or connect an existing site, ask AI to change it, see a safe preview, approve it — and roll back if you want to.

WordPress questions

The questions this module is built to answer — including what is not ready yet.

Do I have to move my site to use this?

No. Managed WordPress is one option; the Connector is for sites that stay where they are, on any host, with the plugin installed. Your hosting, domain and database do not move when you connect.

Who owns the content and the database?

You do. Your content, files and database stay yours, the Connector connection is revocable at any time, and it carries project-specific scopes rather than account-wide access.

Can AI edit my PHP files or plugins directly?

Not directly. Code-level changes — PHP, theme files, plugins, database schema — run through the gate: snapshot, staging clone, checks and tests, your approval, selective deployment, and a rollback if the result is not clean.

What happens if a change goes wrong?

The pipeline ends with a post-deploy check, and a result that is not clean is rolled back. Staging exists so that failures happen where no customer sees them.

Is staging safe to use on a live shop?

The specification is explicit: a live WooCommerce database is never blindly overwritten with a staging database. Live orders and customer records stay authoritative — staging tests the change, it does not become the source of truth.

Can I use managed WordPress today?

Not yet. Managed WordPress and the Hostingsurge Connector are in development as early access, and no WordPress instance exists on the platform today. What you can read here is the contract they are being built against.

WordPress that AI can change without putting the site at risk.

Managed WordPress and the Hostingsurge Connector are built so that every risky change has a preview, an approval and a way back.

Start building