Malcolm Peralty joins the Jukebox Podcast to discuss managed WordPress hosting, his path through the CMS world, and Pressable’s approach to performance, customer care, and AI-driven tooling.
Background
Malcolm has been part of the WordPress ecosystem for about 20 years, starting with very early versions of WordPress as a full-time blogger and later moving into project management and technical roles. He spent time working around Drupal and at Acquia as a technical account manager before returning to WordPress as a technical account manager at Pressable.
Technical Account Management at Pressable
At Pressable Malcolm’s role is not sales or standard support; technical account managers (TAMs) act as long-term WordPress and hosting strategists. They help customers plan for one-to-two-year horizons, advise on performance and plugin choices, and recommend optimizations that can change a customer’s required resources (sometimes even downgrading plans when appropriate). TAMs also perform deeper escalations when support issues need more than an hour to resolve.
Pressable’s infrastructure — WP Cloud — is a managed, private cloud (not AWS/Google). TAMs bridge customer needs and the infrastructure team, suggesting both software and hardware-focused improvements while relying on WP Cloud specialists for hardware decisions.
Performance, Cacheability, and Real-World Tradeoffs
Malcolm emphasizes cacheability as the major delineator for how much consultative support a site needs. Brochure or marketing sites that are highly cacheable generally run well on Pressable without intensive handholding. By contrast, sites using e-commerce, LMS, or plugins that break cache (like some Facebook/WooCommerce integrations) create uncached sessions and require more resources and custom solutions.
Pressable’s worker model is notable: one worker per vCPU (dedicated lanes) rather than high-density worker counts on a single vCPU. That design choice affects how resources are consumed and how predictable performance is under load.
Malcolm stresses the difficulty of communicating nuance to customers: single-user speed tests can be misleading. Platforms that appear faster for one person may fail under concurrent load. Much of the TAM role is customer education about realistic expectations, tradeoffs, and what changes would improve resilience.
Emerging and Future Hosting Technologies
Malcolm sees several key trends:
– WebAssembly and in-browser WordPress experiences: ephemeral WordPress installs and playgrounds that run client-side for rapid prototyping.
– Better caching and database replication: transactions require near-real-time replication for high-availability e-commerce; current replication strategies can introduce unacceptable latency for transactional sites.
– Virtual clusters and multi-datacenter approaches that appear as a single local server, improving resiliency and failover.
– Improved logging, auditing, and actionable visibility: more usable, compressed, and AI-assisted audits are needed to make sense of massive amounts of operations data without overwhelming storage or staff.
AI and Pressable’s MCP (Managed Control Panel)
Pressable is developing MCP, an AI-powered control panel designed to accept natural language commands for hosting tasks. Planned capabilities include:
– Creating sandboxes/staging sites on demand, pulling code and assets from production, and notifying the developer when they’re ready.
– Searching managed sites for specific plugin versions (e.g., Gravity Forms updates) and performing bulk actions like updates across many sites.
– Acting on any control-panel action available via API: MCP exposes API endpoints so AI agents can operate the same controls a human could in the UI.
Guardrails, Backups, and Auditability
Malcolm acknowledges the risks: AI can make mistakes or take unintended actions. Pressable plans multiple safeguards:
– Human-in-the-loop confirmations for destructive operations.
– Robust backups: hourly database backups, daily file-system backups, and protections like simlinked core files that prevent accidental removal of core WordPress code.
– Audit logs and human-readable records that capture actions, providing traceability and rollback capability. Malcolm uses system prompts asking the AI to back up before acting and to produce step-by-step markdown logs of what it did.
He highlights the importance of readable, actionable audit trails so users and support staff can unpick multi-step AI-driven changes and selectively roll back where needed.
Who MCP is For
MCP will be most valuable for agencies and teams managing many sites (tens to thousands) where automation and bulk tasks dramatically reduce time-to-delivery. Single-site users are less likely to need advanced MCP features initially. Early adopters will likely be developers and agencies comfortable untangling complex setups and iterating with tooling.
Human vs AI Support Balance
Malcolm believes features should be human-first and AI-enhanced rather than AI-first. AI will be necessary to remain competitive—agencies expect faster delivery aided by AI—and can free human support to focus on customers who need personalized help. However, companies must carefully manage the shift to avoid eroding trust or over-automating human relationships.
Operational and Cost Challenges from AI
AI introduces new operational costs and attack patterns:
– Bots and AI crawlers can generate high volumes of uncached traffic and uncached sessions (e.g., repeatedly adding/removing items from carts), costing bandwidth and compute and complicating billing and mitigation.
– Hosting providers face decisions about whether to absorb these costs, block certain agents, or pass costs to customers. Solutions include advanced bot detection, IP/user-agent blocking, and rate-limiting, but sophisticated bots can evade simple measures.
– Storing audit logs, backups, and AI-generated artifacts raises storage and retention costs. Providers must balance customer protection with feasible pricing models.
The Changing UX of WordPress Sites
Malcolm predicts a future where many interactions with WordPress hosting and even site edits will happen through AI assistants, IDE integrations, or other non-traditional UIs. This could reduce the need for many users to visit the WordPress admin directly; instead, they’ll prompt AI or development tooling to change themes, create blocks, or update content. That will change workflows and support patterns and require new tooling for observability and reversibility.
Practical Advice and Closing
– Cacheability is central: know whether your site can be cached or whether user-specific, uncached sessions are unavoidable.
– Backups and audit logs will be more important than ever; ensure you can roll back changes made by automation.
– AI tooling will accelerate workflows, especially for agencies and multi-site managers, but guardrails and human oversight are essential.
– Hosting providers must adapt to new bot traffic patterns, replication needs, and storage demands driven by AI.
Contact
Malcolm directs listeners to Pressable at pressable.com and his personal site at peralty.com. He’s available in WordPress Slack communities and on LinkedIn for professional connections.