beaconwp

BeaconWP Platform Framework

BeaconWP

BeaconWP is a modular WordPress platform framework built to turn standard WordPress installs into cleaner, more scalable, product-ready sites. Core stays lean while modules, visual packs, cloud authorization, update tooling, documentation, and customer access expand the platform without bloating the base install.

View Products Read Docs Members Area

Current BeaconWP Architecture

BeaconWP Core / Lite is the foundation layer. It should remain lean and focused on platform infrastructure: admin shell, dashboard structure, module registry, module loader, visual pack runtime, settings framework, update handling, compatibility checks, and basic diagnostics.

Premium capability belongs in separately installed modules and packs. Core should not permanently carry store systems, forum systems, advanced diagnostics, white-label controls, cloud licensing tools, AI features, or marketplace functionality unless they are required for the foundation itself.

Lean Core

Core handles the platform foundation, not every product feature.

Admin shell
Dashboard shell
Module loader
Visual pack runtime
Settings framework
Update foundation

Modules

Feature expansion lives in optional modules.

Diagnostics Pro
Dev Tools
SEO Signal
Signal Analytics
Quartermaster
Cloud Connector

Visual Packs

Visual packs control assigned page presentation without hijacking normal WordPress pages.

Lighthouse
Nebula
Cinematic Cove
Future premium packs

Cloud Capability

BeaconWP is designed to connect to HPS Unified Cloud through a cloud authorization layer. The cloud should handle licensing, entitlement checks, activation slots, subscription state, signed update access, usage reporting, and future SaaS-grade controls while keeping BeaconWP Core backend-agnostic.

License Validation

Cloud-backed license status checks for Core, modules, packs, and customer entitlements.

License key validation
Tier detection
Subscription status
Grace/offline handling

Activation Slots

Cloud-authoritative site activation management.

Fingerprint binding
Activation limits
Deactivate / release slot
Environment-aware validation

Entitlements

Product access should be controlled by cloud-issued entitlement results.

Allowed modules
Allowed packs
Feature flags
Bundle profiles

Signed Updates

Future update access can be tied to entitlement and signed release feeds.

Update eligibility
Package verification
Checksum support
Recovery-safe updates

Usage Reporting

Optional usage reporting can support SaaS features, overage billing, AI credits, and agency limits.

Usage events
Token/call metering
Overage checks
Telemetry-ready structure

Cloud Connector

Cloud integration should live in a connector/module layer instead of hard-wiring HPS Cloud directly into Core.

Default provider: HPS Unified Cloud
Backend-agnostic Core contract
Enterprise provider support later
Signed JSON authorization results

Cloud API Direction

BeaconWP should consume a stable JSON authorization contract rather than hardcoded keys or local-only checks. The cloud-facing contract should support license validation, activation, deactivation, status checks, feature access, usage reporting, telemetry, and update entitlement.

Core Endpoints

/cloud/beaconwp/status
/cloud/beaconwp/license
/cloud/beaconwp/modules
/cloud/beaconwp/ping

License Object

Status
Tier
Environment
Activation limit
Activations used
Features
Grace state

Rules

Strict test/live separation
Signed responses
Soft-fail support
No hardcoded customer keys
No module entitlement drift

Release Stage

BeaconWP is in a late release-candidate stage. The current work is focused on stabilizing Core behavior, finalizing module boundaries, improving visual pack reliability, preparing customer-facing documentation, aligning cloud licensing, and tightening the product/store/member flow.

Launch Readiness

Final polish, documentation, store flow, module readiness, and support paths.

SaaS Readiness

Cloud-connected licensing, entitlements, updates, subscriptions, and usage reporting.

Marketplace Direction

Future module, visual pack, and third-party product ecosystem.