Novamira HQ currently supports Kinsta, InstaWP, SandyWP, Pantheon, Pressable, WP Engine,
Rocket.net, Hostinger, Cloudways, Plesk, xCloud, cPanel, and WHM. Available operations vary by provider.
SandyWP accounts connect with a SandyWP API key, created from the account menu
in the SandyWP dashboard. HQ lists your sandboxes with their status and expiry
and creates new ones from the CLI; a new sandbox is provisioned in the
background, so wait for it with hosting ops wait. The workspace is optional:
leave it blank to use your personal workspace. HQ never shows or stores a
sandbox's admin password or one-click login link. Novamira setup uploads the
official plugin to a ready sandbox and activates it, and never overwrites an
existing Novamira folder. HQ does not turn on Novamira's AI Abilities there, on
any plan, so enable them in WordPress before connecting. SandyWP's API cannot run
WP-CLI, manage backups or change PHP, so those actions are not available.
Plesk accounts can list hosted domains. An active WP Toolkit adds WordPress
installation discovery, Novamira setup, WordPress backup and restore, and
directional copying between two selected WordPress installations. Plesk copying
requires an explicit database and/or WP Toolkit files scope; selected files and
a separate search-and-replace step are not supported. WP Toolkit excludes
WordPress configuration and server rewrite files from its default file copy.
xCloud accounts list WordPress sites with their staging sites, and support
backups, full-page cache purges, plugin and theme updates, access logs, and site
events. The xCloud API cannot install plugins, create or push staging sites, or
restore backups, so Novamira setup, pushes, and restores are not available
there; install the Novamira plugin yourself and connect the site by URL.
cPanel accounts connect with the HTTPS cPanel address (the panel URL, for
example https://server.example.com:2083), the cPanel username and a cPanel
API token. HQ lists WordPress installed at the root of each domain, creates
and lists whole-account backups in the home directory, and shows the domain
error log. An account backup counts against the account's disk quota. With
WP Toolkit, HQ installs and activates Novamira through it. Without WP
Toolkit, and only after you approve it, HQ uploads Novamira and a temporary
installer that runs once when WordPress loads and then removes itself; when
Novamira is already installed, HQ uploads only the temporary installer, no
ZIP. This needs WordPress permalinks turned on. cPanel has no user-level API
for restoring backups, clearing caches or changing PHP, so those actions are
not available. WordPress installed in a subfolder is not listed.
WHM servers connect with the HTTPS WHM address (for example
https://server.example.com:2087), the WHM user and that user's API token.
With root, one profile covers every cPanel account on the server; with a
reseller, the accounts that reseller owns. Site ids are <account>:<domain>.
The operations, limits and temporary-installer approval are the same as
cPanel's. HQ uses WP Toolkit for an account only when that account's feature
list includes it; otherwise it reads the account's files and, after you approve
it, sets up Novamira with the temporary installer, uploaded through a
short-lived cPanel session that HQ logs out. That temporary installer path
needs https://<WHM host>:2083 reachable from this computer with a valid
certificate. WHM's WP Toolkit API does not accept reseller tokens, so a
reseller's sites always use the temporary installer, which needs the
reseller's create-user-session privilege; listing needs list-accts. A root
token controls the whole server, so create one for HQ and revoke it from
WHM » Development » Manage API Tokens.
The desktop app includes everything it needs. You do not need to install
Node.js, npm, Deno, or any additional Novamira component.