Architecture Overview

Understand the modular architecture of RakuWP and how the plugin communicates with the panel.

How RakuWP Works

RakuWP consists of two parts that work together:

  • The WordPress Plugin — installed on your WordPress site. It loads service modules, communicates with the panel, and extends WordPress functionality.
  • The Panel — a web application where you manage licenses, sites, companies, and subscriptions. The plugin talks to the panel via a REST API.

Plugin Structure

The plugin follows a modular architecture. At its core is a lightweight loader that handles:

  • License validation — verifying your license key against the panel server
  • Service discovery — loading only the service modules enabled for your site
  • Health checks — periodic pings to report site status and plugin version
  • Auto-updates — checking for new plugin versions from the panel

Service Modules

Each service module is a self-contained unit that adds specific functionality to WordPress. Service modules:

  • Have their own settings, hooks, and admin UI
  • Can be enabled or disabled per site from the panel
  • Are loaded conditionally — disabled services use zero resources
  • Follow a standard base class pattern for consistency

Communication Flow

  1. The plugin makes an HTTPS request to the panel API
  2. The request includes the license key for authentication
  3. The panel validates the license and returns the response
  4. The plugin caches responses locally to minimize API calls
Note: All communication between the plugin and panel happens over HTTPS. Your license key is never exposed in URLs — it is always sent in the request body.
Next Hooks and Filters