A Knowledge Cluster VM is a single GCP Compute Engine instance running five WordPress sites on a shared LAMP stack — each site with its own domain, SSL certificate, and WordPress installation, all managed from one server with Claude Code deployed for AI-assisted content operations. Five sites, one VM, unified content architecture, fraction of the cost of five separate hosting accounts.
Running five WordPress sites on five separate managed hosting accounts costs $200–$500/month and gives you five completely isolated environments with no shared infrastructure, no shared AI tooling, and no economies of scale. A dedicated GCP VM changes the math: one e2-standard-2 instance runs all five sites for around $30–$50/month, with Claude Code deployed directly on the server for zero-latency AI content operations.
We run our own 5-site knowledge cluster this way — restorationintel.com, riskcoveragehub.com, continuityhub.org, bcesg.org, and healthcarefacilityhub.org are all on one VM. The hub-and-spoke content architecture connects them intentionally: each site covers a different facet of a shared knowledge domain, and internal cross-linking amplifies authority across all five.
Who This Is For
Operators building a network of related WordPress sites — knowledge hubs, geo-local networks, topic clusters across related domains — who want shared infrastructure, lower hosting costs, and a unified AI content operation rather than five separate managed accounts.
What We Build
- GCP Compute Engine VM — e2-standard-2 (2 vCPU, 8GB RAM) or larger depending on traffic requirements, configured in us-west1 or your preferred region
- Shared LAMP stack — Apache with virtual hosts, MySQL with separate databases per site, PHP 8.x configured for WordPress
- Five WordPress installations — Each in its own directory, individual wp-config, separate database credentials
- SSL certificates — Certbot/Let’s Encrypt for all five domains with auto-renewal configured
- Claude Code deployment — Anthropic API key stored in GCP Secret Manager, Claude Code installed and configured for WP-CLI integration
- Hub-and-spoke content map — Architecture document defining which site is the hub, which are spokes, and the interlinking strategy
- WP-CLI batch scripts — Common operations (plugin updates, bulk post operations, taxonomy management) scripted for all five sites
What We Deliver
| Item | Included |
|---|---|
| GCP VM provisioning and configuration | ✅ |
| 5 WordPress installations with SSL | ✅ |
| Shared LAMP stack with Apache virtual hosts | ✅ |
| Claude Code deployment + GCP Secret Manager integration | ✅ |
| Hub-and-spoke content architecture document | ✅ |
| WP-CLI batch operation scripts | ✅ |
| Monitoring + auto-restart configuration | ✅ |
| Technical handoff documentation | ✅ |
Ready to Consolidate 5 Sites onto One Smart Server?
Share the 5 domains you want to host and your current monthly hosting cost. We’ll scope the VM build and show you the cost reduction.
Email only. No commitment to reply.
Frequently Asked Questions
What happens if the VM goes down?
GCP Compute Engine has 99.9% uptime SLA. We configure automatic restart policies and GCP’s built-in monitoring with alerting. For production sites with stricter uptime requirements, we can add a load balancer with health checks.
How is this different from WordPress Multisite?
WordPress Multisite shares a single WordPress installation across all sites — changes to plugins or core affect all sites simultaneously and customization is limited. The cluster uses five independent WordPress installations that share only the server hardware. Each site is fully independent.
Can more than 5 sites run on one VM?
Yes — an e2-standard-2 instance comfortably handles 8–10 low-to-medium traffic WordPress sites. We scale the VM size based on your traffic requirements. The architecture pattern works for 3–15 sites.
Last updated: April 2026
