Malcolm Peralty, a Canadian based near Toronto, has spent roughly 20 years in the WordPress space, starting with early versions of WordPress as a full-time blogger and moving through project management, agency work, and a stint in the Drupal/Acquia world before joining Pressable as a technical account manager (TAM).
Role and focus
– As a TAM at Pressable, Malcolm’s role centers on long-term strategy rather than sales or first-line support. He advises customers on site architecture, performance, plugin choices, anticipated end-of-life issues, and how sites should evolve over months and years.
– TAMs help determine appropriate service tiers, advise on optimizations, and sometimes recommend downsizing plans after improvements. They act as a bridge between customers and Pressable’s WP Cloud infrastructure teams.
Pressable’s platform and approach
– Pressable runs its own WP Cloud rather than using AWS or Google Cloud. That gives the company control over hardware and how server resources are provisioned.
– The platform is designed for a range of sites: from simple brochure/marketing sites that are highly cacheable and require minimal hands-on management, to complex sites (WooCommerce, LMS, heavy customizations) that are mostly uncached and require consultative support.
– Pressable places emphasis on resiliency and real-world performance under load, not only single-user speed tests. Some competitors can appear faster in single tests but may fail under concurrent, heavy traffic.
Performance and optimization challenges
– A key challenge is educating customers about trade-offs: plugins, page builders, and third-party integrations (e.g., Facebook for WooCommerce) often break cacheability or create heavy server load.
– Pressable optimizes with both server-side choices and by advising customers on architecture and plugin selection. For example, Pressable’s worker model assigns one worker per VCPU (dedicated lanes) rather than the common 40:1 worker-to-VCPU model, improving predictable performance under concurrency.
– Many sites are cacheable and will work perfectly without intervention. Issues arise when dynamic, user-specific pages (shopping carts, learning progress) make caching ineffective and require more CPU/worker resources.
Infrastructure trends and needs
– Malcolm highlighted several areas of ongoing and future investment:
– Better database replication and real-time streaming to reduce latency and the potential for lost transactions during failover—critical for ticket drops and big product sales.
– Virtual clusters and data center approaches that make multi-location deployments appear local, improving resiliency and failover.
– Improved auditing, logging, and human-readable forensic tools to trace actions on sites (who changed what, when) without relying solely on backups.
AI and the MCP (Managed Control Panel)
– Pressable is developing an MCP—an AI-powered control layer that exposes control panel actions via natural language. The long-term goal is that anything click-able in the control panel could be performed by AI on a user’s behalf.
– Examples shared:
– Developers could ask the AI to spin up a sandbox/staging site, push code, sync files and databases from production, and notify when ready.
– An admin could ask for a list of sites needing a specific plugin update and have the MCP update those plugins across multiple sites.
– Access to these capabilities will be via APIs/endpoints—the control panel is API-driven—so connecting AI tools to actions is technically straightforward. The harder parts are defining semantics, expectations, inputs and outputs so AI acts correctly.
Guardrails, safety, and human-in-the-loop
– Malcolm emphasized safety: backups, simlinked core files, and design decisions limit the worst possible outcomes. For example, core WordPress files are protected by a simlink setup so they can’t be erased by a mistaken command; plugins, uploads, and database can be restored from backups.
– MCP will involve phased rollouts and human approvals. Guidance includes using system prompts that require verification before destructive actions and keeping humans in the loop, especially for high-risk tasks.
– Pressable expects early adopters to be agencies and developers who can untangle issues; the tool is most valuable at scale (managing dozens or hundreds of sites), not so much for single-site hobbyists.
Observability, audit logs, and rollback
– With AI-driven changes, comprehensive, readable audit logs become essential. Logs must record steps taken and provide clear, reversible actions. Pressable already retains hourly DB backups and daily filesystem backups; more granular backups may be needed for rapid AI-driven workflows.
– Malcolm uses AI to build diagnostic scripts that run WP-CLI and other checks; soon AI could summarize findings, propose fixes, and execute changes if permitted.
New costs and bad actors
– AI agents and crawlers introduce new resource costs. Malcolm described an incident where an AI bot repeatedly added and removed items from carts across a site, creating uncached sessions and huge load. Bots then adapted to evade blocks.
– The industry faces questions about who bears additional costs for AI-driven indexing, traffic, storage for audit logs, and more. Some customers may resist paying for these extra resources.
– Pressable will need to balance offering AI features with detecting, blocking, and mitigating abusive or resource-intensive bot traffic.
Impact on relationships and UX
– AI tooling could change how customers interact with hosts: less reliance on the hosting UI and more natural-language orchestration via developer tools, IDEs, or local AI agents.
– Malcolm believes features should be “human-first, AI-enhanced,” but recognizes competition will push rapid adoption. Agencies want faster delivery and proofs-of-concept—AI could enable building a sandboxed site during a client meeting.
– There will be a market for offerings that avoid AI entirely, but those businesses may struggle to scale in the same way.
Future technical opportunities
– WebAssembly and in-browser ephemeral WordPress environments (playgrounds) are promising for development and experimentation.
– Better caching, smarter database replication, and compressed, efficient audit logging are key technical investments.
– AI will help surface meaningful log anomalies by ranking signals and reducing the manual slog of interpreting raw logs.
How to reach Malcolm and Pressable
– Pressable: pressable.com
– Malcolm Peralty: peralty.com; he’s intermittently on LinkedIn and active in WordPress Slack communities.
Summary
Malcolm Peralty’s work at Pressable highlights the tension between making WordPress accessible and managing the complexity that real-world sites introduce. Pressable aims to provide resilient hosting for simple, cacheable sites while offering consultative support for dynamic, uncached workloads. The introduction of AI (MCP) promises convenience and scale—automating routine, multi-site tasks and accelerating development workflows—but brings new challenges around safety, auditing, cost, and bot traffic. Pressable is approaching this with phased rollouts, human-in-the-loop safety measures, robust backups, and investments in observability and infrastructure resiliency.