NoyaCare

NoyaCare is for agencies and freelancers who look after client sites and need updates to be safe and provable. Every item goes through the same steps:

1. Restore point — the plugin or theme folder is archived and the option rows it owns are saved.
2. Update — the item is installed on its own, never in a batch, so a failure always has a clear cause.
3. Check — key pages are loaded over real HTTP and compared with before the run: status codes, PHP fatal errors on those pages or in the updated code, a page that shrinks or stops half-way, and new PHP error-log entries.
4. Roll back — if the site broke, the restore point is put back automatically and the run carries on (or stops, your choice).
5. Report — the client gets an HTML e-mail, with a PDF when the backup folder is protected. Every run and every item has its own reference number.

Why it is different

• A restore point before every item, small and fast even on shared hosting: one folder and its option rows. A full database dump is optional.
• The live site is checked over HTTP, the way a visitor sees it — not from inside the update process.
• Careful rollback rules. Only a problem a visitor would notice counts as a failure. Slowdowns and deprecation notices are reported, never rolled back.
• Background runs that survive shared hosting: small steps, a watchdog, a live progress bar and a cancel button.
• Quarantine. A version that broke the site stays held until you release it.
• Security fixes first. With a WPScan or Patchstack key, an update that fixes a known vulnerability goes in straight away and leads the client report.
• Website speed from Google PageSpeed Insights and NoyaCare’s own checks, which also work on local sites, kept as a trend.
• No bloat. No bundled libraries and no build step.

NoyaCare Pro

NoyaCare is complete on its own. The separate NoyaCare Pro add-on adds uptime monitoring, AI analysis of failed runs, GTmetrix, scheduled speed tests and white-label reports.

Scheduling

Automatic runs are off until you choose a schedule, and WP-Cron only runs on visits. With real cron, run maintenance from the command line:

0 3 * * 2 cd /path/to/site && wp noyacare run --quiet

or keep NoyaCare’s schedule and call WP-Cron every few minutes:

*/5 * * * * cd /path/to/site && wp cron event run --due-now --quiet

WP-CLI

wp noyacare status|run|health|speed|quarantine|backups|restore|prune|access|report — `wp help noyacare <command>` shows the options of each, such as `run --dry-run`.

REST API

Read-only, authenticated with an application password over HTTPS: GET /wp-json/noyacare/v1/status, …/updates, …/runs/<run-uid>, …/performance. No run starts from outside.

For developers

Filters and actions include noyacare_loaded, noyacare_run_tasks, noyacare_report_data, noyacare_capability and noyacare_run_finished. Like WordPress’s own, NoyaCare’s requests to the site skip TLS certificate checks, which local and staging sites would fail; noyacare_sslverify turns them on.

External services

NoyaCare connects to these services only when the feature that needs them is used.

• Google PageSpeed Insights — when you start a speed test (dashboard, Website speed screen, wp noyacare speed) or test the connection: each tested page’s address, the device (mobile or desktop) and your optional API key go to Google, which then loads the page like a visitor. Terms of service, privacy policy.
• WPScan — only when vulnerability checks use WPScan: whenever NoyaCare looks at pending updates (dashboard, runs, WP-CLI), the slugs and installed versions of the plugins, themes and WordPress release with an update waiting go with your API token. Answers are kept for 12 hours. Terms of service, privacy policy.
• Patchstack — only when vulnerability checks use Patchstack: the same slugs and versions, with your API key. Terms and conditions, privacy policy.
• WordPress.org — when a WordPress core update breaks the site, the previous release is downloaded from downloads.wordpress.org to put it back; the request names only the version and language. Privacy policy.

Suggested wording for the site’s privacy policy appears under Settings → Privacy.