Overview
WP Suite Static Publisher – WordPress to AWS S3 + CloudFront
Static Publisher keeps WordPress as the editing and administration environment while moving public page delivery to static infrastructure.
A separate Node.js and Playwright publishing engine renders the real frontend, discovers the assets the browser actually uses, rewrites URLs for the target environment, deploys generated output to Amazon S3, and creates CloudFront invalidations.
Unlike a simple one-time static export, Static Publisher is designed as a repeatable WordPress-to-AWS publishing workflow.
Core capabilities
- Render-aware WordPress crawling
- Browser-discovered asset capture
- URL rewriting between development, staging, and production
- Amazon S3 deployment
- Amazon CloudFront invalidation
- Job queue, runtime state, and audit logs
- Portable queue runner for server, workstation, cron, or CI environments
- Optional incremental publishing and multiple deployment targets with WP Suite Pro
WordPress remains the editorial source. AWS becomes the public delivery layer.
Professional Services
Smart Cloud Solutions provides remote architecture, implementation, migration, and production rollout services for Static Publisher.
Services can include:
- Static WordPress architecture assessment
- Publisher exporter and Playwright runner installation
- Amazon S3 and CloudFront target configuration
- Source and production-domain URL rewrite configuration
- Asset-discovery and render troubleshooting
- Cron, queue-runner, and CI/CD integration
- Private or staging-only WordPress authoring environments
- Incremental and multi-target publishing configuration
- Integration with Gatey and Static Site Guardian for protected static routes
- Production testing, migration, and operational handover
AWS infrastructure remains customer-owned and customer-controlled.
Highlights
- Render-aware static WordPress publishing: capture the frontend users actually see, including browser-discovered assets, responsive images, scripts, styles, and page-builder output.
- AWS-native delivery path: rewrite WordPress output for the target domain, deploy to Amazon S3, serve through CloudFront, and invalidate edge caches after publishing.
- More than a one-time exporter: operate repeatable publishing jobs with queue runners, logs, automation, and optional incremental or multi-target workflows.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Pricing
Custom pricing options
How can we make this page better?
Legal
Content disclaimer
Support
Vendor support
Docs: wpsuite.io/docs Email: info@wpsuite.io 24/7 email support available for Professional plan.