Platform

A clear operating model for WordPress protection

WPLURA aligns local plugin controls with cloud-side durable orchestration so security, backup, diagnostics, and response workflows stay understandable at every scope.

Core Layers

How the platform fits together

Each surface has a job. The public website explains products, the plugin handles local site ownership, the customer panel handles customer-owned cloud workflows, and cloud-admin handles internal operations.

WordPress plugin layer

Local site-agent workflows for WordPress admins who need practical controls inside the environment they operate every day.

  • Local checks and product status
  • Nonce/capability-protected admin actions
  • Secure cloud handoff without password collection

Cloud customer layer

Customer-owned sites, subscriptions, reports, support, and account workflows without platform-wide admin data.

  • Customer site and product visibility
  • Billing and entitlement context
  • Team ownership and support routing

Cloud authority layer

Durable product intelligence, policy decisions, retention/deletion state, and operational workflows that must survive stateless runtimes.

  • Entitlement and quota authority
  • Durable jobs and reports
  • Audit, retention, deletion, and incident lifecycle

Boundary Model

Plugin is local, cloud is authority

This boundary keeps WordPress.org distribution clean and keeps cloud workflows durable across Docker, AWS, and horizontally scaled runtimes.

Plugin scope
Local WordPress admin UX, local site actions, product-specific settings, and signed site-agent communication.
Customer scope
Customer-owned account, sites, subscriptions, support, reports, and team access.
Admin scope
Platform operations, global customers/sites, system jobs, product catalog, security feeds, and billing operations.
Public scope
Website pages, SiteCheck, support/legal entry points, docs, pricing, and product education.

Team Model

Operational ownership by role

Site owner

Owns risk posture, subscription decisions, and sensitive approvals.

Operator

Handles daily checks, alert review, and approved response work.

Manager

Coordinates priorities across people, products, and connected sites.

Support team

Receives context-rich escalation for urgent incidents or account issues.