The governed WordPress platform
An AI-assisted content lifecycle, from WordPress editing to published knowledge
WP Suite connects governed drafts and update proposals, human review, WordPress publishing, optional static delivery, and automatic knowledge-base sync. Use only the layers your project needs, with WordPress as the editable source of truth and optional runtime services in your own AWS account.
One platform, four visible layers
Your WordPress site
Content, plugins, review and publishing
Agent Composer + Agent Canvas
Governed AI-assisted building and editing
WPSuite.io
Workspace, Pro configuration and commercial state
Your AWS account · optional
Identity, AI, workflows and static delivery
Not a mandatory bundle: plugin-only use, connected Pro features and customer-owned AWS are different adoption levels.
Understand WP Suite in 60 seconds
WordPress stays at the center; every other layer has a specific job
WP Suite extends a WordPress site instead of replacing it. Agent Composer governs AI-assisted changes, WPSuite.io coordinates connected configuration and access, and optional backends can run in the customer’s own AWS account.
Your WordPress site
The editable source of truth
Content, plugins, Agent Composer, review, publishing and the frontend remain under normal WordPress ownership.
Browser / visitor
The experience people use
Frontend UI, plugin scripts and optional on-device AI run close to the visitor rather than through one mandatory platform runtime.
WPSuite.io · control layer
Connection, configuration and access
Site and workspace connection, supported Pro configuration, subscription state and administrative previews.
Customer-owned AWS · optional
Advanced runtime services
Selected identity, AI, workflow, API, storage and static-delivery services can run in the buyer’s AWS account.
Flexible purchase paths
Free, Pro, Agency or deployment access
Start with Free plugins, add Stripe Pro for one site, choose Agency Subscription, or buy Deployment Access and use 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
A modular system, not a feature wall
01
WordPress-native ownership
Editors keep the CMS, content model, Media Library, revisions and familiar approval workflow. A static frontend does not remove WordPress from the editorial process.
02
Governed AI editing
Agent Composer exposes approved page types, patterns, media and fields to compatible agents. New content remains a validated draft; changes to published content become separate update proposals. Editors review the result before publication or merge.
03
Focused product roles
Gatey handles identity UI, AI‑Kit adds local and optional backend AI, Flow covers forms and workflows, and Static Publisher connects approved WordPress content to static delivery.
04
Customer-owned runtime
When selected, AWS resources run under the buyer’s billing, IAM, monitoring and operational responsibility. Only the chosen component families are deployed.
Governed editing after handoff
AI can help change the site without becoming the site owner
Agent Composer is the bridge between an AI client and governed WordPress operations. It reads the active Blueprint and design context, validates allowed structures, and prepares new drafts or separate update proposals for published content. Editors can request changes on the same proposal, reject it, or merge an approved update into the original item.
What stays governed
- approved page types and pattern sequences
- theme tokens, media placement and content fields
- draft ownership, validation and audit boundaries
- human review before publication
Why this matters after launch
A client or agency can continue editing the real WordPress site instead of depending on an opaque generated frontend. The visual system and site contract remain relevant when a new page, field or component is requested later.
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
Move selected runtime responsibilities only when the project needs them
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
From an AI-assisted WordPress change to the live static frontend
The platform keeps creation, approval and delivery as visible stages. AI output is not automatically treated as final, and a static site can still keep WordPress as its editorial control plane.
01
AI-assisted create or edit
The agent creates new content or proposes an update to an existing published item.
02
Agent Composer
Blueprint, design and ownership rules constrain the draft.
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
An external exporter can run full or incremental releases, then use a verified baseline to process journaled editorial changes as targeted, resumable deployments.
05
Live static frontend
Visitors receive the newly published content after the job completes.
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
Stripe and AWS Marketplace are access paths, not different platform architectures. Deployment Access is the Marketplace product; Quick Launch is the guided deployment flow used after purchase.
Individual site
Free plugins
No subscription for included Free capabilities
Optional Stripe Pro
Connected Pro access for one WordPress site
Agency
AWS Marketplace
Agency Subscription
Multi-site Pro entitlement and central workspace management
Customer-owned backend
AWS Marketplace
Deployment Access
Account-scoped deployment entitlement
Quick Launch
Guided Marketplace deployment flow
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 AWS Marketplace product when a buyer wants supported WP Suite backend infrastructure deployed into one buyer-owned 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
Each product closes a different part of the lifecycle
Agent Composer + Agent Canvas
Governed, WordPress-native AI-assisted building and post-handoff editing, backed by a visible site and design contract.
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
Queued full and incremental releases plus journal-driven targeted content sync, S3 deployment, completed CloudFront invalidation, and public verification.
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 it for supported workspace, Pro configuration, subscription and multi-site management functions. It is not described as a mandatory data path for every plugin or frontend request.
Is Quick Launch another product?
No. Deployment Access is the AWS Marketplace product. Quick Launch is the guided Marketplace flow used after purchase to deploy the supported root CloudFormation stack.
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 the next useful layer
Start with WordPress. Add governance, Pro access or customer-owned runtime when the project calls for it.
Use the pricing guide to compare access paths, or start from a concrete WordPress, AI or AWS requirement in the solution library.