Malcolm Peralty joins the Jukebox Podcast to discuss managed WordPress hosting, his career in the CMS space, and how Pressable approaches performance, customer care, and AI-powered tooling.
Background
Malcolm has worked in and around WordPress for roughly 20 years. He started as a full-time blogger on early WordPress releases, moved into project and technical roles, spent time working with Drupal and at Acquia as a technical account manager, and returned to WordPress as a technical account manager (TAM) at Pressable.
The Technical Account Manager role at Pressable
Unlike sales or first-line support, Pressable’s TAMs act as long-term hosting and WordPress strategists. They plan with customers on one- to two-year horizons, advise on performance and plugin choices, and recommend optimizations that can change resource needs (including downgrades when appropriate). TAMs also handle deeper escalations for issues that take more than an hour to resolve.
Pressable runs WP Cloud, a managed private cloud (not built on AWS/Google). TAMs translate customer needs into actionable suggestions for both software and hardware, while relying on WP Cloud specialists for infrastructure decisions.
Performance, cacheability, and real-world tradeoffs
Cacheability is the primary factor determining how much hands-on support a site requires. Highly cacheable brochure or marketing sites typically perform well on Pressable with minimal intervention. Sites that rely on e-commerce, LMS, or plugins that break caching generate many uncached sessions and need more resources and custom solutions.
Pressable’s worker model uses dedicated lanes—one worker per vCPU—instead of packing many workers onto a single vCPU. That architecture makes resource consumption and performance under concurrent load more predictable.
Malcolm emphasizes that single-user speed tests can be misleading. A platform that looks fast for one person may underperform with concurrent users. A big part of the TAM job is educating customers about realistic expectations, tradeoffs, and the changes needed to improve resilience and capacity.
Emerging hosting trends Malcolm watches
– WebAssembly and in-browser WordPress sandboxes for instant, ephemeral installs and rapid prototyping.
– Better caching plus near-real-time database replication for transactional e-commerce; current replication methods can add unacceptable latency for some workloads.
– Virtual clusters and multi-datacenter setups that behave like a single local server to improve failover and resiliency.
– Smarter logging and auditing: compressed, actionable logs and AI-assisted audits to surface meaningful signals without overwhelming storage or staff.
Pressable’s MCP — an AI-powered control panel
Pressable is building MCP (Managed Control Panel), an AI-enabled interface that accepts natural-language commands to manage hosting tasks. Planned capabilities include:
– On-demand sandbox/staging creation that pulls code and assets from production and notifies developers when ready.
– Site-wide searches for plugin versions (for example, locating Gravity Forms instances) and bulk operations like mass updates.
– Acting on any control-panel action exposed via API, so AI agents can perform the same operations available in the UI.
Guardrails: backups, confirmations, and auditability
Malcolm recognizes the risks of AI acting without constraint. Pressable intends to layer multiple safeguards:
– Human-in-the-loop confirmations for destructive or risky operations.
– Robust backups: hourly database snapshots, daily filesystem backups, and protective measures such as simlinked core files to prevent accidental removal of WordPress core code.
– Detailed audit logs and readable records capturing actions and changes so teams can trace and roll back multi-step AI-driven modifications. Malcolm uses prompts that require the AI to back up systems before changes and to produce step-by-step, human-readable logs of its actions.
Who benefits most from MCP
MCP’s greatest value will be for agencies and teams managing many sites—dozens to thousands—where automation and bulk operations significantly reduce delivery time. Solo site owners are less likely to need advanced MCP features at launch. Early adopters will be developers and agencies comfortable iterating on tooling and untangling complex configurations.
Balancing human and AI support
Malcolm advocates a human-first, AI-enhanced approach. AI should speed routine work and free humans to handle personalized, high-touch support. Agencies expect faster delivery aided by AI, but providers must manage the shift carefully to preserve trust and avoid over-automation that damages relationships.
Operational and cost challenges introduced by AI
AI and automated agents create new attack surfaces and operational costs:
– Bots and AI crawlers can generate large volumes of uncached traffic and behave in ways that force uncached sessions (for example, repeatedly adding and removing items from carts), driving up bandwidth and compute costs.
– Providers face choices: absorb those costs, block offending agents, or pass costs to customers. Mitigations include advanced bot detection, IP and user-agent blocking, and rate-limiting, though sophisticated bots can evade simple measures.
– Storing audit logs, backups, and AI-generated artifacts increases storage and retention costs. Providers must balance customer protection with sustainable pricing.
The evolving WordPress UX
Malcolm expects more people to interact with hosting and site edits via AI assistants, IDE integrations, or other non-traditional interfaces. Many users may no longer need to visit wp-admin directly; instead they’ll prompt AI or developer tools to update themes, create blocks, or change content. That shift will change workflows and support needs and will require better tooling for observability and reversible actions.
Practical takeaways
– Determine cacheability: know whether your site can be safely cached or if user-specific uncached sessions are unavoidable.
– Prioritize backups and audit logs so automation can be rolled back if needed.
– AI tooling accelerates workflows, especially for agencies and multisite managers, but must include guardrails and oversight.
– Hosting providers must adapt to new bot traffic patterns, replication demands, and storage needs driven by AI.
Contact
Malcolm points listeners to Pressable at pressable.com and his personal site at peralty.com. He is active in WordPress Slack communities and available on LinkedIn for professional connections.