Vexal Hub overview
Vexal Hub is the multi-tenant control plane for connected WordPress sites: Operator Console for staff, Workspace for customers, machine authentication for Hub↔site pulls, and fail-closed authorization.
Historical note: Earlier documentation described Hub as a future-only layer. Hub 0.3.x ships Operator Account Management, /vexal-login/, Workspace shell, membership, and Intake module/workspace ingest. Archive that older assumption—do not treat Hub as “not production.”
Two human surfaces
| Surface | Audience | Entry |
|---|---|---|
| Operator Console | Operators / admins | wp-admin (vexal-sites, Accounts, Integration Health) |
| Vexal Workspace | Customers with membership | /vexal-workspace/ after /vexal-login/ |
Not merely a dashboard
- Account membership and site assignment
- Customer provisioning (subscriber +
vexal_hub_access) - Customer Admin Guard (customers blocked from wp-admin)
- Machine credential vault and remote module ingest
- Module Manifest + Workspace contracts with Intake
- Operator preview (explicit; does not create customer context)
Platform fit
Hub sits beside SmartBlocks (site intelligence), Intake (lead forms + lead Workspace), Media, Portfolio, and SearchAsist Engine. See Vexal Ecosystem and Experience Framework.