PatchOn Agent vs StifLi Backup Tools

PatchOn is an AI service that runs your WordPress plugin, theme, and core updates for you. It reproduces your production site in a staging environment, lets AI verify whether each update can be applied safely, and applies only the updates that pass every check to production. If an update ever fails, one click restores your site. This plugin acts as the agent connecting your WordPress site to PatchOn. Getting Started This plugin requires the PatchOn service (patchon.jp) and does not function on its own. Activation alone performs no external communication and does not redirect you. Clicking “Start PatchOn” on the welcome screen opens a consent dialog describing the data that will be sent; confirming it with “Agree and Start” registers your site anonymously and, if updates are available, starts the first inspect-and-update run. No account is required to get started — you need one only to: view detailed inspection results configure automatic updates use paid features Main Features Pre-inspection — in a staging environment, AI compares before / after screenshots of your site to detect layout breakage and fatal errors Inspect and update — a manual run goes from inspection to production rollout in one action, applying only updates that passed every check Automatic updates with inspection — the site is inspected on a schedule and only updates that passed every check are applied Backups — taken automatically right before each update and downloadable for a plan-based retention period One-click restore — if an applied update fails, one click puts your site back to the pre-update backup This plugin (the free distribution on WordPress.org) does not write patched code to your site files, even when it detects a problem. AI auto-repair, which fixes the code causing a problem found during a pre-inspection, is provided by the separately distributed PatchOn Agent Pro extension plugin (available to paid plan subscribers). This plugin writes to your site files in only two cases: applying the updates themselves through the standard WordPress upgrader, and the one-click restore, which runs only on your explicit request and writes your own backed-up plugins, themes, MU plugins, and wp-content drop-ins (and your database) back to the site. Data Sent Once you have consented on the consent screen, running a “Pre-inspection” or “Apply update” sends the following data to PatchOn and related external services. See the Privacy Policy for details. Site URL / WordPress version / PHP version / DB version List and versions of installed plugins, themes, and MU plugins List of available updates (names and versions of plugins, themes, and WordPress core). While the site is connected, this is sent automatically once a day Site files prior to update application, used for the pre-update backup: wp-config.php, active and to-be-updated plugins and themes, MU plugins, and wp-content drop-ins (such as object-cache.php) Contents of WordPress debug.log (used to detect issues) A full copy of your site’s database, taken during a pre-inspection and reused as the pre-update backup. It may include personal data stored on your site, such as member accounts or contact-form submissions External services This plugin depends on the following external services. No external communication is performed merely by activating the plugin; it starts only after you explicitly click the “Agree and Start” button on the consent screen shown on first use. PatchOn API (https://patchon.jp and its subdomains) The backend for all inspection, repair, update, and database-dump operations. Two host names are used, both operated by Rocketa Inc. and routed to PatchOn’s infrastructure: https://patchon.jp/api/* — site registration, pre-inspection control, apply-update control, billing https://dump.patchon.jp/* — database-dump control endpoints and signed-URL chunk uploads for pre-inspections and pre-update backups Provider: Rocketa Inc. (rocketa.co.jp) When data is sent: On click of the “Agree and Start” consent button (one-time): anonymous site registration and UUID issuance Once a day while connected (daily check-in): the list of available updates and plugin version When the user runs a “Pre-inspection”, or when automatic updates run their scheduled inspection: list of plugins / themes, debug.log, full database copy When the user runs an “Apply update”, or when automatic updates apply an update that passed every check: a backup (site files and a full database copy) and the application result When the user runs the one-click restore after a failed update: restore control requests and progress status (the backed-up files and database themselves are downloaded from cloud storage at that time, not sent) What is sent: see the “Data Sent” section above Terms of Service: https://patchon.jp/terms Privacy Policy: https://patchon.jp/privacy-policy Subprocessors: https://patchon.jp/subprocessors AWS S3 (Tokyo region, accessed via PatchOn) Storage destination for the site backup (zip) and the database copy (uploaded in chunks). Uploads and downloads are performed only against pre-signed URLs issued by PatchOn on a per-request basis. The customer site does not hold any S3 credentials. During a one-click restore, the backed-up site files and database chunks are downloaded from S3 in the same way. Provider: Amazon Web Services, Inc. Endpoint: https://*.s3.ap-northeast-1.amazonaws.com (pre-signed URLs only) When data is sent: when the user runs a “Pre-inspection” (database copy) or an “Apply update” (backup: site files and database copy) What is sent: site files (zip) and a full copy of the database AWS Privacy: https://aws.amazon.com/privacy/

StifLi Backup Tools is a professional WordPress backup plugin for creating full site backups, database backups, file backups, scheduled backups, staging sites, Fast Staging builds for developers, Local Developer Packages, and migration packages directly from your WordPress dashboard. The plugin is designed for everyday WordPress site owners, freelancers, agencies, and administrators who need a practical backup and restore workflow without depending on complex server tools. It uses background processing, resumable jobs, chunked ZIP creation, streaming database exports, and HTTP range downloads to help backups and restores complete even on shared hosting, slower servers, or environments where long requests may be interrupted. For agencies and development teams, StifLi Backup Tools also includes differentiated workflows for building lean staging environments and exporting Local Developer Packages, reducing the time spent cloning oversized production sites just to test changes, debug issues, or hand work over for local development. Use StifLi Backup Tools to back up WordPress before updates, keep scheduled backup copies, migrate a site to a new domain, create a staging copy, restore selected components, or send backup archives to remote storage such as Google Drive, Dropbox, Amazon S3-compatible storage (including Cloudflare R2), FTP, or SFTP. Official documentation: StifLi Backup Tools Documentation. WordPress backup features Full WordPress backups including database, plugins, themes, uploads, and selected site files. Database-only backups for quick snapshots before plugin, theme, or content changes. Files-only backup options for plugins, themes, and uploads. Differential scheduled backups to save only changed files between full backups. Backup integrity checks before restore. Backup explorer for reviewing backup contents. Component restore for database, plugins, themes, or uploads. Selective restore for specific files or directories. Backup upload and local backup rescan tools. HTTP range downloads for large backup archives and interrupted downloads. Scheduled backups Create automatic WordPress backups on a schedule and control how many copies are kept locally and remotely. Daily, weekly, fortnightly, monthly, and custom scheduled backup workflows. Choose backup components: database, plugins, themes, uploads, or full site. Choose local storage, remote storage, or remote-only backups. Full or differential backup strategy. Separate retention rules for local backups, remote backups, and differential backups. Email notifications for backup results. Optional webhook notifications for external monitoring or automation. Remote backup storage StifLi Backup Tools can send backup archives to remote destinations only after you explicitly configure and enable them. Supported destinations include: Google Drive Dropbox Amazon S3 S3-compatible storage such as Backblaze B2, Wasabi, MinIO, DigitalOcean Spaces, and Cloudflare R2 FTP SFTP Remote storage is optional. The plugin does not contact external storage services unless you enable and configure the corresponding destination. WordPress restore and recovery Restore your WordPress site from a backup with a guided process and live progress updates. Restore database and files. Restore only selected components. Restore uploaded backup ZIP files. Restore local or remote backup archives. Merge differential backups with their parent full backup when required. Streaming restore progress designed to avoid browser and hosting timeouts. Semaphore locking to help prevent overlapping backup and restore operations. WordPress migration tools Move a WordPress site to another server or domain using migration packages and URL remapping. Create migration packages from the WordPress dashboard. Import migration packages on the destination site. Remap URLs when moving to a new domain. Optional site-to-site Push/Pull migration using a shared secret between two WordPress sites you control. Standalone installer for migration scenarios where WordPress is not yet installed on the destination server. Staging sites Create a staging copy of your WordPress site for safe testing before making changes on production. Create full staging sites or lean Fast Staging builds in a subdirectory. Copy files and database tables into the staging environment. Exclude selected tables, plugins, themes, uploads, and WooCommerce-heavy data for developer-focused staging builds. Search and replace URLs for the staging copy. Track staging job progress. Delete staging sites from the plugin interface. Developer workflows StifLi Backup Tools includes dedicated workflows for developers, freelancers, and agencies who need faster QA environments and cleaner local handoff packages. Fast Staging for developers creates lean staging builds by letting you limit the copy to the tables, plugins, themes, uploads, and data scope you actually need. Local Developer Package export prepares a LocalWP-friendly package for local development workflows so a selected site snapshot is easier to move, inspect, and hand off. Background processing, live progress updates, cancel support, and resumable job handling help these workflows stay practical on large sites and typical WordPress hosting. Useful for client review environments, bug reproduction, plugin or theme QA, and pre-release testing without cloning the full production site every time. Maintenance and optimization tools StifLi Backup Tools also includes practical maintenance utilities for WordPress administrators. Image optimization using the WordPress image editor when available. Database cleanup for revisions, spam comments, trash comments, transients, and overhead. Temporary file cleanup for backup, restore, staging, and upload leftovers. Custom exclude rules for uploads and wp-content backup paths. System information and log viewer for troubleshooting backup issues. Built for shared hosting Many WordPress sites run on shared hosting or constrained VPS environments. StifLi Backup Tools is built with those limitations in mind. Background processing via WP-Cron. Resumable backup and restore stages. Chunked ZIP creation. Streaming database export and import. Memory-aware file operations. Locking to avoid concurrent destructive operations. Compatibility options for different archive engines and compression profiles. AI agents and MCP abilities StifLi Backup Tools can expose selected WordPress Abilities to MCP-compatible AI agents for professional and commercial automation workflows. Uses the WordPress Abilities API (WordPress 6.9+). Lets administrators enable or disable abilities globally and per ability. Exposes a safe default set for backup and remote-management operations. Keeps restore and scheduled-execution operations outside MCP ability exposure by design. External services This plugin can connect to third-party services only when you explicitly enable and configure the corresponding feature. No telemetry, analytics, license check, or automatic external update call is made by the plugin. The full list of services that may be contacted, the data that is sent, and when, is described below. Google Drive (optional, opt-in) If you connect a Google account to use Google Drive as a remote backup destination, the plugin contacts Google’s OAuth and Drive APIs. Endpoints used: https://oauth2.googleapis.com/token — to exchange and refresh OAuth tokens. https://www.googleapis.com/drive/v3/* — to list, create, update, download, and delete backup files in your Drive. https://www.googleapis.com/upload/drive/v3/files — to upload backup archives in resumable chunks. What is sent: your OAuth client ID and secret provided by you, the refresh/access token, backup ZIP files you choose to upload, and metadata such as filename, size, and parent folder ID. When: only when you start OAuth connection from the settings page, run a backup that has Google Drive selected as a destination, or browse, restore, or delete remote backups stored in your Drive. Provider terms: Google Terms of Service and Google Privacy Policy. Dropbox (optional, opt-in) If you connect a Dropbox account to use it as a remote backup destination, the plugin contacts Dropbox APIs. Endpoints used: https://api.dropboxapi.com/oauth2/token — to exchange and refresh OAuth tokens. https://api.dropboxapi.com/2/* — to query account info, list files, and delete files. https://content.dropboxapi.com/2/* — to upload and download backup archives. What is sent: your Dropbox app key and secret provided by you, the refresh/access token, backup ZIP files you choose to upload, and request metadata such as paths, filenames, and sizes. When: only when you start OAuth connection from the settings page, run a backup that has Dropbox selected as a destination, or browse, restore, or delete remote backups stored in Dropbox. Provider terms: Dropbox Terms of Service and Dropbox Privacy Policy. Amazon S3 and S3-compatible services (including Cloudflare R2) (optional, opt-in) If you configure an S3-compatible remote destination, the plugin contacts the endpoint you specify in the destination settings. Endpoints used: AWS S3 endpoints such as https://s3. .amazonaws.com and https:// .s3. .amazonaws.com, Cloudflare R2 endpoints such as https:// .r2.cloudflarestorage.com, or the custom S3-compatible endpoint URL you enter. What is sent: your access key ID, the SigV4-signed request, the backup ZIP file you choose to upload, and request metadata such as bucket, object key, and size. Your secret access key is used locally to sign requests and is not sent as plain text. When: only when you test the connection, run a backup that has the S3 destination selected, or browse, restore, or delete remote backups stored in the bucket. Provider terms: depend on the provider you configure. For AWS, see AWS Service Terms and AWS Privacy Notice. For S3-compatible providers, see the terms and privacy policy of the provider you choose. FTP and SFTP servers (optional, opt-in) If you configure an FTP or SFTP destination, the plugin connects to the server details you enter in the destination settings. Endpoints used: the FTP or SFTP host, port, and path entered by you. What is sent: the credentials or key details you configure, backup ZIP files you choose to upload, and request metadata required to list, upload, download, or delete files. When: only when you test the connection, run a backup that has the FTP/SFTP destination selected, or browse, restore, or delete remote backups stored on that server. Provider terms: depend on the FTP/SFTP server or hosting provider you choose. Webhooks (optional, opt-in) If you configure one or more webhook URLs in the scheduled backup settings, the plugin sends an HTTP POST to those URLs when a scheduled backup completes, depending on your notification settings. Endpoints used: any webhook URL you enter in the settings. What is sent: a small JSON payload containing the site URL, backup name, backup type, result status, and timestamp. No credentials, database content, or backup archive content is sent in the webhook payload. When: only when a scheduled backup task with a webhook configured finishes. Provider terms: depend on the third-party endpoint you enter. The plugin authors are not affiliated with any specific webhook provider. Site-to-site migration Connect API (optional, opt-in) If you enable the built-in Connect API and use the Push/Pull migration feature, this WordPress site exchanges data with another WordPress site that you control. Endpoints used: /wp-json/stifbt/v1/connect, /wp-json/stifbt/v1/push, and /wp-json/stifbt/v1/pull on the remote site URL you enter manually. What is sent: a shared secret generated by you and, for Push/Pull operations, the migration ZIP package containing the data you chose to migrate. When: only when you test the connection or start a Push/Pull migration from the migration screen. Provider terms: not applicable; the remote endpoint is another WordPress site under your control. No third-party service is involved.