MSP technology engineer with 15+ years in the industry. Co-owner of an MSP since 2020. By day I architect cloud, messaging, and network infrastructure. By night I build the WordPress plugins that MSPs use to run their businesses.
Six commercial WordPress plugins, designed as one ecosystem. Each solves a real problem I encountered running an MSP.
WordPress admin reimagined
I rebuilt the entire WordPress admin because wp-admin is hostile to end users. GLASS is an admin shell, canvas page builder (58 sections), Blinds mega headers, Mats footers, and a full themeless rendering engine. This site runs on it.
The billing platform I needed
WooCommerce was overkill for what MSPs need — invoices, card payments, and a customer portal. So I built a standalone Stripe billing platform with autopay, subscriptions, QuickBooks/Xero sync, and PDF invoices via WeasyPrint.
Autotask PSA on the web
Our MSP customers needed to see their tickets, approve quotes, and manage services without calling us. MSP Hub extends Stripe Pro's portal with Autotask PSA integration, contract e-signing, white-label branding, and an accounting bridge.
2FA that just works
Every WordPress MFA plugin I tried was bloated or unreliable. I wrote a pure-PHP RFC 6238 TOTP engine with zero dependencies — trusted devices, per-role enforcement, hidden login URL, activity log, and MSP Hub integration.
Backups I actually trust
After years of managing client WordPress sites, I built a backup plugin that encrypts at rest (AES-256-GCM), verifies integrity (SHA-256 checksums), and supports the cloud providers MSPs actually use — SharePoint, OneDrive, Google Drive, S3.
Email that actually sends
WordPress's wp_mail() is unreliable. I built an SMTP plugin with 8 providers, one-click Microsoft 365 OAuth (no Azure AD app registration), domain health monitoring, email queue with retry, and AES-256 credential encryption.
Every plugin shares the same security model (AES-256 encryption, nonce-protected AJAX, capability-gated admin), the same UX system (CSS design tokens, Nunito Sans typography, Pewter Plum neutral scale), and the same licensing infrastructure (RSA JWT tokens, HMAC verification, Sentinel MU-plugin). They're designed as one system that happens to ship as six packages.
From helpdesk to MSP co-owner to plugin architect.
Began my career in managed services. Helpdesk, desktop support, then quickly into server and network infrastructure.
Specialised in Microsoft cloud — Exchange, Office 365 (before it was M365), Azure AD, hybrid deployments. Became the messaging and cloud guy.
Added network architecture — firewalls, VPNs, SD-WAN, switching. Full-stack infrastructure engineer across cloud and on-prem.
Became co-owner of the MSP. Started building WordPress plugins to solve the problems I saw every day.
First commercial plugin — Net-14 invoicing and Stripe gateway. Built because WooCommerce was too heavy for simple MSP billing.
Autotask PSA integration for customer self-service. Built server-authoritative licensing with RSA JWT tokens and HMAC verification.
Migrated to asymmetric RSA tokens. Introduced Sentinel MU-plugin for tamper detection. AES-256 encryption across all plugins.
MFA, Backup, SMTP Pro. Three new plugins in one year, all sharing the same architecture, licensing, and UX system.
The most ambitious project — a complete WordPress admin replacement. Canvas editor, 58 section types, Blinds/Mats, themeless rendering. This site is the proof.
The technical stack across both the day job and the plugin development.
Microsoft 365, Exchange Online, Azure AD / Entra ID, Teams, SharePoint, Intune, conditional access, hybrid Exchange, migration tooling. 10+ years.
Firewalls (FortiGate, SonicWall, Meraki), VPN/SD-WAN, VLAN architecture, switching, DNS/DHCP, WiFi design. Enterprise and SMB.
RSA asymmetric JWT, AES-256-CBC/GCM encryption, HMAC request verification, TOTP 2FA, nonce-protected APIs, blind-index encrypted search.
Stripe API (PaymentIntents, Subscriptions, Invoicing), SCA/3DS, server-side price authority, QuickBooks + Xero OAuth2 accounting sync.
Multi-plugin ecosystems with shared infrastructure, portable licensing modules, command bus patterns, MU-plugin enforcement, shared database layers.
CSS design token systems, canvas page builders, windowed desktop environments, responsive portals, sub-100KB themeless pages. Zero jQuery.
When I'm not building infrastructure or writing PHP, I'm usually soldering something. I'm into electronics, mechanical keyboards (custom builds, QMK firmware, the whole rabbit hole), and anything that involves making physical things work better. The same attention to engineering that goes into a keycap profile or a PCB layout is what goes into my plugin architecture.
I'm always interested in challenging WordPress architecture problems. If you need a plugin built properly, let's talk.