Straight answers about WP Nexus
What the platform does today, what it does not do yet, and where the boundaries are.
How many sites can I manage?
There is no hard cap. Operations are designed for fleets rather than single sites: bulk actions, per-site scoping, and durable operation records that survive a worker restart. Multisite networks are handled as networks rather than as a pile of unrelated sites.
What happens if an update breaks a site?
A restore point is captured before the update runs. Afterwards, health is verified with independent probes rather than trusting the update response. If verification fails, the previous release is restored automatically and the result is recorded. If the recovery route is unreachable before the update starts, the update does not start.
Does it work if WordPress itself is broken?
Yes. There is a recovery channel that runs independently of WordPress. When WordPress is returning errors on every request, that channel still reports database connectivity, disk and version state, and can restore the previous plugin release.
What can WP Nexus not do yet?
Self-serve billing is not open. Some provider integrations are still gated behind acceptance testing rather than enabled by default. We would rather tell you a capability is unavailable than have it half work against a client site.
Where is my data held?
Site credentials are encrypted at rest and never sent to the browser. Backups can be replicated to storage you control. Exports are supported, and leaving is a supported path rather than a support conversation.
See how Nexus fits your operating model
Start with a scoped conversation. No subscription begins from this page.