How the WP Suite platform works
WordPress at the center. Connected services in your own AWS account.
Manage content, page structure and publishing in WordPress. WP Suite components connect the visitor-facing website to authentication, AI and workflow services in your own AWS account. The site can be published statically, later changes synchronized, and selected approved content used to update an AI knowledge base.
One content source, connected services
Your WordPress site
Content, plugins, review and publishing
Agent Composer + Agent Canvas
Governed AI-assisted building and editing
WPSuite.io
Workspace, Pro configuration and subscription status
Your AWS account · optional
Identity, AI, workflows and static delivery
Choose the components the project needs. Customer-owned AWS services and static publishing can be added independently.
Understand WP Suite in 60 seconds
WordPress stays at the center; every other layer has a specific job
WordPress holds the content and page definitions. WP Suite components provide the visitor-facing features and connect to the configured services. Static Publisher and AI-Kit can synchronize approved WordPress content to the public site and the knowledge base.
Your WordPress site
The central source of content
Create and maintain pages, posts, media and structured content in WordPress. Editors review and publish changes there, whether the public site is served by WordPress or exported statically.
Browser / visitor
Components connected to your services
Gatey, AI-Kit and Flow run their visitor-facing components in the browser and communicate with their configured services. These supported features can keep working on the statically published site.
WPSuite.io · control layer
Connection, configuration and access
Site and workspace connection, supported Pro configuration, subscription state and administrative previews.
Customer-owned AWS · optional
Authentication, AI and workflows
Run the selected backend services and static delivery in your own AWS account. Your organization controls the resources, permissions, data and AWS billing.
Flexible purchase paths
Free, Professional, Agency Subscription or Deployment Access
Start with free plugins, choose Professional for one site or Agency Subscription for multiple sites. For supported backends in your own AWS account, subscribe to Deployment Access through AWS Marketplace and open the WP Suite Deployment Wizard from Quick Launch.
Platform at a glance: WordPress stays central. The surrounding nodes show who interacts with it, which control layer is optional, where customer-owned runtime can live, and how access is purchased.
Platform layers
What each part of the platform does
01
Content and editing in WordPress
Keep the content model, Media Library, revisions and review process in WordPress. The same approved content can feed the public website and the knowledge base.
02
Governed AI editing
Agent Composer defines the permitted page structures and changes for people and AI tools. Compatible AI tools create drafts and update proposals. Editors review the result before publication.
03
Components for the public website
Gatey adds sign-in and account management. AI-Kit adds AI tools, chatbots and knowledge search. Flow adds forms, discussions, ratings and connected workflows. Their configured services remain available after static publishing.
04
Backend and delivery in your AWS account
Authentication, AI, workflow processing and static delivery run on the selected AWS services. Static page traffic is handled separately from WordPress editing; managed services scale within their configured capacity and service quotas.
Governed editing after handoff
Keep page structure consistent as content changes
Agent Composer lets you define named content sections, their order and which parts can be edited. The same configured structural rules apply to supported human and AI editing. AI changes remain drafts or separate update proposals for review.
What stays governed
- named content sections and their order
- editable text, images and permitted additions
- permissions for each editor or connected AI tool
- human review before publication
Why this matters after launch
Shared page structures and each page’s own content are managed separately. Compatible structural updates can preserve the content of the named sections; larger changes follow a reviewed migration. This helps an agency change the site’s structure later without rebuilding every page.
Edit a private or firewalled WordPress site with supported MCP transport
The transport can change without changing Composer’s permissions. For a private endpoint, OpenAI Secure MCP Tunnel runs inside the network that can already reach WordPress and uses outbound HTTPS; it does not publish the private WordPress server. Where a remote MCP endpoint is already securely reachable, a compatible client can use direct authenticated MCP. In both cases, WordPress authorization and Composer’s Blueprint rules still apply.
AI / editing client
ChatGPT or compatible MCP client
Private network path
OpenAI Secure MCP Tunnel
Outbound-only transport from a host that can already reach WordPress.
Reachable endpoint path
Direct authenticated MCP
HTTPS endpoint plus a dedicated WordPress agent identity.
Client WordPress environment
Agent Composer → governed WordPress draft → human review
No administrator execution path and no automatic publication are added by the transport.
Optional customer-owned AWS
Deploy the services the site needs into your own AWS account
Deployment Access supports a guided CloudFormation path for four backend families. The resulting resources are created in the entitled buyer AWS account; AWS service charges and production operations remain the buyer’s responsibility.
Cognito identity foundation
Authentication resources for supported Gatey and protected-API integrations.
AI‑Kit Backend
Optional private AI, fallback processing, grounded chat and knowledge-access APIs.
Flow Backend
Durable submissions, templates, event-driven workflows, webhooks and supported automation.
Static Site Guardian
Protected static delivery through CloudFront and a private S3 origin for selected routes or assets.
Representative AWS services can include API Gateway, Lambda, DynamoDB, S3, CloudFront, Cognito, EventBridge and Bedrock. The exact resources depend on the selected component and configuration. See the WordPress and AWS reference architecture.
Governed content lifecycle
Update the website and knowledge base from WordPress
Editors and AI tools work on the same WordPress content. After review and publication, the configured synchronization jobs update the static website and eligible knowledge-base content.
01
Create or edit in WordPress
An editor changes the content directly within their permissions, or an AI tool prepares a draft or update proposal.
02
Apply the site’s editing rules
Agent Composer checks supported AI changes against the configured page structure, editable content and permissions.
03
Review and approve in WordPress
An editor publishes a new draft or reviews and merges an update proposal into the original item.
04
Static Publisher job
Static Publisher supports full and incremental site publishing. Once the site is delivered, scheduled content-sync tasks publish content changes against a verified baseline, updating affected pages, listings, archives and sitemaps much faster than a full site export.
05
Live static frontend
Visitors receive static pages from S3 and CloudFront. Configured Gatey, AI-Kit and Flow components continue to communicate with their services.
Available
Approved content → automatic AI‑Kit knowledge-base sync
Automatic Knowledge Sync keeps selected public WordPress content types connected to an AI‑Kit knowledge base. Choose whether WordPress publication counts as approval or a separate KB review is required. The scheduled WordPress runner sends approved changes to the backend; semantic search, DocSearch and grounded chatbot answers can use them after KB indexing completes. Drafts are not synchronized, and separate manually managed documents remain available.
Edit once in governed WordPress → approve → publish → optionally make the same approved knowledge available to search and chat. Read the Static Publisher architecture.
Pricing and deployment paths
Understand what you install, what you subscribe to and what you deploy
Professional is the subscription for one WordPress site, with payments handled by Stripe. Agency Subscription covers multiple sites. Deployment Access is a WP Suite subscription purchased through AWS Marketplace: it grants access to our published CloudFormation stack, with guided configuration in the WP Suite Deployment Wizard opened from Quick Launch.
Individual site
Use the free plugins
No subscription is needed for the included free capabilities
Professional
Subscription for one WordPress site, with payments handled by Stripe
Agency
AWS Marketplace
Agency Subscription
Multi-site Pro entitlement and central workspace management
Customer-owned backend
AWS Marketplace
Deployment Access
AWS Marketplace subscription granting access to the WP Suite CloudFormation stack
Quick Launch
Opens the WP Suite Deployment Wizard for guided configuration and deployment
Customer AWS account
Selected CloudFormation stacks and runtime services
Agency Subscription
Use this AWS Marketplace subscription for Pro-level access and central workspace management across multiple active WordPress sites.
Read the agency model · View Agency Subscription on AWS Marketplace
Deployment Access
Use this separate WP Suite subscription, purchased through AWS Marketplace, to access the supported CloudFormation stack and deploy backend infrastructure into your own AWS account.
Typical ways to use WP Suite
Start from the buyer problem, then choose the smallest useful stack
Static delivery
Make WordPress static without losing dynamic features
Move public page delivery away from PHP while keeping login, forms, discussions and AI on explicit browser or service paths. If the editing origin itself should stay private, see how to keep WordPress for editing without exposing it publicly.
AI data path
Use AI without routing every draft through an AI SaaS
Use supported local execution where it fits, then add a configured backend deliberately. When visitors need grounded answers, follow the WordPress RAG and cited-answer path.
Workflow
Replace email and spreadsheet approvals with a WordPress workflow
Keep the record, review state and downstream actions in an explicit process instead of scattering the decision across inboxes and shared sheets.
Identity
Use Amazon Cognito as the application identity layer
Keep WordPress focused on content and presentation while Cognito owns application users, authentication and tokens for browser and API experiences.
After handoff
Give clients AI without losing design control
Let a compatible agent create validated WordPress drafts inside the delivered content and design contract while human review remains the production boundary.
Product roles
Products connected through WordPress and your services
Agent Composer + Agent Canvas
Agent Canvas provides the WordPress theme and reusable layouts. Agent Composer controls supported AI changes and the configured editing rules.
Gatey
Authentication UI and supported Amazon Cognito integration for WordPress and static experiences.
AI‑Kit
Local-first editorial AI, optional backend APIs, and AI-Kit Pro Automatic Knowledge Sync of eligible approved public content for grounded chatbot and documentation search after indexing.
Flow
Forms, multi-step experiences, save and resume, discussions, ratings and optional AWS workflows.
Static Publisher
Full and incremental publishing to S3 and CloudFront, plus scheduled content-sync tasks for faster content updates on an already delivered site. The journal identifies affected content; cache invalidation and public verification complete the update.
Static Site Guardian
An optional customer-owned AWS component for protected static routes and delivery.
Common questions
Clarify the boundaries before choosing a product
Do I need AWS to use WP Suite?
No. The listed free plugin capabilities do not require a WP Suite subscription or a customer-owned AWS backend. AWS becomes relevant for selected identity, AI, workflow and protected static-delivery use cases.
What is WPSuite.io used for?
Connected sites use WPSuite.io for workspace management, supported Pro configuration and subscription access. Visitor requests can go directly to the configured AWS services.
Is Quick Launch another product?
No. Deployment Access is a WP Suite subscription purchased through AWS Marketplace that grants access to our published CloudFormation stack. Quick Launch opens the WP Suite Deployment Wizard, which guides you through configuration and deployment into your own AWS account.
Can WP Suite work with a static site?
Yes. Static Publisher keeps WordPress as the editorial control plane while an external exporter produces and deploys static output. Professional and Agency content sync can follow later WordPress changes and refresh affected pages, listings, archives, and sitemaps against a verified baseline. Gatey, AI‑Kit and Flow can add selected dynamic capabilities when their runtime is configured.
Need implementation detail? Browse the documentation, solution guides, architecture library and comparisons.
Choose your platform components
Start with your content, then connect the services your site needs.
Keep WordPress as the content source, choose the visitor-facing components, and decide which services and static delivery to run in your own AWS account.