Malcolm Peralty, a Canadian WordPress veteran who’s worked with the platform since its earliest releases, joins the Jukebox Podcast to discuss managed WordPress hosting, performance, infrastructure, and the rising role of AI in hosting workflows. He now serves as a Technical Account Manager (TAM) at Pressable, where his focus is long-term strategy, performance optimization, and bridging customer needs with Pressable’s WP Cloud.
Background and role
Malcolm’s path includes two decades around WordPress, project management, agency work, and a stint in the Drupal/Acquia world. He explains that a TAM is neither sales nor standard support: the role takes a strategist’s view—planning where a site should be in one to two years, advising on technologies, handling end-of-life concerns, and recommending more performant plugin or architecture choices. TAMs also help pre-sales decisions for which product tier fits a site and what customizations or optimizations are advisable.
Proactive optimisation and WP Cloud
Pressable’s TAMs sometimes proactively monitor platform data and server instances, spotting sites that use more resources than expected and recommending optimizations. Interestingly, Malcolm points out that optimizing a site can mean advising customers to downgrade their plan—good for the customer and for shared server resources. Pressable runs its own WP Cloud rather than relying on AWS or Google Cloud, so resource efficiency matters for resilience during traffic spikes.
The complexity of performance
Malcolm discusses the tension between presenting WordPress as performant and managing real-world plugin complexity. Brochure or marketing sites are highly cacheable and run well without intervention. But e-commerce, LMS platforms, and any site with uncached, user-specific interactions are different animals. Plugins, especially page builders and some integrations (like Facebook for WooCommerce), can break caching and spike resource use. Pressable’s architecture differs from many competitors: they provision one worker per vCPU—dedicated lanes for processes—rather than overcommitting many workers to one CPU. That design changes how sites perform under real load vs. single-user speed tests.
Infrastructure innovations ahead
Malcolm highlights several hosting trends:
– WebAssembly and browser-based ephemeral WordPress instances as promising playground and developer tools.
– Improved caching and database replication technologies to reduce latency in syncing transactional data across replicas—critical for high-availability commerce during flash sales.
– Virtual clusters and multi-datacenter approaches that present geographically dispersed hardware as a single coherent platform to increase resiliency.
– Better auditing and human-readable logs coupled with compressed storage or inference techniques to avoid excessive data costs. Current logging is often not user-friendly; AI can help surface the most relevant events.
AI and Pressable’s MCP
Pressable is developing an MCP—an AI-powered control panel that exposes control-panel APIs to natural-language interfaces and AI tools. Malcolm describes use cases:
– Developers telling an AI (from their IDE or Git tooling) to spin up a sandbox site, push code, sync uploads from production, then notify when ready.
– Running cross-site checks like “list all sites needing Gravity Forms updates” and optionally triggering updates automatically.
– Automating maintenance scripts, diagnostics, and corrective actions via natural language.
Guardrails, backups, and auditability
Malcolm stresses staged rollout and human-first design. MCP features will require guardrails—confirmations, backups, and audit logs—so destructive actions can be reversed. Pressable keeps frequent backups: hourly DB backups and daily file backups, plus protections like simlinked core WordPress files to prevent accidental deletion of core. He recommends system prompts and “human in the loop” confirmations to reduce dangerous automation.
Operational and cost implications
AI-driven behavior introduces new platform pressures. Malcolm recounts an incident where an AI bot repeatedly added items to carts millions of times, creating many uncached sessions and heavy load. Bots can adapt to blocks and continue, compounding costs for bandwidth, CPU, and storage. Hosting providers face decisions on whether to absorb those costs or pass them to customers. There may also be customer segments wanting to block AI crawlers or avoid AI-driven features entirely—“luddite toggles” that limit exposure and prevent extra charges.
Customer relationships and scaling
Malcolm and the team expect AI tooling to be most valuable for agencies and organizations managing many sites, where automation greatly reduces time-to-delivery and repetitive tasks. For individual site owners, human support remains essential and desirable. Pressable intends to add AI features to help scale the company’s human support, allowing teams to serve lower-cost customers who need more handholding, while automation helps big customers move faster. The emphasis is on AI-enhanced human workflows rather than AI-first relationships.
Future content and UX shifts
As AI tools become capable of creating themes, blocks, plugins, or CSS tailored to a prompt, the way people build and manage WordPress sites will diversify. Many users may never log into the WordPress admin, instead interacting via AI assistants or other UIs. That shift complicates support and standardization but also unlocks new efficiency: building proofs-of-concept in minutes, creating custom blocks on demand, and automating routine maintenance.
Practical precautions
Malcolm recommends:
– Backups and audit logs as a baseline.
– Human confirmations for destructive or broad actions.
– Careful design of system prompts and policies for any connected AI.
– Monitoring for bot activity and cost impacts.
– Educating customers about cacheability and uncached workloads to set realistic performance expectations.
Contact and links
Pressable: pressable.com
Malcolm: peralty.com (LinkedIn is the best social contact)
Overall, the conversation underscores that managed WordPress hosting today involves more than “files and a database.” It requires careful orchestration of caching, workers, databases, and now AI. Pressable’s MCP aims to make that orchestration accessible via natural language and automation while keeping human oversight, backups, and auditability central to the design.