# WP Suite: AWS-native WordPress platform WP Suite helps teams keep WordPress as the CMS, editing, and presentation layer while adding cloud-grade identity, AI, APIs, workflows, protected routes, and static delivery through modular plugins and AWS-backed infrastructure. The platform is designed for gradual adoption. Each product has useful free capabilities on its own, and the connected AWS-backed features are optional: they apply when you configure your own AWS services, deploy a backend into your own AWS account, or enable Pro/Agency features through a WP Suite workspace. ## Current commercial status WP Suite has four clear commercial paths: 1. **Free plugin capabilities** for teams that want to start without a subscription. 2. **WP Suite Pro** for one connected WordPress site, priced at $19.90/month or $199/year. 3. **WP Suite Agency Subscription**, now available on AWS Marketplace as a pay-as-you-go multi-site subscription for agencies and technical teams. Agencies choose a discounted 10, 20, 50, or 100-site commitment tier, then use hourly metered overage for additional active sites beyond the selected baseline. 4. **WP Suite Deployment Access**, available separately on AWS Marketplace as a 36-month, $500 software contract for deploying and updating supported WP Suite backend infrastructure in one buyer-owned AWS account through the Deployment Wizard, AWS Marketplace Quick Launch, and CloudFormation. Agency Subscription and Deployment Access solve different problems. Agency Subscription controls multi-site workspace and Pro product entitlements. Deployment Access controls account-scoped access to the supported infrastructure deployment and update flow. AWS service charges for deployed resources are separate from both product prices and are billed to the buyer AWS account. Lifetime access is not part of the WP Suite pricing model. Agency Marketplace listing: https://aws.amazon.com/marketplace/pp/prodview-db6r5h44kydsa Deployment Access Marketplace listing: https://aws.amazon.com/marketplace/pp/prodview-6co4ozyovp2qg The Agency tiers are pricing commitments, not product ceilings. The model is designed to work like pay-as-you-go after the selected baseline: commit to the lowest tier that covers the expected active-site count, then let extra sites be charged as AWS Marketplace metered overage. The 100-site tier is the largest public discounted tier currently shown, not the maximum number of sites an agency can manage. ## What you get on WP Suite ### 1) Local-first AI for WordPress: AI-Kit AI-Kit integrates on-device AI capabilities available in modern Chromium browsers, enabling editors to draft, rewrite, translate, summarize, and improve content directly inside WordPress without sending content to external AI providers by default. When a project needs more than browser-only AI, AI-Kit can optionally connect to an AWS-native backend for fallback processing, grounded chat, documentation search, and knowledge-base use cases. ### 2) AWS-friendly authentication for WordPress: Gatey Gatey connects WordPress to Amazon Cognito so a WordPress login can participate in the same identity setup as other applications without rewriting themes or maintaining fragile custom SSO bridges. It is designed to work with classic WordPress, headless setups, and static-site workflows. ### 3) Forms, workflows, and backend actions: Flow Flow lets teams build block-based forms in Gutenberg and post submissions directly to the endpoint they choose. In Pro or Agency setups it can connect to a separately deployed WP Suite Flow Backend for durable submissions, templates, workflow automation, webhooks, EventBridge integrations, and AI-agent steps. ### Automatic knowledge-base updates AI-Kit's Automatic Knowledge Sync is a separate delivery path from static publishing. It sends approved changes from selected WordPress content types into the Knowledge Base through a scheduled WordPress runner. Per-type policies decide whether publication is approval or a separate KB review is required; search and grounded chat use updates after indexing. Metadata merges manual policy with external and WordPress-derived vocabularies, while base-document metadata and source URL overrides remain respected. See the [Knowledge Sync guide](https://wpsuite.io/docs/ai-kit/knowledge-sync/). ### 4) Rendered static publishing for WordPress: Static Publisher Static Publisher keeps WordPress as the editorial control surface while a separate Node/Playwright exporter crawls, rewrites, deploys, and invalidates static output for S3 and CloudFront. The free workflow covers the core crawl/publish/deploy/invalidate path. Pro and Agency entitlements add advanced publishing capabilities such as incremental workflows, scheduling, additional deployment targets, and workspace-backed configuration. ### 5) Protected static delivery: Static Site Guardian Static Site Guardian is the AWS-side infrastructure pattern for protected static WordPress delivery. It is used when production pages or assets are served from S3 and CloudFront, but selected routes or resources still need access control, signed-cookie delivery, or other AWS-native protection. Static Site Guardian is infrastructure-oriented. It belongs to the Deployment Access path rather than the ordinary plugin subscription layer. ### 6) A platform mindset, not a pile of plugins WP Suite is built for teams that care about what “under the hood” means for: - **Security**: modern identity flows, protected APIs, static delivery controls, and clear ownership boundaries. - **Performance**: local-first processing where possible, static delivery where useful, and scalable AWS backends when needed. - **Maintainability**: shared runtime contracts and fewer bespoke integrations across client projects. - **Ownership**: client-owned AWS infrastructure instead of a mandatory shared SaaS runtime for sensitive backend components. - **Agency operations**: central workspace management, site entitlements, consolidated AWS Marketplace billing, discounted baseline commitments, hourly metered overage, and a path toward repeatable AWS deployments. ## Who WP Suite is for WP Suite is a good fit when editors, engineers, agencies, and security stakeholders all have a say, for example: - Editorial teams working inside the Block Editor - Product and marketing teams that need consistent messaging at scale - Agencies delivering WordPress projects to AWS-heavy clients - Enterprise environments with strict security, identity, and infrastructure ownership requirements - Teams that want WordPress as the editorial layer while selected runtime responsibilities move to AWS ## How to start - If you want AI-assisted editing and SEO support inside WordPress, start with **AI-Kit**. - If you need SSO or modern identity aligned with AWS and Amazon Cognito, start with **Gatey**. - If you need forms, submissions, templates, or workflow automation, start with **Flow**. - If WordPress should remain the editor while production runs from S3 and CloudFront, start with **Static Publisher**. - If static delivery also needs protected routes or signed-cookie access, use **Static Site Guardian** through Deployment Access. - If you manage multiple client sites, use the **WP Suite Agency Subscription** on AWS Marketplace: choose the smallest discounted baseline tier you need, then scale with hourly metered overage. The 100-site tier is not a hard limit. - If the use case requires backend services, use **Deployment Access** to deploy supported Cognito, AI-Kit Backend, Flow Backend, or Static Site Guardian infrastructure into the entitled buyer AWS account. --- This page provides a general overview of WP Suite. For commercial details, see the pricing, Agency Subscription, and Deployment Access knowledge-base pages. For product-specific implementation details, see the Gatey, AI-Kit, Flow, Static Publisher, and Static Site Guardian documentation and solution pages.