Disallowed Plugins on BionicWP

To maintain site stability, speed, and security, BionicWP restricts the use of certain plugins that conflict with our optimization stack or introduce risks. This article outlines which plugins are disallowed and why, so you can plan your builds and migrations accordingly.

Some plugins duplicate functionality already built into the BionicWP platform (like caching or backups). Others have been found to cause performance or security issues. When a disallowed plugin is detected, we’ll automatically deactivate it during onboarding or optimization — and let you know.

We constantly review this list and update it based on plugin behavior, compatibility, and redundancy.

Here are the most common reasons a plugin may be disallowed:

• Caching Plugins – Conflict with our built-in caching layer

• Backup Plugins – Overlap with BlogVault and platform-level backups

• Security Plugins – Duplicate protections already provided at the server level

• Performance Boosters – Often break sites or override our optimization stack

• SSL Managers – Handled natively through our platform

• Database Cleanup – Can be too aggressive and risk breaking the site

1. Before migrating a site, compare the plugin list to our disallowed list

2. Remove or replace flagged plugins before onboarding

3. If a disallowed plugin is detected after migration, we’ll deactivate it and notify you

4. Reach out to support if you need help finding an alternative plugin

(Not exhaustive — contact support if unsure)

• WP Super Cache

• W3 Total Cache

• WP Fastest Cache

• Autoptimize

• Breeze

• WP Rocket (already provided)

• UpdraftPlus

• BackWPup

• Wordfence

• iThemes Security

• Really Simple SSL

• Better Search Replace

• WP Optimize

• NitroPack

• SGO (SiteGround Optimizer)

• Redis Object Cache (unless pre-approved)

If you're unsure whether a plugin will conflict with our stack, reach out to our support team before installing. We'll help you find an approved, performance-friendly alternative.