Note: Solid Central is in the process of being rebranded as Kadence Central — both names may still show up across the product and its documentation during the transition, but the platform and features described here remain the same.
Some WordPress management tools stay shallow on purpose, offering just enough to handle updates and a basic backup. Solid Central goes the other direction — it’s built as a genuinely deep control panel, with dedicated tooling for staging pipelines, cross-server deployments, full site migrations, and vulnerability tracking tied directly into SolidWP’s own security product line. Here’s a full look at what that depth actually includes.
What Solid Central Is
Solid Central is a centralized dashboard for managing multiple WordPress sites — updates, backups, security, performance, and user access — from a single login instead of switching between individual wp-admin panels. It comes bundled with every StellarSites hosting plan, where sites are pre-linked automatically with no separate setup required, but it also connects to sites hosted anywhere through a lightweight plugin.
The Individual Site Dashboard
Selecting a single site from the Sites screen opens a detailed management view built around several tabs and a set of quick-action buttons:
- Site access — jump straight to the live frontend or log directly into that site’s WordPress admin without re-entering credentials.
- Backup and deployment shortcuts — trigger an immediate backup, or start a deployment/migration to another host.
- Tags and data refresh — organize sites with tags, and pull the latest plugin, theme, and status data from the connected install.
- Status badges — see your current plan tier, the site’s WordPress version, and whether Solid Security Pro is active, all at a glance.
Timeline
The Timeline tab is essentially an activity log crossed with a backup manager — it records events from both Solid Central itself and the connected WordPress site, tracks backup creation and restoration history, and lets you create, download, or restore a backup archive directly from that same view.
Admin
This tab mirrors a good chunk of the WordPress admin experience itself — plugins, themes, posts and pages, users, comments, and analytics — all manageable without leaving Solid Central.
Site Audit
Site Audits run on Google’s Lighthouse engine, scoring a site on performance, accessibility, and SEO. For agencies, this doubles as a client-facing value-add: a concrete, data-backed report showing what’s working and what needs attention.
Backups — NextGen
This is Solid Central’s current backup engine, replacing the older legacy Solid Backups plugin. It’s cloud-first and captures the entire site — database, files, plugins, themes, uploads, and configuration — in one complete backup rather than a partial snapshot. Sites still running the legacy plugin will see a separate “Backups” tab until they migrate over.
Security
Once Solid Security is installed on a connected site, its core settings become manageable right from this tab: authorized host IPs, currently locked-out user accounts (from failed logins or suspicious activity), and two-factor authentication configuration.
Search Console and Optimize
Linking a Google Analytics account unlocks Search Console data inside the dashboard. The Optimize tab handles basic database cleanup to trim bloat — though it’s described as a fairly blunt tool, so having a fresh backup on hand before running it is the sensible move.
Backups NextGen: Depth Behind the Basics
Beyond the individual site view, Backups NextGen is worth calling out on its own — it’s positioned as the central pillar of the platform’s data-protection story, covering full-site backups (files, database, and configuration together) with cloud storage behind it, rather than treating backups as an afterthought bolted onto an update manager.
Deployments vs. Migrations: Two Distinct Workflows
Solid Central draws a clear line between two similar-sounding but functionally different Pro features:
Deployments move file and database changes between two connected environments — typically staging to production — without changing the site’s domain. The process: connect origin and destination sites (with WordPress admin and SFTP/SSH credentials for each), start the deployment, and Solid Central copies files and database tables across, automatically rewriting URLs and paths to match the destination.
A standard site takes roughly 10–15 minutes, longer for large media libraries or complex databases, and the process runs in the background with a live status card and readable logs in the Timeline — no need to stay watching it.
Migrations move an entire site — files, database, plugins, themes, and media — from one host to another, including changing the destination’s domain to match the origin. The origin site must be on a real registered domain (not a temporary or placeholder one) for this to work. After the file and database transfer, the destination is initially reachable at a temporary URL for review — testing navigation, forms, admin access, and general functionality — before you finalize anything.
At that stage you can re-sync to pull in any last-minute changes from the origin, or cancel outright. Finalizing runs one last URL/path cleanup, after which you update your domain’s DNS records to point at the new host (allow up to 24 hours for propagation, though it’s often much faster). Once finalized, Solid Central disconnects the origin site, transfers backup scheduling to the destination, and preserves the original site’s historical logs even though the live connection has moved on.
Environments and Environment Groups
For teams running a Production/Staging/Development pipeline, Solid Central lets you bundle related sites into an Environment Group — a set of linked sites you can switch between without cluttering the main Sites list. Only the group’s designated “primary” environment (usually Production) shows up in the general Sites view; the others stay accessible through an Environment Switcher at the top of that site’s dashboard.
Group management supports adding more environments, reassigning which one is primary, or removing a site from the group entirely (which disbands the group if it was the last member left). This is purely an organizational feature — it doesn’t change how updates or backups work, just how you navigate between related sites.
Vulnerability Tracking
The Vulnerabilities page aggregates known security issues across every connected site, grouped by plugin, theme, or WordPress core, with a CVSS severity score, a priority indicator, affected-site counts, and a recommended fix for each. Three status states matter here: Active (currently detected somewhere in your portfolio), Resolved (confirmed gone after an update, removal, or deactivation), and Mitigated (protected by virtual patching through Solid Security Pro, but the vulnerable version is technically still installed — reduced risk, not eliminated). Status updates depend on Solid Security actively confirming the fix and pushing that confirmation back to Central, so a resolved issue can occasionally linger on the dashboard if that confirmation hasn’t come through yet — running a manual security scan on the affected site is the usual fix for that lag.
Reporting
Reports pull together site activity and update history into a document that can be generated once or scheduled to run automatically — daily, weekly, monthly, quarterly, semi-annually, or annually. Report content is flexible: Standard (posts, comments, plugin/theme updates), Standard + Backups, Standard + Security, Standard + Stats, a combined “Everything” option, or a fully custom selection of exactly what to include.
Reports can be saved inside your Solid Central account (retained for 30 days) or directly to a site’s own filesystem. Premium license holders can strip SolidWP branding entirely and apply their own logo, company name, contact details, and a customized email template — turning the reports into something that looks like it came entirely from the agency running it.
Security Architecture: Application Passwords
Rather than storing a site’s actual login credentials, Solid Central connects using WordPress’s built-in Application Passwords system — a scoped credential tied to a specific integration that can be revoked at any time without touching the main account password.
This connection is created automatically during the Smart Site Connection process and appears in that user’s profile labeled “SolidWP.” The practical benefit is straightforward: Solid Central never needs (or has) your actual WordPress password, every API call it makes is authenticated through a credential you can kill instantly, and if 2FA is active on Solid Security, Application Passwords can be explicitly allowed per user group without weakening two-factor protection elsewhere on the account.
WP-CLI Support
Solid Central offers limited command-line support focused specifically on licensing: checking license status (wp ithemes-licensing show), activating or deactivating a license, and updating the licensed site URL. Installing or updating SolidWP plugins isn’t yet supported through WP-CLI, so that part of the workflow still runs through the dashboard.
Connection Troubleshooting
Because Solid Central connects to sites remotely over the REST API, a number of server- and plugin-level settings can quietly block that connection — and SolidWP’s documentation is unusually thorough about diagnosing it.
Common culprits include Application Passwords being disabled by a security plugin, a site running on plain HTTP instead of HTTPS, a “Plain” permalink structure, a stripped Authorization header on the server, an outdated TLS configuration, or a host’s firewall (ModSecurity rule 225170 is specifically called out as a known blocker) rejecting Central’s requests outright. For persistent cases, Solid Central publishes its server IPs, required ports, and user-agent string so a host or security plugin can explicitly allowlist it, and a documented wp-config.php constant exists for sites that disconnect intermittently after certain plugin updates.
Who Solid Central Fits Best
The feature set skews toward agencies and freelancers running a real staging-to-production workflow rather than someone managing a handful of simple sites — the Deployments, Migrations, and Environment Groups features specifically assume you’re moving code and content between environments on a regular basis, not just pushing the occasional plugin update.
The depth of the vulnerability tracker and its tie-in with Solid Security Pro’s virtual patching also points toward users who take security seriously enough to want granular, per-site status rather than a simple “everything’s fine” indicator. For StellarSites customers, it comes as part of the hosting plan with sites pre-connected, making it close to a default choice rather than a separate purchase decision.
FAQs
Is Solid Central changing names?
Yes. Solid Central is transitioning to Kadence Central. During the changeover, both names may appear across the product and documentation, while the underlying platform and features remain the same.
What’s actually different between a Deployment and a Migration?
A Deployment moves file and database changes between two environments you already manage, such as staging and production, without changing the domain. A Migration moves an entire website to a new host and changes the destination domain to match the original site.
Do I need to babysit a deployment or migration while it runs?
No. Both processes run in the background after they are started. You can monitor progress through a live status card and review readable logs in the Timeline without keeping the page open.
What happens to the original site after a migration is finalized?
The original site is disconnected from Solid Central and its backup schedule stops. However, its historical timeline and migration records remain preserved. Solid Central then treats the new destination as the official site.
Can I organize a site’s staging and development copies without cluttering my main site list?
Yes. Environment Groups let you organize related Production, Staging, and Development sites together. Only the group’s primary environment appears in the main Sites list, while the other environments can be accessed through the environment switcher.
Why does a vulnerability I already fixed still show up as active?
Solid Central relies on Solid Security to confirm that a vulnerability has been fixed and send that confirmation back to the dashboard. If the confirmation hasn’t arrived because a scan hasn’t run, there’s a temporary connection problem, or Solid Security is disabled, the previous status can remain until the next successful check.
Does Solid Central ever see or store my actual WordPress password?
No. Connections use WordPress’s Application Passwords feature, which creates a revocable, scoped credential specifically for the integration instead of using your actual WordPress login password.
Can client-facing reports be fully rebranded to remove SolidWP’s name?
Yes, but white-label reporting is available only with premium licenses. It allows you to replace SolidWP branding with your own logo, company name, contact details, and customized report email template.
What’s usually the first thing to check if a site won’t connect to Solid Central?
First, check whether WordPress’s Application Passwords feature is enabled and isn’t being blocked by a security plugin. Also confirm that the site uses HTTPS and has a permalink structure other than Plain. These are common causes of connection failures.
Can I manage SolidWP licenses without opening the dashboard?
Partially. WP-CLI lets you check, activate, deactivate, and update the licensed URL for SolidWP products. However, installing or updating the plugins themselves still needs to be handled through the Central dashboard.
7 Alternatives to Solid Central
Here’s how seven other WordPress management platforms compare to Solid Central’s deployment- and migration-heavy toolset:
- MainWP — self-hosted and free for unlimited sites, a much simpler alternative without Solid Central’s staging/deployment pipeline tooling.
- ManageWP — cloud-based with a free tier and per-site, per-add-on premium pricing, lighter on technical depth than Solid Central’s environment groups and migrations.
- WP Umbrella — a single flat per-site rate built around Safe Updates and visual regression checks, rather than Solid Central’s deployment/migration workflow.
- InfiniteWP — self-hosted with a free core and annual license tiers, without Solid Central’s vulnerability-tracking depth or environment-group organization.
- WP Remote — matches Solid Central’s technical depth but focuses it on security and AI/API workflows rather than deployments and staging pipelines.
- Modular DS — cloud-based with fixed pricing and bilingual support, aimed more at day-to-day maintenance than Solid Central’s staging-to-production tooling.
- CMS Commander — shifts entirely away from deployment/staging workflows toward content sourcing and affiliate monetization.