Does every WordPress site autoscale?
No. WordPress sites use one tenant pod by default. The cluster node pool can add capacity, while multi-pod tenant scaling is configured only after Nova validates the workload.
Platform // GKE
WordPress Platform on Kubernetes
Nova runs isolated WordPress workloads on Google Kubernetes Engine with explicit resource controls, OpenLiteSpeed server-side caching, managed TLS, health checks, and automated full-site backups.
Isolated workloads
Each site runs in its own Kubernetes namespace with defined resource requests and limits.
- + Per-site isolation
- + Managed TLS certificates
- + Rate limits and security headers
Capacity and scaling
The cluster node pool can add capacity. WordPress sites use one tenant pod by default; multi-pod scaling is an operator-configured exception that must be validated for the site.
- + Cluster capacity controls
- + Per-site resource limits
- + Operator-reviewed scaling configuration
Origin performance
OpenLiteSpeed provides server-side page caching, compression, and optimized WordPress execution at the origin. Nova does not currently provide a CDN or edge network.
- + OpenLiteSpeed page cache
- + Compression
- + Optimized PHP execution
Recovery
Nova creates periodic full backups stored in Google Cloud Storage. The dashboard lists available backups and supports a full-site restore; backup objects expire after 90 days.
- + Offsite object storage
- + Backup listings
- + Full-site restore
FAQ
Does Nova include a CDN?
No. Nova currently uses OpenLiteSpeed server-side page caching, compression, and optimized WordPress execution at the origin.
How are sites backed up?
Nova creates periodic full-site backups in Google Cloud Storage, lists available backups in the dashboard, and supports full-site restore. Backup objects expire after 90 days.