NexraOne Agent connects your WordPress site to NexraOne for WordPress uptime monitoring and alerts. NexraOne checks the site’s URL from outside WordPress, so a stopped site can still be detected when WordPress itself cannot send a heartbeat. If a check fails or returns an HTTP 5xx response, NexraOne records the failure and sends an email alert after the configured number of consecutive failures. You can also see when the site recovers.

Install the Agent on each site to combine this external availability check with WordPress health data in one dashboard. As a WordPress monitoring and maintenance tool, NexraOne also shows alerts and pending plugin, theme, and core updates across the sites you manage.

Check whether your WordPress site is up

Check the registered site URL from NexraOne’s servers at the interval set for that site (5 minutes by default)
Detect connection failures and HTTP 5xx responses; HTTP 4xx responses are tracked separately because the server responded
Set how many consecutive failed checks trigger a downtime alert (3 by default)
Receive downtime and recovery notifications by email, and review the site’s uptime history in NexraOne

The external uptime check runs from NexraOne, not from WP-Cron on the monitored site. A NexraOne account is required. External uptime monitoring can continue without the Agent; installing the Agent adds the internal WordPress checks described below.

Manage multiple WordPress sites from one dashboard

Install NexraOne Agent on each site you manage to view their status together. The NexraOne dashboard helps you find sites that need attention without opening every WordPress admin screen.

View site status, health scores, WordPress versions, PHP versions, and pending updates
Filter sites by status, category, WordPress version, PHP version, or installed plugin
Track SSL certificate and domain expiry dates
Review alerts and update history

Monitor WordPress from the inside

After the site is connected, the plugin reports periodic heartbeats and configured events to NexraOne. Depending on the enabled checks, you can monitor:

WP-Cron health
Fatal errors
Failed login activity and administrator account changes
Email delivery failures reported by WordPress
WordPress core, plugin, and theme versions
Disk usage and basic WordPress configuration diagnostics

Alerts can be sent by email. Paid plans also support Slack, Chatwork, and webhook notifications.

Update with a backup and post-update checks

Safe Update can update WordPress core, plugins, and themes from the NexraOne dashboard. Before changing the site, it saves the database and files belonging to the update targets. It applies updates one at a time, then checks the home page and WordPress REST API from outside the site.

If an update fails, NexraOne can attempt to restore the backup. The backup Safe Update keeps on the site is limited to the update targets and the database, and its checks do not cover site-specific flows such as forms, checkout, bookings, or member login. For a copy of the whole site outside your server, use the external backup described below.

Remote update commands are disabled by default. A site administrator must explicitly enable them in the plugin settings before NexraOne can run an update.

Back up the whole site to storage outside your server

External backups send the database and the files in wp-content to storage you choose in NexraOne, so a copy survives even if the server itself is lost. This is optional and off by default.

Choose your own S3-compatible storage (for example AWS S3, Cloudflare R2, Wasabi, Backblaze B2, or MinIO), or the storage NexraOne provides on Cloudflare R2
Set how often files and the database are backed up and how many copies to keep, or run a backup by hand from the NexraOne dashboard
Optionally send an external backup before each Safe Update. If it fails, the update does not start
The backup is uploaded from your server straight to the storage, not through the NexraOne API, and wp-config.php is never included
Restore the database and the files you choose from an external backup, started from the NexraOne dashboard. The backup is downloaded from the storage, checked, and prepared beside the live site; the site is switched over only at the end, and switched back automatically if it does not load afterwards. wp-config.php and this plugin’s own folder are never replaced. Restoring needs both “Allow external backups” and remote updates to be turned on, and the administrator email address is notified when a restore starts

A site administrator must turn on “Allow external backups” on the plugin’s settings page before anything is sent. Using your own storage is included in paid plans; NexraOne-provided storage is a paid add-on. See the NexraOne pricing page for current terms.

Start with up to 3 sites free

A NexraOne account is required. The Free plan supports monitoring for up to 3 sites, requires no credit card, and includes email alerts. Safe Update and additional notification channels require an eligible paid plan.

Create a NexraOne account and connect your first site.

Service and privacy

NexraOne Agent is the official WordPress connector for NexraOne, operated by Solgeo Inc.

The plugin does not transmit monitoring data until a site administrator connects the site to a NexraOne account. See the External services section below for the destination, timing, and types of data sent.

Plugin source is GPLv2 or later. Use of the hosted service is governed by the NexraOne terms.

External services

This plugin connects to https://api.nexraone.app, the NexraOne API operated by Solgeo Inc. The connection provides monitoring, alerts, dashboard reporting, and optional remote updates.

When data is sent:

During pairing or token-based connection, after a site administrator starts the connection
In periodic heartbeats while the site remains connected
When a monitored event occurs, such as a fatal error or email delivery failure
When an administrator sends a test submission with form test mode
While processing an authorized remote update command and reporting its progress
When you set up or run a backup in NexraOne, or enable an external backup before a Safe Update (only if you turned on “Allow external backups” in WordPress; it is off by default)

Data sent may include:

Site URL, title, environment type, and relevant WordPress admin or REST URLs
WordPress, PHP, and database product versions
Installed plugin and theme names, versions, and update availability
Disk usage summaries and WordPress configuration diagnostics
WP-Cron timestamps, login-failure and administrator-account counts, and email delivery status
Fatal-error metadata, including file paths and message excerpts
For a form test mode test submission: the form plugin, form ID and title, the page URL (without query string), and how many emails were sent or failed. The test recipients and the submitted content are not sent
The administrator email address used to initiate the connection
Safe Update targets, progress, results, and backup metadata
Database export and wp-content files, only when the site owner enables external backups in NexraOne (sent to the storage described below, not to the NexraOne API)

Monitoring data is sent only after an administrator connects the site. Remote updates remain disabled until separately enabled in WordPress. Commands then come from the paired NexraOne account without an additional on-site prompt for each queued command.

External backup storage (optional):

If you set up external backups in NexraOne, this plugin sends a backup to the storage you selected there: your own S3-compatible storage, or Cloudflare R2 provided by NexraOne. Nothing is sent unless a site administrator turns on “Allow external backups” on the plugin’s settings page and you set up or run a backup in NexraOne. The plugin does not store storage credentials; NexraOne issues time-limited upload URLs. If the destination changes after you turned the setting on, nothing is sent until an administrator approves the new destination in WordPress.

What is sent: a database export, the files in wp-content (wp-config.php is never included), and a manifest.json (site URL, WordPress and PHP versions, and a list of the backup files)
When it is sent: when you set up or run a backup in NexraOne, and before a Safe Update if you enable the external backup for it
Restoring: when you start a restore in NexraOne, the plugin downloads the backup from the same storage with time-limited download URLs that NexraOne issues for that restore. It connects only to the destination an administrator approved in WordPress, and sends nothing to the storage while restoring
If you use your own S3-compatible storage, the data goes to that provider under its own terms and privacy policy, which you chose and are responsible for
If you use storage provided by NexraOne, the data is stored on Cloudflare R2, which NexraOne uses as a subprocessor
Cloudflare terms: https://www.cloudflare.com/website-terms/
Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/

Service provider: NexraOne, operated by Solgeo Inc.

Service: https://nexraone.app/
Support: https://nexraone.app/support/
Terms of use: https://nexraone.app/terms
Privacy policy: https://nexraone.app/privacy