AWS Marketplace · WP Suite Deployment Access
Deploy customer-owned AWS backends for WordPress without building the delivery platform yourself.
Configure supported identity, AI, workflow, protected-delivery and recovery capabilities in WP Suite, review the launch in AWS, deploy into the buyer’s own account, and turn the resulting outputs into a WordPress Pro site configuration. The customer keeps the AWS account and infrastructure; the agency keeps the solution relationship.
From project settings to WordPress
01
Configure the supported backend capabilities in WP Suite
02
Review and deploy the CloudFormation stack in AWS
03
Save the outputs and export the WordPress configuration
The delivery gap
A modern WordPress project needs more than a frontend.
A polished frontend is only one part of a production client solution. Identity, protected APIs, forms, workflows, AI-backed knowledge access and recovery all introduce infrastructure, permissions and operational work. Deployment Access turns the supported parts of that work into a repeatable delivery path while WordPress remains the CMS.
Identity and customer access
Client portals, protected content and account-aware experiences need more than a WordPress login form. Supported Gatey configurations can use an Amazon Cognito identity foundation deployed into the buyer account, while the application remains responsible for its own roles and domain rules.
AI and knowledge experiences
AI-assisted features need APIs, storage, configuration and optional knowledge resources behind the WordPress blocks. AI-Kit can connect to a supported AWS-native backend instead of pushing that responsibility into the public WordPress runtime.
Forms and workflows
A static or heavily cached frontend still needs a dependable route for submissions, validation, notifications and downstream processes. Flow separates the browser experience from the backend workflow and integration layer.
Protected delivery and recovery
Static Publisher can separate public delivery from WordPress authoring. Static Site Guardian adds supported access-control patterns, while the optional DR Backup template can create a scheduled recovery foundation for supported, deployment-tagged resources.
More than deployment templates
A complete path from project settings to WordPress configuration
The difficult part is not producing a CloudFormation file once. It is collecting valid project settings, authorizing the package, launching it in the correct account, retaining the supported outputs and making later changes reviewable.
Guided configuration
The Deployment Wizard collects the supported component choices and settings in one project context. Agencies can begin with the capability the client needs now and extend a supported deployment later instead of assembling unrelated stacks by hand.
Marketplace-authorized access
The AWS Marketplace entitlement controls access to the paid deployment packages. The public CloudFormation definitions remain reviewable, while private runtime artifacts are staged only through an authorized deployment path.
Customer-account deployment
AWS Quick Launch opens the deployment in the buyer’s AWS account. The buyer reviews the parameters, permissions and CloudFormation capabilities, then explicitly starts the stack in the selected account and Region.
Configuration handoff
When the deployment completes, supported outputs such as API URLs and identifiers return to the matching deployment session. WP Suite can then generate the corresponding WordPress Pro site configuration instead of leaving the implementer to copy stack outputs field by field.
Modular client capabilities
Start with the capability the client needs.
Deployment Access is not a requirement to install every component. The template bundle is modular, so the project can select the supported services that belong in the customer solution and keep the remaining responsibilities outside the stack.
Gatey identity foundation
Deploy a supported Amazon Cognito foundation for authentication, application clients and optional protected API access. Gatey supplies the WordPress-facing sign-in and account experience; the customer application remains authoritative for its own business permissions.
AI-Kit backend
Create the supported API, compute, storage and optional knowledge resources used by AI-Kit paid features. The result can support grounded chat, DocSearch and other configured AI-assisted experiences without treating WordPress PHP requests as the AI runtime.
Flow backend
Deploy the supported API, worker, storage, eventing and integration layer for Flow forms and workflows. This gives static and dynamic WordPress frontends a backend-connected route for submissions and business processes.
Static delivery and DR foundation
Static Site Guardian can protect selected paths in a statically delivered WordPress frontend. The current public template repository also includes optional scheduled AWS Backup resources for supported, deployment-tagged S3 buckets and DynamoDB tables, including cross-Region copy where configured.
First deployment
From AWS Marketplace to a connected WordPress site
The first launch deliberately separates configuration in WP Suite from approval and execution in AWS. That keeps the guided workflow while leaving the buyer in control of what is created in the account.
- Choose the project and scope — Subscribe through AWS Marketplace, select the WP Suite workspace and project, then choose the supported components and configuration that belong in this deployment.
- Open Quick Launch and review — The wizard opens the AWS Quick Launch flow with the prepared configuration. The buyer reviews parameters, requested IAM permissions, acknowledged CloudFormation capabilities and the target account and Region.
- Deploy in the buyer account — The buyer explicitly launches the root CloudFormation orchestration. It validates the authorized deployment, stages the supported runtime packages into the buyer-owned deployment bucket and creates the selected component topology.
- Capture supported outputs — After the stack reaches a successful state, the deployment session records the supported status and outputs needed by WP Suite. The buyer can also inspect the created resources and CloudFormation outputs directly in AWS.
- Export the WordPress configuration — WP Suite uses the returned outputs to generate the matching WordPress Pro site configuration. The configuration can then be attached to the site record and applied to the intended WordPress installation.
Buyer approval stays in AWS Deployment Access does not ask the customer to paste broad access keys, passwords or unrestricted administrator credentials into a WordPress page. Stack review and execution remain explicit actions in the buyer’s AWS account.
Update lifecycle
Update existing deployments without giving up control.
A production stack needs a supported change path as well as a first-deployment path. The update workflow prepares the requested difference, but AWS remains the place where the buyer reviews and executes it.
- Select the deployment session — Open the existing deployment in WP Suite so the wizard can work from the recorded component choices, supported outputs and current lifecycle state.
- Prepare supported changes — Reopen the deployment in the update wizard, add or reconfigure supported components and review the updated project settings before anything is sent to AWS.
- Generate an AWS change set — The workflow prepares a CloudFormation change set against the existing root stack. The change set exposes the resource-level additions, replacements and modifications that AWS plans to make.
- Review and execute explicitly — The buyer examines the change set in AWS and chooses whether to execute it. WP Suite does not silently apply later infrastructure changes to the customer account.
- Synchronize and re-export — After successful execution, the deployment session synchronizes the supported result and latest outputs. A refreshed WordPress Pro site configuration can be exported when the backend endpoints or identifiers have changed.
No hidden update channel The entitlement provides access to supported updates during the contract term; it does not replace the buyer’s responsibility to review changes, operate the account and approve production modifications.
Commercial scope
One buyer AWS account. Three years of deployment and update access.
The live AWS Marketplace offer separates the software entitlement from the infrastructure and services that the customer or agency continues to own.
USD 500 for 36 months
The public contract covers one buyer AWS account for a 36-month term. It provides the supported deployment and update path for that account rather than a per-stack or per-change usage charge.
Included access
The contract includes the guided Deployment Wizard, AWS Marketplace Quick Launch path, supported CloudFormation templates, entitlement validation, controlled package access and deployment-update guidance within the supported scope.
AWS usage is separate
The buyer pays AWS infrastructure charges directly. WordPress hosting, third-party services, custom development, unsupported AWS resources and ongoing managed operations are not included unless covered by a separate agreement.
A strong fit for delivery teams
Deployment Access fits agencies and technical teams that want WordPress to remain the CMS while selected backends run in a customer-owned AWS account. A project still needs an accountable owner for security policies, cost, integration and production operations.
Maintained delivery foundation
Start with the delivery platform. Add your expertise where the customer sees the value.
WP Suite
Deployment foundation
WP Suite maintains the supported path from guided project settings to buyer-account CloudFormation deployment, output handoff and later change-set preparation. The aim is repeatability across client projects, not a one-off infrastructure diagram.
- Version-controlled public deployment definitions and authorized runtime packages
- Guided first deployment, supported output capture and WordPress configuration export
- A reviewable update path based on AWS CloudFormation change sets
Agency or implementation partner
Customer solution and ongoing value
The delivery partner decides how the pieces become a useful client system. That includes discovery, information architecture, brand and frontend work, content, data and API integration, operational ownership and the commercial service wrapped around the platform.
- Design the client-specific experience, permissions and integration boundaries
- Connect WordPress, the customer’s application and any approved third-party services
- Package implementation, support and operations at the value of the complete solution
Ownership and product roles
Two WP Suite products support different parts of the same agency delivery model.
Deployment Access
Backends in the buyer AWS account
Deployment Access is the AWS Marketplace entitlement and deployment path. It creates supported backend resources in one buyer-owned AWS account and provides access to supported deployment changes and template updates during the term.
- The buyer owns the AWS account and the deployed infrastructure
- The buyer pays AWS charges and approves CloudFormation launches and changes
- The agency can manage the implementation without presenting deployment access as the final client product
Agency Subscription
Paid WP Suite capabilities across managed sites
The Agency Subscription covers the WordPress-side commercial relationship. It lets an agency activate supported Pro capabilities across the sites in its workspace with volume-based pricing, while each site is connected to the appropriate configuration and backend.
- Site entitlements and paid plugin capabilities are managed from the agency workspace
- Deployment Access supplies optional customer-account backends; it is not the site subscription
- Together they support a reusable platform that the agency can extend with its own services
Ready for the first client deployment?
Build the customer solution. Do not rebuild the delivery platform.
Use WP Suite Deployment Access to configure supported WordPress backends, review and deploy them in the customer’s AWS account, capture the resulting outputs and keep later changes explicit and reviewable.