AI-Kit for WordPress
Private, practical AI where WordPress teams already work
Use on-device AI in supported desktop Chrome for writing, rewriting, translation, proofreading, summaries, and image metadata. Add a customer-owned AWS backend only when you need broader model access, knowledge retrieval, or a reliable fallback.
Local first
Browser AI before backend AI
Free mode processes supported tasks in the browser. Pro can use backend-only or backend-fallback modes through an endpoint you configure.
Ownership boundary
WordPress remains the editing surface. Optional backend processing runs through the API deployed and configured for your own environment.
Why AI-Kit
Use the smallest AI runtime each task needs
AI-Kit starts with practical editor and media workflows instead of forcing every request through a shared cloud service. Teams can keep simple work local, then add backend capabilities selectively.
01
Work inside Gutenberg
Generate post metadata and draft text from the AI-Kit sidebar, or proofread, rewrite, and translate selected text from the block toolbar.
02
Improve media metadata
Generate titles, captions, descriptions, and alt text from Media Library workflows, including preview and bulk review before saving changes.
03
Keep local work local
When supported on the visitor’s device, free-mode tasks run in desktop Chrome without an AI provider account or public API key.
04
Extend without moving the CMS
Add frontend AI Feature controls, a configurable chatbot, DocSearch, and backend fallback while WordPress stays the content and administration layer.
Capabilities
From editor assistance to knowledge-backed experiences
Editor generation and revision
Create text from a topic and instructions, adjust tone and length, or improve existing blocks through focused proofread, rewrite, and translation actions.
Image SEO workflows
Generate and review image metadata in list view, grid view, attachment details, attachment editing, and supported image-like Gutenberg blocks.
Frontend AI surfaces
Pro adds an AI Feature block and shortcode for summarize, write, rewrite, translate, and proofread actions on the public site, including static exports.
Chatbot and DocSearch
Configure a frontend chatbot or knowledge-base search experience, with optional categories, subcategories, tags, citations, and WordPress-managed KB sources.
Architecture
Local-first by default, customer-controlled when extended
The browser decides whether local AI is available. A configured backend can handle fallback or backend-only work, while Knowledge Base sources are prepared in WordPress and published to the selected backend.
EDITOR OR VISITOR
│
▼
AI-KIT IN THE BROWSER
├── supported task → on-device model
└── backend mode or fallback
│
▼
CONFIGURED HTTPS API
│
▼
CUSTOMER-OWNED AWS BACKEND
├── model invocation
├── knowledge retrieval
└── protected admin/frontend routes
AI-Kit does not require WordPress/PHP to proxy frontend requests. Local tasks stay on the device; backend requests go directly to the endpoint configured for the site.
Comparison
Why AI-Kit stands out
Most AI plugins are wrappers for paid SaaS APIs. AI-Kit is different.
| Feature | AI-Kit (Free) | Typical AI SaaS Plugin | ChatGPT / Manual |
|---|---|---|---|
| Architecture | Browser on-device, optional backend | Sends data to vendor cloud | Copy-paste to external tab |
| Backend ownership | Your AWS account (optional) | Vendor SaaS | OpenAI account |
| Data privacy | 100% private (local) | Shared with vendor + OpenAI | Shared with OpenAI |
| Static site support | Yes — works after export | No | No |
| Cost model | Free, unlimited | Subscription / per-token | Free / Plus subscription |
| API keys needed? | No | Yes (complex setup) | N/A |
| Static Site Support | Yes (JS-based) | No (PHP-based) | N/A |
| Setup time | ~5 min | 15–30 min | Instant |
Evaluation questions
What teams usually need to know
Does AI-Kit require an AI provider account?
No for Free local-only mode. It uses supported on-device AI capabilities in recent desktop Chrome. Backend use is optional and depends on the endpoint and authentication mode you configure.
What happens when on-device AI is unavailable?
Free features that depend on browser AI may not be shown. Pro can use backend-only or backend-fallback modes so the same workflow can continue through your configured API.
Can it work after a static export?
Yes. The editor tools run in WordPress, while frontend AI Feature, chatbot, and DocSearch experiences run in JavaScript. Backend-enabled features call the configured endpoint from the browser.
Where does knowledge-base content live?
WordPress can manage which posts, pages, and sections become KB sources. Generated documents are then published to the backend selected for the site, typically infrastructure in the customer’s AWS account.
Start locally, extend deliberately
Add AI to WordPress without making a shared SaaS the default runtime
Install AI-Kit for the editor and media workflows first. Connect a WP Suite workspace and deploy an optional backend when the project needs frontend AI, DocSearch, chatbot, fallback processing, or protected APIs.