Rebrand b.s.

Hi @kcrusher ,

Id love to clear up exactly what is happening here and what this means for your active subscription. We did send out an email update regarding this product consolidation. However, weve since received feedback from several users that the notification unfortunately landed in their spam or junk folders. I am very sorry that you missed that communication.

Regarding your license, if you have an active subscription or a lifetime license purchased prior to these updates, your plan remains fully valid, active, and grandfathered in. These legacy products will continue to receive feature improvements and updates that you have full access to. You absolutely do not need to purchase a new bundle to keep utilizing the security tools you have already paid for.

If you have any specific questions about your account or need help verifying your license status, please feel free to reach out to us directly at https://software.liquidweb.com/support so we can get it sorted out for you.

Hello,

I understand the frustration here, and I think the main issue is not only the rebrand itself, but the lack of clear and practical information for existing users.

The public plugin is now shown as Kadence Security, while many existing installations and customer accounts still refer to Solid Security, Solid Security Pro, iThemes Security, or legacy licensing. That creates real confusion.

For example, the public Kadence Security plugin currently appears to be at version 10.0.2, while Kadence Security Pro appears to be at version 9.0.4. At the same time, existing users are told that legacy products will continue to receive updates and that their access remains valid.

That may be true, but the update path is not clear enough.

Existing users should not have to guess whether they should:

• keep using the old Solid Security / Pro plugin;
• install Kadence Security instead;
• wait for an update through the legacy license system;
• or reconnect/revalidate their license somewhere else.

This is even more important for a security plugin. Updates are not just cosmetic or optional. They are needed to keep up with new attack methods, security improvements, compatibility changes, bug fixes, and new protection features. When the update path is unclear, users may delay updates or stay on an older version, which is not ideal for a plugin whose main purpose is to improve website security.

For a security plugin, this kind of rebrand should be explained very clearly inside the WordPress dashboard and in the customer account area, especially when plugin names, branding, licensing and version numbers all changed at the same time.

So yes, I agree with the concern raised here. The issue is not just the new name. The issue is the lack of a clear migration and update explanation for existing users.

A simple official clarification would help a lot:
Which plugin should existing users use now?
Which version should they currently be on?
How should updates appear through the old/legacy licensing system?
And do the same Pro features remain available as before?

That would avoid a lot of unnecessary confusion.