Welcome to the Jukebox Podcast from WP Tavern. Nathan Wrigley interviews Malcolm Peralty, a WordPress veteran of nearly 20 years now working as a technical account manager at Pressable, a managed WordPress hosting company.
Malcolm’s background
– Began with WordPress 0.72 as a full-time blogger, moved into project management, agencies, and some work in the Drupal/Acquia space.
– Took a Technical Account Manager (TAM) role at Acquia before returning to WordPress when Pressable offered a competitive position.
– His TAM role blends project management, hosting knowledge, and WordPress expertise.
What a Technical Account Manager does at Pressable
– TAMs are strategists focused on medium-to-large customers: planning site architecture a year or two ahead, tracking end-of-life technologies, optimizing performance, and advising on plugins and alternatives.
– They differ from sales or basic support: TAMs work proactively on long-term strategy, optimizations, and resource planning.
– TAMs may advise customers to downgrade plans after successful optimizations — helping both the customer and Pressable’s resource utilization.
Platform and infrastructure
– Pressable runs WP Cloud — its own cloud stack rather than using AWS or Google Cloud.
– TAMs act as a bridge between customers and the WP Cloud team, offering WordPress-specific insight while leaving hardware design to infrastructure experts.
– Pressable targets a range from simple brochure sites (highly cacheable) to complex uncached workloads like WooCommerce and LMSs.
Performance, caching, and trade-offs
– Cacheability is a key delineator: static marketing sites are easy to serve and resilient; dynamic e-commerce and LMS sites create uncached sessions requiring more resources.
– Plugin bloat and builder plugins (e.g., Elementor, Divi) can seriously impact performance.
– Some hosts mask website issues with heavy caching layers or oversized hardware, which can look fast for single-user tests but fail under scaled traffic (e.g., sales spikes).
– Pressable’s architecture includes a one worker per VCPU model (dedicated processing lanes), contrasted with hosts that multiplex many workers over fewer CPUs. This structure improves throughput and resilience under load.
TAM interactions with infrastructure
– TAMs provide recommendations to WP Cloud about optimizations and competitive features but generally don’t dictate hardware decisions.
– Discussions explore database replication, virtual clusters, and ways to make resiliency and replication faster and more reliable.
Emerging hosting trends and challenges
– WebAssembly and in-browser ephemeral WordPress installs (playgrounds) are interesting and may change hosting interactions.
– Better caching, database replication, and virtual clusters are key near-term priorities to reduce replication latency and improve high availability.
– Current replication can introduce seconds of latency; in high-transaction events that can mean lost purchases. Real-time streaming and low-latency replication are important.
– Auditability and human-readable logging are weak spots industry-wide: tracing who changed what, when, and reversing it quickly remains difficult. Backups are a fallback but not an ideal method for fine-grained rollback.
AI and Pressable’s MCP (Managed Control Panel)
– Pressable is developing an MCP — an AI-powered control panel to let users deploy and manage WordPress sites via natural language.
– Intended use cases include:
– Spinning up sandboxes/staging sites on demand: pull code, sync uploads and DB, run tests, all via a natural language prompt.
– Bulk tasks across many sites: e.g., find sites needing a specific plugin update and apply updates automatically.
– Developer workflows: integrate with IDEs, GitHub, or local AI agents to automate staging, deployments, and environment setup.
– The MCP exposes control panel APIs so any AI agent can act on user behalf; the challenge is ensuring the AI understands API semantics and expected behavior.
Guardrails, safety, and human-in-the-loop
– Phased rollout: features will be exposed gradually with guardrails and human confirmation where necessary.
– Pressable keeps backups (hourly DB, daily filesystem) and restrictions (e.g., main WordPress core is simlinked to prevent deletion).
– Users can connect different AI engines (local or cloud); responsibility for some safeguards falls to the user/system prompts, but Pressable also plans system-level protections.
– Recommended approach: human-first, AI-enhanced workflows (AI augments humans, not replaces them). Initially MCP targets agencies and developers who can manage complexity.
Audit logs, reversibility, and UX
– Natural language-driven changes can create many quick iterations (theme tweaks, content edits); audit logs and readable summaries are crucial to review and roll back specific changes.
– Malcolm suggests backing up before AI makes big changes and having the AI create a step-by-step markdown of actions performed.
– The future will demand better UI for viewing and reversing changes and for presenting audit trails clearly.
AI-driven maintenance and automation
– Malcolm already uses AI to generate scripts that run WP-CLI commands, database checks, and code searches to surface optimization opportunities — speeding diagnostics and actioning fixes.
– He foresees AI not only creating code but also being used to maintain and update AI-created artifacts, reducing human maintenance burden over time.
– There’s potential for AI to create custom themes, plugins, or blocks tailored to a brief rather than pulling packaged marketplace assets.
New costs and bad actor problems
– AI crawlers and bots can generate unexpected load and uncached traffic (e.g., bots repeatedly adding and removing cart items), increasing resource use and costs.
– Blocking bots can be circumvented; AI agents rotate IPs or user agents, causing repeated hits and more load.
– This introduces a tension: who bears the cost of AI-driven indexing, backups, logs, and bandwidth? Hosts must decide whether to absorb costs or bill customers for extra usage — a thorny commercial and UX issue.
Human relationships, scaling, and product strategy
– Though AI can offload repetitive tasks and enable new workflows, maintaining human relationships remains important. Pressable aims for AI tools to free humans to focus on higher-touch customers rather than replace human support entirely.
– Agencies pushing for faster delivery want tools that allow rapid proof-of-concept creation (e.g., iterate a sandbox during a client meeting). If hosts don’t support this, agencies will choose other platforms.
– Pressable’s goal: deliver AI-assisted capabilities for agencies at scale while retaining human-first support for customers who value it.
Practical examples and user scenarios
– A developer could ask the MCP to spin up a sandbox, pull production assets, push a code branch, and signal when ready.
– An administrator could ask for all sites on the platform with a specific plugin version and request updates.
– A content owner could ask for a seasonal theme swap or localized CSS changes and have the MCP perform and document the changes.
– All these require robust auditability, backups, and permission checks.
Where to find Malcolm and Pressable
– Pressable: pressable.com
– Malcolm Peralty: peralty.com; active on LinkedIn and WordPress community channels.
Closing
Malcolm’s view balances optimism for AI’s efficiencies with caution about safety, auditing, and cost. Pressable’s MCP aims to make hosting actions available via natural language while preserving human oversight, improving scalability, and addressing the technical complexities of modern WordPress sites — from cache strategies and workers to low-latency replication and bot mitigation.