AWS-native WordPress platform
Build in WordPress. Run the platform on AWS.
WP Suite keeps WordPress as the familiar content, editing, layout, and admin layer — while authentication, static delivery, AI features, workflows, and protected runtime logic move into scalable, customer-owned AWS infrastructure.
Secure
Static-ready
Client-owned AWS
Modular by design
Runtime model
WP → AWS
WordPress
CMS, editor workflows, admin UI, media, blocks, shortcodes, and optional frontend rendering.
WP Suite
Connection layer for auth, deployment, AI, forms, workflows, and frontend integration.
AWS services
Cognito, API Gateway, Lambda, S3, CloudFront, Bedrock, WAF, EventBridge, and more.
Platform overview
WordPress stays familiar. AWS becomes the runtime.
WP Suite is not a replacement for WordPress. It changes what WordPress is responsible for. Use WordPress for content, editing, layout, media, and client workflows. Use AWS for identity, APIs, static delivery, AI backends, workflow automation, and protected application logic.
WP Suite keeps WordPress as the familiar editing and admin layer while moving authentication, publishing, AI, workflows, and backend runtime services to AWS.
Architecture at a glance
A cleaner split between content, experience, and cloud runtime.
Client browser
Public frontend, authenticated journeys, editor-facing and customer-facing experiences.
WordPress
CMS, content modeling, editorial workflows, admin UI, and optional frontend rendering.
WP Suite
The connection layer between WordPress, static frontend delivery, and protected cloud capabilities.
AWS services
API Gateway, Cognito, Lambda, S3, CloudFront, Bedrock, WAF, EventBridge, and other backend building blocks.
What the platform solves
Use the CMS your team already knows — without forcing backend complexity into WordPress.
Support classic WordPress rendering or a more static frontend approach.
Add secure AWS-backed capabilities without rebuilding the entire stack.
Keep infrastructure visible, governable, and cost-aware from the start.
What makes it different
Not a hosted abstraction. A deployment model you can own.
No shared runtime hidden behind a plugin UI.
No forced lock-in between WordPress and backend services.
AWS services are provisioned as part of a repeatable, client-specific architecture.
WP Suite helps teams keep WordPress while upgrading the runtime around it: secure access, static publishing, AI, workflows, and customer-owned AWS infrastructure.
Platform layers
Each layer has a clear role in the stack.
WP Suite is designed as a bridge: WordPress remains the content and admin layer, while AWS provides the secure, scalable backend services that would otherwise be hard to manage cleanly inside a plugin-only setup.
Experience layer
Client browser, site frontend, optional static delivery, protected user journeys, and editor-friendly experiences.
Content layer
WordPress admin, content types, editorial workflows, media, and the familiar CMS model agencies and clients already use.
Integration layer
WP Suite modules such as Gatey, Static Publisher, AI-Kit, and Flow, plus shared glue for APIs, auth, and cloud-side workflows.
AWS layer
Cognito, API Gateway, Lambda, S3, CloudFront, Bedrock, WAF, EventBridge, and deployment templates for repeatable backend provisioning.
Rollout path
Start with one need. Expand into a platform.
You do not have to rebuild everything at once. Start with an existing WordPress site, connect it to WP Suite, deploy the required AWS infrastructure, then add secure authentication, static publishing, protected sections, AI features, and workflows step by step.
A practical rollout path: start with WordPress, connect the site, deploy AWS infrastructure, add authentication, publish statically, protect routes, then extend with AI and workflows.
Product layer
Four connected building blocks.
Secure
Gatey
Connect WordPress to Amazon Cognito for login, registration, SSO, MFA, user attributes, protected sections, and API access.
Explore Gatey →AI
AI-Kit
Add local-first AI, Knowledge Base search, DocSearch, chatbot experiences, and AWS-backed AI endpoints when needed.
Explore AI-Kit →Workflow
Flow
Build forms, multi-step wizards, process maps, webhooks, email flows, S3 uploads, and event-driven automation.
Explore Flow →Publish
Static Publisher
Export WordPress output and publish it to AWS. Configure it in WordPress or run the publisher as a standalone tool.
Read the docs →Admin and frontend
Managed in WordPress. Rendered anywhere.
WP Suite capabilities are configured where WordPress teams already work: inside the SmartCloud admin experience. On the frontend, they appear through Gutenberg blocks, Elementor widgets, shortcodes, CSS variables, and JavaScript utilities. Editors keep a familiar workflow; developers get a cleaner integration layer for advanced projects.
WP Suite is managed where WordPress teams already work — inside WP Admin — and rendered through familiar frontend tools like blocks, shortcodes, Elementor widgets, CSS variables, and JavaScript utilities.
Deploy
Launch your backend in a few steps.
Select the building blocks you need, generate the deployment path, and provision the backend in the target AWS account. The goal is not to hide infrastructure, but to make a strong architecture easier to launch, inspect, and reuse.
Next step
Ready to turn WordPress into a modern application platform?
Start with authentication, static publishing, AI, or workflows — then expand into a connected AWS-native architecture over time.