Aiwend – AI Chatbot
Free WordPress plugin by ERFAN TEYMOURIKALGODARI
Visitors keep asking the same questions, and the answers are often already on your site. Aiwend adds an AI chatbot that answers from the pages, posts and text files you choose, lists the sources it u…
About Aiwend
Aiwend 0.11.0 is a free WordPress plugin by ERFAN TEYMOURIKALGODARI. It is active on 0 WordPress sites. The latest version is 0.11.0, last updated on 19 Nov 2026. You can download it free from WordPress.org — no account or payment needed.
Visitors keep asking the same questions, and the answers are often already on your site. Aiwend adds an AI chatbot that answers from the pages, posts and text files you choose, lists the sources it used, and says so when your content does not contain the answer. Bring your own key: connect your own account at OpenAI, Anthropic, Google Gemini, DeepSeek, xAI, OpenRouter or GroqCloud, and the provider bills you, not Aiwend. Aiwend has no server and no subscription, sends nothing to its author, and does not host or resell AI models. Usage limits you set, including a site limit, stop the assistant when they are reached. AI answers can still be wrong, so test before visitors see it. Developed by Erfan Teymouri.
Aiwend also includes tools for drafting content, WooCommerce product text, inquiries and read-only access for an AI app you authorise. All six modules are free and switched off after activation, so you turn on only what you need.
This is a public beta (0.11.0). Each of the seven connections (OpenAI, Anthropic, Google Gemini, DeepSeek, xAI, OpenRouter and GroqCloud) was exercised with a real provider account using sample content only; OpenRouter only partly, and not every free model works. Everything else is tested with recorded sample responses. Providers change their services without notice, so expect rough edges, try Aiwend on a staging site first, and set a spending limit at your AI provider as well as in Aiwend. The interface is available in 30 languages: English plus 29 bundled translations. The translations are AI-assisted drafts that no native speaker has reviewed (see the FAQ).
What is included
- Answer visitor questions from your own content (Chat and Knowledge). Create an assistant with its own name, instructions, look and AI model. Add knowledge from published posts and pages, or from uploaded TXT or Markdown files. The assistant answers only from sources you attach and mark Public, and each answer lists the sources it used. If the sources do not contain the answer, it says so. Show it inline with the “Aiwend Chat” block or the
[aiwend_chat bot="ID"]shortcode, or as a floating launcher. - Stay in control of cost. A site usage limit (assistants do not answer until you set one), per-conversation and per-visitor daily limits, a pause switch, and an administrator view of conversations with export and delete. Limits count “units” (an estimate of text size), not money; your provider’s invoice can differ.
- Draft posts and pages (Content Studio). Write a brief, review the proposed draft, edit it, and save it as a WordPress draft. Nothing is published for you.
- Improve WooCommerce product text (WooCommerce AI, needs WooCommerce). Pick a simple or variable product, choose which fields to send as reference and which fields to replace, and review the proposal. Price, SKU, stock, status and other fields are never changed.
- Collect inquiries (AI Forms). Add an inquiry form with
[aiwend_form id="N"]. Messages stay on your site for administrators. Nothing goes to an AI provider unless an administrator presses Analyze on one message, and Aiwend sends no emails. - Connect an AI app, read-only (MCP). An optional endpoint for AI apps that you connect with an application password. It offers nothing until you tick a tool, and it cannot change anything.
How it works with your own API key
You create an API key at OpenAI, Anthropic, Google AI Studio, DeepSeek, xAI, OpenRouter or GroqCloud, add it under Aiwend > AI Connections, and press Check access. The key is stored encrypted on your site. Answers and their cost go through your own provider account; Aiwend does not provide free AI usage.
Not available
Meaning-based (embedding) search, human handoff, order or customer assistants, automatic emails, tools that change the site through MCP, and OAuth for MCP are not part of this plugin. Aiwend works with OpenAI, Anthropic, Google Gemini, DeepSeek, xAI, OpenRouter and GroqCloud only. See the FAQ for what the AI model cannot do.
This edition does not read PDF files; add that content as a post, a page or a text file.
Deactivation and uninstall
- Deactivating stops scheduled jobs and removes the chat widget and routes; all Aiwend data stays in the database.
- Deleting the plugin keeps all data by default (tables wp_aiwend_*, options aiwend_*), so reinstalling restores everything.
- To remove everything on delete, turn on Aiwend > Settings > Privacy > “When the plugin is deleted” > permanently delete (you must type DELETE). It then removes, for that site, the tables, options, capabilities and scheduled job, and the key file when no site on the installation keeps its data (saved provider keys then become unrecoverable). It cannot be undone.
- Your posts, pages, media and users are never deleted. AI providers keep their own records.
Requirements
Minimums: PHP 8.1 with the json, sodium and mbstring extensions; WordPress 7.0 or newer (tested on 7.0.7 and 7.1.3); InnoDB. Tested with WordPress 7.0.7 and 7.1.3 and WooCommerce 11.2.1 and 10.9.4, on Linux (Apache and nginx) and Windows. Full integration tests ran on PHP 8.1 and 8.3; PHP 8.2 and 8.4 had compatibility checks; unit tests ran on PHP 8.1 to 8.5. PHP 8.5 has not had integration testing.
Database versions: Aiwend supports MySQL 8.0 or newer and MariaDB 10.11 or newer. The suites were run on MySQL 8.0.46 and 8.4.11 and MariaDB 10.11.14 and 11.4.13 (unit tests with real-database variants, the integration suite, and install and uninstall checks); other patch versions of those series are expected to work. Newer series (for example MySQL 9 or MariaDB 11.8) were not individually verified; no problem is known and Aiwend shows no warning for them. Servers older than the minimum are not supported and Aiwend then shows a notice. MySQL 8.0 reached upstream end of life in April 2026: keep it patched through your host or move to 8.4. Aiwend never blocks activation because of the database version.
Other requirements: an API key from OpenAI, Anthropic, Google AI Studio, DeepSeek, xAI, OpenRouter or GroqCloud, with billing (or the provider’s own free plan) set up at the provider.
External services
Aiwend contacts an AI provider only after an administrator connects their OWN account, and only for the actions below. Nothing is sent when settings are opened or saved, no provider is contacted by default, and Aiwend never switches to another provider on its own. Aiwend has no server and sends nothing to its author. It loads no scripts, styles, fonts or images from other servers.
- OpenAI (https://api.openai.com). “Check access” sends your API key to the model list endpoint. A chat answer sends the assistant’s instructions, the visitor’s conversation and the text excerpts of the sources used. “Send test message” sends one fixed test message. API customer terms (Services Agreement): https://openai.com/policies/services-agreement/ How API data is handled (Data controls in the OpenAI platform): https://developers.openai.com/api/docs/guides/your-data OpenAI’s general privacy policy, which covers its websites and consumer services and does not govern API customer content: https://openai.com/policies/privacy-policy/
- Anthropic (https://api.anthropic.com): the same purposes. Terms: https://www.anthropic.com/legal/commercial-terms Privacy: https://www.anthropic.com/legal/privacy
- Google Gemini API (https://generativelanguage.googleapis.com): the same purposes (Google AI Studio keys; Vertex AI is not supported). Terms: https://ai.google.dev/gemini-api/terms Privacy: https://policies.google.com/privacy
- DeepSeek (https://api.deepseek.com): the same purposes. Terms: https://cdn.deepseek.com/policies/en-US/deepseek-terms-of-use.html Privacy: https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html
- xAI (https://api.x.ai; the Grok models): the same purposes. Terms for API use (enterprise terms): https://x.ai/legal/terms-of-service-enterprise Data processing addendum: https://x.ai/legal/data-processing-addendum Privacy policy: https://x.ai/legal/privacy-policy xAI’s general privacy policy does not necessarily cover API content. xAI’s published security FAQ (https://docs.x.ai/developers/faq/security) says it keeps API requests and responses for a limited period by default and offers an optional team-level Zero Data Retention (ZDR) setting that Aiwend cannot see or change. xAI’s Enterprise Terms (version dated October 27, 2026) restrict knowingly submitting Personal Data through the API and expect reasonable efforts to prevent end users doing so, unless ZDR is used, and they incorporate the addendum. If visitors or customers may type personal data into a chat or form, read these documents and check your xAI team’s ZDR status before connecting xAI. Aiwend does not check ZDR and does not stop visitors typing personal data; for assistants that use xAI it adds the sentence “Please do not enter personal information.” to the chat notice and shows a warning on the xAI connection screens. These notices do not make a site compliant. Because of this, visitors cannot chat with an assistant that uses xAI unless the site owner allows it in wp-config.php (see the FAQ). Reasoning models bill their reasoning as output.
- OpenRouter (https://openrouter.ai): the same purposes, but OpenRouter forwards each request to the company that hosts the model you choose, so that company also receives your data. By default Aiwend asks OpenRouter to use only providers that, according to OpenRouter, do not collect user data (provider.data_collection=deny; a site developer can relax this with the
aiwend_openrouter_data_collectionfilter). This does not mean Zero Data Retention: OpenRouter and the serving provider may still process and temporarily handle a request as their own policies describe, and Aiwend does not use OpenRouter’s separate zero-data-retention option. A model with no such provider is refused, which can include free models; free models also have low request limits, and a refused or interrupted request may leave its usage unconfirmed until an administrator resolves it. OpenRouter’s model pages show each provider’s data policy. Aiwend never picks a model for you and adds no fallback; if you choose a routing model (for example openrouter/auto), OpenRouter decides which model answers and Aiwend records the model it reports. Terms: https://openrouter.ai/terms Privacy: https://openrouter.ai/privacy Logging by model providers: https://openrouter.ai/docs/guides/privacy/provider-logging - GroqCloud (https://api.groq.com; not xAI’s Grok): the same purposes. Free plans have rate limits and models are retired on published dates. Terms: https://groq.com/terms-of-use Privacy: https://groq.com/privacy-policy
- Content Studio and WooCommerce AI send your brief or the selected product fields and the instructions to your connected provider only when someone starts a generation. AI Forms sends one stored message only when an administrator presses Analyze; visitors’ submissions never reach a provider by themselves.
- MCP makes no outbound request. It lets an application that you authorise with an application password read the data described below from your site; that application and its AI service are not controlled by Aiwend.
- Your provider may charge your account for these requests and may keep its own records; providers may handle data differently on free and paid plans. Aiwend’s unit budget limits what Aiwend sends; it is not your provider’s invoice, and local deletion cannot erase a provider’s copy.
- Answers are streamed through the WordPress HTTP API (wp_remote_post). These requests are HTTPS only, verify certificates, do not follow redirects, contact only the hosts above, and obey WP_HTTP_BLOCK_EXTERNAL, WP_ACCESSIBLE_HOSTS, the WordPress proxy constants and the
pre_http_requestfilter. Theaiwend_streaming_enabledfilter (return false) switches streaming off. Stop: when a visitor presses Stop, Aiwend stops showing and processing the answer, keeps the part already received and closes the connection to the AI provider (through the WordPress http_api_curl action). Whether the provider stops generating or billing is up to the provider, so Aiwend records a stopped answer as “usage unknown” and holds its reservation as uncertain. An administrator resolves such holds on the Usage page, by entering the usage from the provider’s own records or by charging the held amount as an unconfirmed estimate; Aiwend never settles them on its own. - Code for an OpenAI embeddings request exists but is switched off and cannot run in this build; meaning-based search sends nothing.
Privacy
- Consent and visitor notice. Nothing leaves your site until an administrator connects their own provider account and turns on a module. The chat shows visitors a short notice under the message box that answers can be wrong and that messages and selected source excerpts are sent to the configured AI provider. As the site owner you decide whether that is enough for your visitors and your local law, and you should mention the provider in your own privacy policy.
- What is stored. Chat messages and sessions are kept in your database and deleted after 30 days by default (Aiwend > Settings > Privacy). Audit events record actions and outcomes, not message content (30 days by default). Usage records (request IDs and unit counts, no message content) are kept for spending control. Knowledge text and its index are kept until you delete the source; uploaded files are stored as text in the database, not in the uploads folder.
- Cookie. A visitor’s chat uses a random cookie (aiwend_chat_, HttpOnly, SameSite=Strict, up to 24 hours); only a hash of it is stored.
- Abuse limits. Aiwend uses a keyed hash of the visitor’s network address (an IPv6 address as its /64 network), never the address itself, for message and conversation limits (kept for minutes) and for the daily limit (a hash that changes every day, kept for about two days). Signed-in visitors are counted by account number. Administrators see only counts.
- Providers. When an assistant answers, the data described under “External services” leaves your site. The
store:falsesetting on OpenAI requests disables response storage but does not promise zero retention. Closing the stream does not prove that remote processing or billing stopped. If you use a page-caching plugin, clear its cache after changing an assistant’s AI connection so visitors see the current provider disclosure. - AI Forms. A submission stores the optional name, email address, topic and message, a creation and expiry time and, if analysed, the administrator’s AI result. Submissions are deleted after 30 days by default (1 to 365 days) and an administrator can delete any message at once. No IP address, user agent or user ID is stored.
- MCP. Requests are logged as tool name and outcome only, never arguments, results or credentials. Tools return the site name and language, a list of published pages or posts, and the text of one published, public, non-password-protected page or post; text you do not want an AI service to read should not be published.
- Aiwend adds text to the WordPress privacy policy guide and supports the WordPress personal data export and erasure tools (conversations of signed-in users, AI Forms by email address). Guests can delete their own conversation in the chat. These controls alone do not make a site compliant with any privacy law.
Source code
All PHP, JavaScript and CSS in this plugin is shipped as written: nothing is minified, compiled or generated, and there is no build step for it. The only bundled library, symfony/polyfill-mbstring, is installed with Composer from composer.json (composer install –no-dev) and its unmodified source is in the vendor folder.
License
Aiwend’s own code and the Aiwend symbol images (assets/brand/aiwend-symbol-64.png, -128.png, -256.png) are licensed under the GNU General Public License, version 3 or (at your option) any later version (SPDX: GPL-3.0-or-later); the full text is in the LICENSE file. Third-party components keep their own licenses and notices, listed in THIRD-PARTY-NOTICES.txt (symfony/polyfill-mbstring is MIT).
Third-party notices
See THIRD-PARTY-NOTICES.txt.
Questions about Aiwend
Is Aiwend free?
Yes. Aiwend is free to download and use from the official WordPress.org directory. There is no payment and no account needed — the download on this page goes straight to WordPress.org.
What is the latest version of Aiwend?
The latest version is 0.11.0, last updated on 19 Nov 2026.
How popular is Aiwend?
It is active on 0 WordPress sites.
How do I install Aiwend?
From your WordPress dashboard, go to Plugins → Add New, search for Aiwend, then Install and Activate. You can also download the ZIP from WordPress.org and upload it under Plugins → Add New → Upload Plugin.
Where do I download Aiwend?
Directly from WordPress.org. The Download button on this page goes straight to the official WordPress.org download, and GPLWPClub does not store the file.
Screenshots