Local First
WPlura Free plugins are designed to provide useful local WordPress workflows before Pro or Cloud features.
Integration
WPlura and WordPress
How WPlura products fit WordPress local plugin workflows, wp-admin evidence, optional cloud connection, and WordPress.org distribution.
Problem, cause, fix, verify
Problem
Users need to know what runs locally in WordPress and what requires optional WPlura Cloud connection.
Audience
WordPress site owners and agencies evaluating WPlura product fit.
First check
WPlura Free plugins are designed to provide useful local WordPress workflows before Pro or Cloud features.
Verify
The practical decision is simple: install the relevant local plugin when the site needs in-admin evidence, connect Cloud only when the workflow requires account-backed services, and use product documentation to confirm the exact boundary before advising a client.
Editorial trust
- Publisher
- WPlura Editorial Team
- Published
- Updated
- Content type
- Integrations
On this page
Integration Boundary
Users need to know what runs locally in WordPress and what requires optional WPlura Cloud connection.
For: WordPress site owners and agencies evaluating WPlura product fit.
Compatibility Review
What to confirm before connecting it
Cloud Boundary
The Cloud connector owns account, consent, entitlement, and product-specific cloud requests for compatible workflows.
What Stays In WordPress
Local plugin screens, settings, diagnostic findings, reports, and exports remain tied to the installed product. That matters for agencies that need evidence inside wp-admin before deciding whether a connected workflow is justified.
What Requires Connection
Account identity, subscription checks, product access, consent, and cloud-assisted requests belong to the connected layer. A page should not imply that free local plugins automatically send private site data to WPlura Cloud.
Operational Fit
Use this integration page to decide whether the next step is a local product review, a WordPress.org plugin install, product documentation, or a connected account workflow. The right answer depends on the product and the evidence the user needs.
Verification Checklist
Confirm the product slug, installed plugin, active plan, connection state, consent status, and source documentation before describing a WPlura feature as available for a specific WordPress site.
Handoff Notes
When a site owner asks what WPlura can see, answer by product. Security, diagnostics, backup, revenue, catalog, and reporting tools each collect different local evidence, so integration guidance should point to the relevant product page instead of making one broad platform claim.
Reader Decision
The practical decision is simple: install the relevant local plugin when the site needs in-admin evidence, connect Cloud only when the workflow requires account-backed services, and use product documentation to confirm the exact boundary before advising a client.
Support level: native integrationLast reviewed: 2026-09-16
Compatibility
What this integration means
Data Handled
- Local WordPress settings and product-specific findings.
- Optional cloud account and entitlement checks through Web Plura Cloud.
- Product-specific reports where the active workflow supports them.
Compatibility
- WordPress compatibility is product-specific.
- Free plugins remain useful locally where product docs state local features.
- Cloud connector is shared across compatible products.
Limitations
- WPlura does not replace WordPress core, hosting, backups, or payment providers.
- Cloud workflows require explicit connection and consent.
- Each product has its own data scope, admin screens, and optional connection behavior.
Sources