# 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 features through a WP Suite workspace.

## 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, and summarise content directly inside WordPress—without sending content to external AI providers by default.

When you need more than browser-only AI, AI-Kit can optionally connect to an AWS-native backend for fallback processing, grounded chat, doc search, and knowledge-base use cases.

### 2) AWS-friendly authentication for WordPress (Gatey)
Gatey connects WordPress to **Amazon Cognito** so your WordPress login can participate in the same identity setup as your other applications—without rewriting themes or maintaining fragile custom SSO bridges. It is designed to work with classic WordPress, headless setups, and even 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 setups it can connect to a separately deployed WP Suite Flow Backend for durable submissions, templates, workflow automation, and event-driven integrations.

### 4) Static delivery 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.

### 5) 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, and clear ownership boundaries),
- **Performance** (local-first where possible, static delivery where useful, scalable backends when needed),
- **Maintainability** (shared runtime contracts and fewer bespoke integrations),
- **Ownership** (client-owned AWS infrastructure instead of a mandatory shared SaaS runtime).

## Who WP Suite is for
WP Suite is a good fit when editors, engineers, and security stakeholders all have a say, for example:
- Editorial teams working inside the Block Editor
- Product & marketing teams who need consistent messaging at scale
- Agencies delivering WordPress projects to AWS-heavy clients
- Enterprise environments with strict security requirements

## How to start
- If you want AI-assisted editing and SEO support inside WordPress, start with **AI-Kit**.
- If you need SSO / modern identity aligned with AWS and 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 your use case requires backend services, deploy the optional AWS-native backend where applicable and connect it through the relevant WP Suite product.

---

*This page provides a general overview of WP Suite. For product-specific details, see the Gatey, AI-Kit, Flow, and Static Publisher documentation sections.*