Jetpack

Jetpack is Automattic’s multi-purpose WordPress toolkit for security, performance, analytics, social publishing, search, backups, anti-spam, newsletters, video and site management. Its main advantage is consolidation: one ecosystem can replace several separate plugins, while individual Jetpack products are also available when you only need one part of the stack.

What Jetpack includes

The core Jetpack plugin combines free and paid features, while Automattic also distributes standalone products such as VaultPress Backup, Jetpack Boost, Jetpack Protect, Jetpack Search, Jetpack Social and VideoPress. Free features include parts of security, performance, site management and growth. Paid plans add services such as real-time backups, malware scanning, advanced search, commercial stats and unlimited social sharing.

Current Jetpack pricing

Pricing checked: September 23, 2026. Jetpack Security is currently advertised at $9.95 per month for the first year when billed annually, then $19.95 per month. Growth follows the same first-year and renewal pricing. Jetpack Complete is $24.95 per month for the first year billed annually, renewing at $49.95 per month.

Security includes VaultPress Backup, Scan, Akismet, a web application firewall, real-time malware scanning, restores and an activity log. Growth bundles Stats, Social, newsletter and monetization tools. Complete combines the broader security, performance and growth suite, including 1TB backup storage, Boost, Search, VideoPress, commercial Stats, Social, AI Assistant and other services.

Where Jetpack makes sense

Jetpack is most attractive when several of its modules are useful on the same site. A publisher might use Stats, Social, CDN-related performance features and newsletter tools together. A business site may value backups, malware scanning, downtime monitoring and the activity log. In those situations, integration across one account and dashboard can be more convenient than maintaining separate vendors.

Where a modular stack can make more sense

A site that only needs backups, only needs caching, or already has hosting-level security may not need the full Jetpack layer. Dedicated plugins can provide deeper controls in one category, different pricing, local data ownership, or licensing that works better across client sites. The right decision depends on which Jetpack modules are actually active and valuable.

How the WordPress.com connection affects Jetpack

Many Jetpack services depend on a WordPress.com connection because part of the work happens on Automattic infrastructure rather than only inside the local WordPress install. That connection powers services such as centralized site management, parts of Stats, Social, Search, Backup, VideoPress and other cloud-backed features.

This model can be convenient because backups, search indexes and some processing remain available even when the origin site has problems. It also means Jetpack is not purely a local plugin. Teams with strict data-location, account-management or vendor-separation requirements should review which modules send data to Automattic services before standardizing on the suite.

Important trade-offs before adopting the full suite

The biggest advantage of Jetpack is also the main trade-off: consolidation. Using several modules through one vendor reduces the number of separate dashboards and support relationships, but it can also make the site more dependent on one account and one ecosystem. If you later move away, backups, historical Stats, social connections, hosted search indexes, newsletter subscribers and VideoPress assets may need separate migration plans.

Performance should also be evaluated module by module. Jetpack Boost and CDN-related features can be useful, but they do not automatically replace every host-level cache, object cache, image service or dedicated optimization plugin. Likewise, Jetpack Protect and Security features can overlap with host security, a CDN firewall or another security plugin. Avoid stacking duplicate infrastructure without deciding which layer owns each job.

Who should compare Jetpack with separate plugins?

A modular stack is worth comparing when you already receive strong backups, caching or security from your host, when one Jetpack module is the only feature you need, or when you want category-specific tools with deeper controls. Agencies may also prefer separate products when licensing across many client sites is easier to manage that way.

By contrast, a publisher or business using several Jetpack services can benefit from keeping them together. The correct comparison is not Jetpack versus one plugin. It is Jetpack versus the complete set of replacement tools you would actually need, including their combined cost, support burden and migration risk.

Jetpack FAQs