lelandf

Themetry

Contrary to popular belief, <a href="https://wordpress.org/plugins/jetpack/" rel="ugc">Jetpack</a> does not require you to connect your website to WordPress.com before you can use it at all.
Several Jetpack modules are self-contained and do not require a WordPress.com connection to function:
<ul>
<li>Asset CDN</li>
<li>Beautiful Math</li>
<li>Carousel</li>
<li>Contact Form</li>
<li>Copy Post</li>
<li>Custom CSS</li>
<li>Custom content types</li>
<li>Extra Sidebar Widgets</li>
<li>Gravatar Hovercards</li>
<li>Infinite Scroll</li>
<li>Lazy Images</li>
<li>Markdown</li>
<li>Sharing</li>
<li>Shortcode Embeds</li>
<li>Site verification</li>
<li>Sitemaps</li>
<li>Tiled Galleries*</li>
<li>Widget Visibility</li>
</ul>
The Development Mode for Jetpack plugin enables (wait for it…) <a href="https://jetpack.com/support/development-mode/" rel="nofollow ugc">Jetpack Development Mode</a>, which does two things:
<ul>
<li>Eliminates “nags” to connect a Jetpack-enabled site to WordPress.com.</li>
<li>Allows usage of modules that do not require a WordPress.com connection.</li>
</ul>
It also means you can stop using individual Jetpack modules that have been forked out into standalone plugins by random people. These plugins tend to be unsupported and out of step with the latest version of the official Jetpack equivalent.
Please note that this plugin requires Jetpack to be activated alongside it to be of any use, and will not help with the following modules that do require a WordPress.com connection:
<ul>
<li>Ads</li>
<li>Backups and Scanning</li>
<li>Comment Likes</li>
<li>Comments</li>
<li>Enhanced Distribution</li>
<li>Google Analytics</li>
<li>Image CDN</li>
<li>JSON API</li>
<li>Likes</li>
<li>Monitor</li>
<li>Notifications</li>
<li>Post by email</li>
<li>Protect</li>
<li>Publicize</li>
<li>Related posts</li>
<li>SEO Tools</li>
<li>Search</li>
<li>Secure Sign On</li>
<li>Site Stats</li>
<li>Subscriptions</li>
<li>VideoPress</li>
<li>WP.me Shortlinks</li>
<li>WooCommerce Analytics</li>
<li>WordPress.com Toolbar</li>
</ul>
Lists of Jetpack modules in this plugin description should not be considered comprehensive or authoritative, and may change at any time.
<ul>
<li>According to the previously linked documentation page for Jetpack Development mode:</li>
</ul>
<blockquote>
Tiled Galleries requires the WordPress.com Photon CDN; however, in Development Mode, Jetpack provides a fallback so developers can have a similar experience during development and testing.
</blockquote>
Other modules may also have “reduced functionality” but retain “a good-faith representation of the feature.”

Development Mode for Jetpack

This plugin enables Jetpack Development Mode, which allows usage of certain Jetpack modules without connecting to WordPress.com.

Rolf Allard van Hagen

<a href="https://wordpress.org/plugins/jetpack/" rel="ugc">Jetpack</a> adds powerful features, but sometimes we don’t want them all… This light-weigth but effective plugin brings additional control over Jetpack.
<h4>Features</h4>
<ol>
<li>Blacklist / remove individual Jetpack modules.</li>
<li>Optionally prevent module auto-activation on connection or after an upgrade.</li>
<li>Optionally run Jetpack “unplugged”, without a WordPress.com connection.</li>
<li>Single site and Multisite compatible.</li>
</ol>
<h4>Examples</h4>
In most use cases, a carefully considered combination of Jetpack modules can be a really good thing. But not always is much consideration being done beforehand. Or site admins just don’t know all the implications…
<ul>
<li>Using Jetpack on a network? Then network incompatible WAF (Web Application Firewall) module should be blacklisted to prevent accidental activation!</li>
<li>Do you already use a light box provided by your theme or another plugin? Then blacklist the Carousel module to prevent accidental activation.</li>
<li>Or you’re running a Multisite and do not want any admins monitoring uptime with the Monitor module just to call you every time their site is briefly inaccessible?</li>
<li>Offer your own backup service? Backlist VaultPress if you do not care for VaultPress competition.</li>
<li>You’re running a school network and sites are managed by minors who are not allowed to sign up for an account at WordPress.com? Then use the Jetpack Offline Mode option to allow usage of modules that do not require a connection.</li>
</ul>
Any one of Jetpack’s modules can bring overlapping or even conflicting functionality. In such cases, being able to prevent (accidental) activation is a good thing.
<h4>Single site and Multisite</h4>
Although the original idea arose on a multisite installation, Module Control for Jetpack is developed for both single and multisite installations.
On multisite, it can only be network activated and allows global rules for Jetpack on all sites. At this point it also allows per-site changes by Super Admin only. Jetpack itself can, but does not need to be network activated. In that case, activate Jetpack on the main site and then network-activate Module Control.
For single site installations, plugin settings can be locked down by adding <code>define('JETPACK_MC_LOCKDOWN', true)</code> to wp-config.php for complete security. This can be useful to prevent other admins being able to reactivate blacklisted modules.
<h4>Development</h4>
The project can be forked and or contributed to on <a href="https://github.com/RavanH/jetpack-module-control" rel="nofollow ugc">Github</a>.
All contributions — be it in the form of feature requests, bug reports, translations or code — are welcome!

Module Control for Jetpack

This plugin fits perfectly with my needs.  For example when installing the Jetpack's gallery in a client's website I prefer not to setup a wordpress.com account just for that.



Very useful

Tames the beast known as Jetpack. Jetpack just seems to be getting worse all the time... This plugin works pretty good at getting some control back over it.
Thanks, Ravan

Tames the beast

like the fact that you can ban(blacklist) features in jetpack! Very good considering that jetpacks tends to do what it wants on your website.

Development Mode for Jetpack vs Module Control for Jetpack