AI-Kit for WordPress
Use the smallest AI runtime each WordPress task needs
Run supported editor and media tasks on-device in compatible desktop Chrome. Add a configured backend only when the workflow needs broader model access, retrieval, public frontend AI or a reliable cloud execution path.
Execution modes
Local when supported, backend when required
AI-Kit separates supported browser execution from configured backend processing instead of making one cloud route mandatory for every task.
WordPress remains the source
Editor tools, media metadata, KB source selection and frontend components stay integrated with WordPress while the selected execution path remains explicit.
Why AI-Kit
Keep AI close to the content workflow without hiding the data path
The product covers concrete WordPress tasks first, then adds backend and knowledge capabilities selectively.
01
Editor assistance
Write, rewrite, translate, proofread and summarize through focused WordPress editor workflows rather than moving content into a separate chat tab.
02
Media metadata
Generate titles, captions, descriptions and alt-text suggestions from Media Library and supported image workflows, with preview and review before saving. See the image metadata at scale guide for the dedicated cleanup workflow.
03
Supported on-device execution
Use compatible browser AI for supported free-mode tasks without requiring a provider API key for those local operations.
04
Configured backend path
Use backend-only or fallback processing when the project needs cloud models, knowledge retrieval, public AI features or a browser-independent execution path.
Capabilities
From editor tools to grounded visitor experiences
Gutenberg generation and revision
Create draft text and metadata, or apply proofread, rewrite and translation actions to selected content inside WordPress.
Image metadata at scale
Work across Media Library list and grid views, attachment screens and supported image contexts, with bulk preview and accept flows for metadata generation.
DocSearch and chatbot
Expose visitor-facing search or chat over configured knowledge sources, with category, subcategory and tag filters plus source or citation data where supported. See the grounded WordPress answers guide when retrieval and sources are part of the requirement.
Automatic Knowledge Sync and source controls
AI-Kit Pro Automatic Knowledge Sync sends selected approved public posts, pages, and eligible custom post types to a compatible knowledge backend. Use WordPress publication as approval or require a separate KB review. Keep source controls for exclusions, sections, and metadata.
Architecture
Keep local and backend processing as separate trust boundaries
The browser can perform supported local work directly. Backend-enabled operations call the HTTPS endpoint configured for the site, while WordPress remains the content and administration layer rather than proxying every request through PHP.
WordPress editor / visitor
├→ supported local AI in compatible browser
└→ configured backend mode
↓ HTTPS
AI backend
├→ model processing
├→ knowledge retrieval
└→ answer + source data
WordPress public content
→ publication approval or separate KB review
→ scheduled Automatic Knowledge Sync
→ compatible knowledge backend
→ indexing
→ DocSearch and grounded chat
Automatic Knowledge Sync is a connected Pro feature and requires a compatible AI-Kit backend. Its scheduled WordPress runner delivers eligible approved content; drafts and unpublished update proposals are not synchronized. DocSearch and grounded chatbot answers use changes after indexing completes. Manually managed knowledge documents can coexist with synchronized sources. Read the Automatic Knowledge Sync guide.
A configured backend does not mean every request is local or private. The relevant questions are which workload uses which execution path, what content crosses that boundary and who controls the configured backend and model access. See the private AI and RAG architecture for the trust zones, or compare customer-owned AWS with managed SaaS AI when backend ownership is the decision.
Fit
Compare execution and ownership, not generic AI feature counts
| Feature | AI-Kit | Managed AI integration | ChatGPT / manual workflow |
|---|---|---|---|
| Architecture | Supported tasks can run on-device in compatible desktop Chrome; an optional configured backend can handle backend-only or fallback work. | Execution follows the managed service or plugin architecture and may use a vendor-operated cloud endpoint. | Content is moved manually to a separate AI interface or workflow. |
| Backend ownership | Optional backend can be deployed in a customer-controlled AWS account. | Depends on the selected service; managed offerings commonly operate the backend for the customer. | The selected AI service account owns its own runtime; it is not part of the WordPress application architecture. |
| Data path | Supported local tasks stay on-device. Backend-enabled tasks send the required request to the endpoint configured for the site. | Data handling depends on the provider, plugin, and configured service boundary. | Users manually submit content to the selected external AI service. |
| Frontend after static export | Supported JavaScript features can continue through local browser execution or the configured backend endpoint. | Depends on whether the integration exposes a browser-reachable runtime that remains available after export. | The external AI tool remains separate from the static site. |
| Cost model | Supported local Free tasks do not incur provider API usage charges; configured backend services have their own AWS/model costs. | Varies by vendor, subscription, and usage model. | Depends on the plan of the external AI service. |
| API keys needed? | No provider API key is required for supported local Free tasks. Backend configuration depends on the selected endpoint and authentication model. | Depends on the managed integration; credentials may be abstracted by the vendor or configured by the site owner. | No WordPress API integration is required for a manual copy-paste workflow. |
| WordPress PHP dependency after export | Frontend AI can call the configured runtime directly from JavaScript; public WordPress PHP does not need to proxy each request. | Depends on the specific plugin or service architecture. | Not applicable to the site runtime. |
| Setup | Local supported tasks require the plugin and a compatible browser; backend and RAG features add endpoint and knowledge configuration. | Setup varies with provider credentials, service configuration, and plugin integration. | The AI service can be used immediately outside WordPress, but the workflow remains manual. |
Evaluation questions
Start from the AI problem
How do I use AI in WordPress without sending every draft through an AI SaaS?
Use /solutions/private-ai-for-wordpress/ for the local-versus-configured-backend decision. AI-Kit does not claim every task is local; execution depends on the selected mode and supported browser capability.
How do I give visitors grounded answers from WordPress content?
See /solutions/wordpress-rag-chatbot-aws/. AI-Kit DocSearch and chatbot can use configured knowledge sources and return source or citation data through the backend path.
Can AI-Kit help fix missing image alt text and metadata?
See /solutions/wordpress-image-alt-text-metadata-ai/. AI-Kit supports media metadata generation and review workflows, but accessibility-sensitive alt text still requires human judgment.
Can frontend AI work after static publishing?
Yes when the browser can use the supported local mode or reach the configured backend directly. WordPress PHP does not need to proxy each frontend AI request.
Choose the AI data path deliberately
Start local where supported and add a backend only for workloads that need it
Use the private-AI problem guide for execution and ownership, then use the grounded-answer guide when retrieval over WordPress content is also required.