Malcolm Peralty joins the Jukebox Podcast to explain how Pressable approaches managed WordPress hosting, the role of technical account managers, and how AI is changing hosting workflows and operations.
Background
Malcolm has been working with WordPress for about 20 years, starting with early releases and moving from full‑time blogging into project management, agency work, and a period in the Drupal/Acquia world as a technical account manager. He returned to WordPress and now serves as a technical account manager (TAM) at Pressable.
What a Technical Account Manager Does
At Pressable, TAMs are long‑term technical strategists rather than sales reps. Their work includes:
– Advising on site architecture, plugin choices, and performance trade‑offs.
– Planning capacity and migration tiers, often looking one to two years ahead.
– Handling pre‑sales sizing and acting as escalation points for complex support issues.
– Translating technical constraints into business terms for customers who don’t want to dig into the details.
Pressable’s WP Cloud and Infrastructure Choices
Pressable runs its own WP Cloud instead of relying exclusively on public clouds. That allows more direct control over hardware and tuning for WordPress workloads. TAMs collaborate with the cloud teams to turn WordPress performance data into actionable infrastructure or configuration changes while respecting infrastructure ownership.
Performance Realities: Caching, Builders, and Worker Models
Malcolm stresses nuance in performance claims. Simple single‑user tests can be misleading; real world traffic and concurrency reveal weaknesses. Important distinctions include:
– Cacheable vs. uncached sites: Static brochure sites benefit massively from caching, while dynamic sites—ecommerce, LMS, membership—often bypass caches and need different planning.
– Plugin and builder bloat: Heavy themes, page builders (Elementor, Divi), and plugins that break caching increase resource needs and require trade‑off conversations.
– Worker model: Pressable uses a one‑worker‑per‑VCPU model to provide predictable, isolated processing lanes rather than packing many workers onto a single VCPU, which can lead to inconsistent performance under load.
– Education: A TAM’s role includes helping customers understand business impacts of technical decisions.
Key Infrastructure Challenges and Trends
Malcolm highlighted several areas where hosting must improve:
– Faster, more reliable database replication to avoid catastrophic transactional data loss during spikes or outages.
– Virtual clusters and multi‑region approaches that present multiple data centers like a single server for failover and reduced replication complexity.
– WebAssembly experiments and ephemeral WordPress instances for fast demos and sandboxes running entirely in the browser.
– Improved logging and auditing, with compressed storage and AI summarization to make investigations feasible without storing prohibitively large datasets.
Pressable MCP: An AI‑Powered Control Panel
Pressable is developing an MCP—an AI control panel that exposes hosting APIs through natural language and agents. Key ideas:
– Natural language management: Users can request sandboxes, push code, sync files, or update plugins across many sites using plain language.
– API first: The UI and AI both call the same APIs; exposing those endpoints is straightforward technically, but teaching AI to understand intent, inputs, and consequences is harder.
– Human‑in‑the‑loop: Guardrails, confirmations, and backups are built in to prevent destructive changes. Pressable maintains hourly DB backups and daily filesystem snapshots and uses protections like simlinked core files.
– Target customers: Initial focus is agencies and multi‑site managers who gain automation scale, e.g., bulk updates across hundreds or thousands of sites.
– Developer integration: MCP can be triggered from editors, CI pipelines, or developer tooling to create sandboxes, push code, and sync uploads.
– Auditability and rollback: Robust logs and restore paths are core design features so AI actions can be reviewed and reversed.
AI, Trust, and the Human Role
Malcolm’s stance is “human‑first, AI‑enhanced.” Features should be built to serve humans first, then exposed to AI. While AI can speed delivery and automate routine tasks, teams must balance automation with customer trust and personal relationships. AI may free human agents to focus on higher‑value support for customers who need it most, but it can also reduce perceived personal service.
Operational and Cost Considerations from AI
AI brings new operational patterns and costs:
– Bot traffic and scraping can create heavy, uncached loads (e.g., automated cart activity) and evolve to evade simple blocks.
– Audit, backup, and log storage required to make AI actions reversible increases storage and compute costs; hosts must decide how to price or amortize those costs.
– Maintenance and security of AI‑generated code raises questions about long‑term ownership and upkeep.
Future Interfaces and Workflows
Malcolm predicts that many users will move from the WordPress admin into AI assistants, editor integrations, or other tools that talk to hosting APIs. This will diversify how sites are built and managed, complicating support but enabling faster prototyping, sandboxing, and iterative client workflows.
Practical Protections
Pressable’s safeguards include scheduled backups, simlinked core protections, confirmation prompts for destructive actions, and using AI to generate diagnostics and scripts that humans review before execution.
Where to Learn More
Pressable: pressable.com. Malcolm Peralty: peralty.com. Episode notes available at WP Tavern.
Summary
The conversation underscored the complexity behind managed WordPress hosting: balancing caching and dynamic workloads, tuning infrastructure for predictable performance, improving replication and multi‑region resiliency, and introducing AI with careful guardrails. When applied thoughtfully, AI can accelerate workflows and automation for agencies and multi‑site managers, but it introduces operational, cost, and trust challenges that hosts must address.