Quick verdict: Jetpack VaultPress Backup is a solid, plugin-based service, but even its standalone version depends on Jetpack's connection infrastructure and runs as PHP code inside your site. BackupYourSite delivers the same protection over SSH with zero plugin footprint and no WordPress.com account dependency.
If you've searched for a Jetpack VaultPress Backup alternative, there's a good chance the reason isn't the backups themselves — it's everything that comes along with them. Jetpack VaultPress Backup is a capable, well-established cloud backup service from Automattic, the company behind WordPress.com. But getting it running on your site means installing a plugin that's built on Jetpack's shared connection infrastructure, and for a lot of WordPress site owners and agencies, that's exactly the dependency they're trying to avoid.
This article breaks down, factually, what Jetpack VaultPress Backup actually installs and requires, what real users say about its footprint, and how BackupYourSite's agentless SSH approach removes the plugin dependency entirely.
Quick Answer: Is There a Backup Tool That Doesn't Need a WordPress Plugin?
Yes. BackupYourSite connects to your server directly over SSH and copies your files and database to offsite storage — no WordPress plugin, no PHP process competing for your site's memory and CPU limits, and no admin-panel dependency for backups to run. Jetpack VaultPress Backup, by contrast, is a WordPress plugin at its core: even its "standalone" version (separate from the full Jetpack suite) still requires an active Jetpack connection to WordPress.com's servers to authenticate and transmit backup data, which means Jetpack's connection package and cloud-service dependency ship with it either way.
What Jetpack VaultPress Backup Actually Requires
It's worth being precise here, because Automattic has changed how this product is packaged more than once.
- VaultPress was an independent premium backup service launched in 2010, later folded into Jetpack in 2019.
- Jetpack VaultPress Backup ("Jetpack Backup" on WordPress.org) is now offered as a plugin you can install without activating the full multi-module Jetpack plugin (Stats, Related Posts, Social, CDN, etc.).
- However, that "standalone" plugin is still built on Jetpack's connection library, and it requires you to connect the site to a WordPress.com/Jetpack account before it can authenticate and push backup data to Automattic's cloud. It is not a self-contained, connection-free plugin — it depends on the same infrastructure the full Jetpack suite uses.
- In practice, many site owners already run the full Jetpack plugin for stats, security scanning, or social sharing, and simply switch on the Backup module inside it — which means the backup feature arrives bundled with a much larger codebase than backup functionality alone requires.
None of this makes Jetpack VaultPress Backup a bad product. Its real-time, continuous backup model and one-click restore are genuinely solid engineering. The question this article addresses is narrower: does getting that functionality require running a WordPress plugin with a persistent connection dependency, and is there a way to get equivalent protection without it? The answer to the second half is yes.
Jetpack VaultPress Backup Pricing (Current, 2026)
| Plan | Intro Price | Standard Price | What's Included |
|---|---|---|---|
| VaultPress Backup (standalone) | $4.95/month | $9.95/month | Real-time backups, 10GB storage, 30-day activity log, one-click restore, unlimited migrations, WooCommerce support |
| Security Bundle | $9.95/month | $19.95/month | Everything above + malware scanning, website firewall (WAF), spam protection (10k API calls/month), automated fixes |
Both plans are billed yearly, and the lower "intro" price applies to the first year only — the standard renewal price roughly doubles after year one. Storage starts at 10GB, which for a WooCommerce store with a large media library or order history can be tight; additional storage is an upsell.
Why "Plugin Bloat" Keeps Coming Up in Jetpack Reviews
Search WordPress.org's own review threads for the Jetpack plugin and the pattern is consistent. Review titles include "Bloatware," "Not worth it. Slows your site down," and "Good All-in-One Tool, But Heavy on Performance." One reviewer summed up a common complaint: after activating several of Jetpack's modules, page load times increased, calling it "a solid plugin, but definitely not the lightest option out there." Others describe Jetpack as bloated with features they don't need or that dedicated single-purpose plugins handle better, leading some site owners to uninstall it within days.
To be fair to Automattic, this has improved. Jetpack's modular architecture in recent versions lets you deactivate the code for features you're not using, and multiple 2026 reviews note that a carefully configured, modular Jetpack install is measurably lighter than it used to be. The bloat complaints aren't universal, and they're less severe than they were several years ago.
But "configure it carefully to minimize the footprint" is still a different proposition than "it has no footprint." Every Jetpack module you activate — Backup included, because of its shared connection package — is PHP code that loads on your site, on every request, competing for the same memory and execution-time limits as your theme and every other plugin. A backup tool's entire job is to protect your site when something goes wrong; adding more moving parts to the thing you're protecting is a real tradeoff, even a modest one.
The Core Structural Difference: On-Server Plugin vs. Agentless SSH
This is the actual technical distinction worth understanding, independent of any one vendor's current bloat level:
Plugin-based backup (Jetpack VaultPress Backup, and most competitors):
- Runs as PHP code inside your WordPress installation
- Requires an active connection/authentication handshake to a remote service (WordPress.com, in Jetpack's case) to push data
- Competes for the same PHP memory limit, execution time cap, and database connections as the rest of your site
- If the site is compromised, has a fatal plugin conflict, or WordPress itself won't load, the backup plugin can be affected too — because it lives inside the thing that broke
- Adds to your total plugin count, which is itself a factor in update overhead, compatibility testing, and attack surface
Agentless SSH backup (BackupYourSite):
- Connects to the server directly over SSH — no code installed inside WordPress, no plugin listed in your
wp-adminplugins page - Copies files and the database at the filesystem/server level, entirely outside PHP execution
- Never touches your active plugin count, so there's zero additional plugin-conflict risk and zero resource competition with your live site
- Keeps working even if WordPress itself is broken, a plugin update fails, or wp-admin is inaccessible — because the backup path never depends on WordPress loading successfully
- Nothing to update, patch, or version-check inside the CMS itself
This isn't a claim that plugin-based backups don't work — millions of sites run them successfully every day. It's a structural point: a backup system that depends on the health of the thing it's backing up has a coupling problem that an agentless, SSH-based system doesn't have.
Jetpack VaultPress Backup vs. BackupYourSite: Side-by-Side
| Jetpack VaultPress Backup | BackupYourSite | |
|---|---|---|
| Installation | WordPress plugin (standalone or via full Jetpack) | No plugin — connects via SSH |
| Account dependency | Requires WordPress.com/Jetpack account connection | Server credentials only |
| Runs inside WordPress? | Yes, as a PHP plugin process | No — filesystem/server level |
| Resource competition with site | Yes, shares PHP memory/execution limits | None |
| Works if WordPress is broken/wp-admin down | Depends on plugin/connection health | Yes, backup path is independent of WordPress |
| Entry pricing | $4.95/mo intro, $9.95/mo standard (annual billing) | See current BackupYourSite plans |
| Storage included | 10GB | Varies by plan |
| Agency/multi-site management | Via Jetpack Manage dashboard | Flat monthly per-site or agency tiers |
| Restore method | One-click restore via Jetpack Backup dashboard | Direct restore, no CMS dependency |
Who Should Actually Consider Switching
A plugin-based tool like Jetpack VaultPress Backup remains a reasonable choice if you're already fully invested in the Jetpack ecosystem (Stats, Social, Boost, etc.) and you're comfortable with the connection/account dependency that comes with it. If your priority is minimizing what's installed and running inside WordPress itself — because you manage many client sites, because a past plugin conflict caused downtime, because you want backups that survive even when the CMS layer doesn't, or because every additional PHP process on a resource-constrained host is a cost you'd rather not pay — an agentless SSH approach like BackupYourSite addresses that directly, by design, rather than through configuration tuning.
How to Check What a Backup Plugin Is Costing Your Site
If you're already running Jetpack VaultPress Backup and want to know whether it's actually affecting performance on your specific site, you don't need to guess. A few concrete checks:
- Query Monitor plugin — install it temporarily and look at the "Queries by Component" and "HTTP API Calls" panels. Jetpack's connection heartbeat and backup-sync calls will show up here if they're firing on front-end page loads, not just in wp-admin.
- Server-side PHP process list — on a VPS or dedicated host,
ps aux | grep phpduring a backup window will show whether a backup-related PHP-FPM worker is consuming a disproportionate share of memory relative to your normal request handlers. - Plugin count vs. site speed tools — run a before/after Lighthouse or GTmetrix pass with the backup plugin deactivated (on a staging copy, not live) to isolate its specific contribution to Time to First Byte and server response time, separate from everything else running on the site.
- wp-admin load time with and without the plugin active — Jetpack's connection and stats-syncing code executes admin-side as well, so agencies managing many client sites sometimes notice this more in the dashboard than on the public-facing pages.
None of these checks are specific to Jetpack — they apply to evaluating any plugin's footprint. The point is that "is this actually a problem for my site" is answerable with data, rather than going purely on general reputation either direction.
What Agencies Managing Multiple Sites Should Weigh
For a single-site owner, the plugin-vs-agentless distinction is a nice-to-have. For an agency or freelancer responsible for a dozen, fifty, or a few hundred client WordPress installs, it compounds. Every additional plugin across every managed site is one more thing to keep updated, one more potential conflict with a client's theme or another plugin, and one more support ticket if a client's host has tight PHP memory limits and something breaks. A backup layer that sits entirely outside WordPress removes an entire category of that maintenance surface — there's no backup-plugin version to track, no compatibility matrix to check before a WordPress core update, and no scenario where the backup tool itself becomes the thing that needs troubleshooting on a client call.
Frequently Asked Questions
Does Jetpack VaultPress Backup require installing the full Jetpack plugin?
Not strictly. Automattic offers a standalone "Jetpack Backup" plugin that doesn't require activating the full multi-feature Jetpack plugin. However, the standalone plugin is still built on Jetpack's shared connection library and requires connecting the site to a WordPress.com/Jetpack account to authenticate backups — so the dependency on Jetpack's infrastructure remains even in standalone form.
Is Jetpack known for plugin bloat?
It has a reputation for it, though the severity is debated and has improved. WordPress.org reviews for the Jetpack plugin include titles like "Bloatware" and "Not worth it. Slows your site down," alongside more recent reviews noting that a carefully configured, modular install is lighter than in past years. The bloat concern is mainly about activating unused modules — the more of Jetpack's feature set you turn on, the more PHP code loads on every page request.
How much does Jetpack VaultPress Backup cost?
The standalone VaultPress Backup plan starts at $4.95/month (introductory rate, billed yearly), renewing at $9.95/month standard. The Security bundle, which adds malware scanning and a firewall, starts at $9.95/month introductory, renewing at $19.95/month. Both include 10GB of backup storage.
What does "agentless" backup mean?
Agentless means no software agent (plugin, extension, or background process) is installed inside the application being backed up. BackupYourSite backs up WordPress sites by connecting over SSH to the hosting server directly, copying files and the database without any code running inside WordPress itself — as opposed to an "agent-based" tool like a WordPress plugin, which must be installed, updated, and kept running inside the CMS to function.
Can an agentless backup restore a site if wp-admin is completely broken?
Yes, in principle, because the backup and restore process doesn't depend on WordPress loading or the admin dashboard being reachable — it operates at the server/filesystem level. A plugin-based backup tool's restore path, by contrast, typically depends on the plugin's dashboard (or a companion recovery tool) being accessible, since the backup system itself lives inside the CMS.
Does removing a backup plugin actually make a measurable performance difference?
It depends on the site and hosting environment, but removing any active plugin reduces the PHP code executed on each page load and removes one more piece competing for the site's memory and execution-time limits. On resource-constrained shared hosting, or on sites already running several plugins, the cumulative effect of each additional plugin — including a backup plugin's connection library — is more noticeable than on a site with generous server resources and few other plugins active.
The Bottom Line
Jetpack VaultPress Backup is a legitimate, well-built backup service, and its real-time backup model and restore workflow work as advertised for a large number of WordPress sites. But it is, structurally, a plugin — even in its "standalone" form, it depends on Jetpack's connection infrastructure and runs as PHP code inside the site it protects. For agencies and site owners who've decided that backup infrastructure shouldn't share resources, update cycles, or failure modes with the CMS it protects, BackupYourSite's agentless SSH approach is built specifically to remove that coupling: no plugin installed, no Jetpack account dependency, and a backup and restore path that keeps working even when WordPress itself doesn't.