An AI chatbot for WordPress that keeps your data close.
Project Engine puts a chatbot on your WordPress site that answers from your own content. It’s developed by MonoboxSG, it runs inside your own site, and it powers Dan, the assistant on this website.
Before you chat or write to me, please read my Privacy Policy.
The background
Most website chatbots have the same two problems. They guess when they don’t know, and they send your visitors’ conversations to a service you don’t control. Project Engine was built to answer from real records instead, from inside the website that owns them.
It grew release by release on working websites, through regular security and logging audits. Version 2.8 brings its stable foundation and its newer add-on system together in one release, after a full review of its security, privacy and logs. Each build runs through nearly 1,000 automated checks before release.
Version 2.8 is an alpha release, so it’s still being tested in real use. This website runs it, so everything you see Dan do here is the real thing.
What it does
Answers from your content
Add your pages and posts, uploaded files, pasted text or web addresses. The chatbot searches them before it replies, and links to the page it used.
Keeps up with your site
When you publish or change a page or post, its knowledge updates by itself. Drafts and private pages stay out.
Shows the right detail to the right person
Three access levels, set by WordPress login or a typed code. For example, members or staff can get answers the public can’t.
Takes on a personality
Give each chatbot its own name, instructions and look. You can run several on one site, or put a group of characters in one chat.
Fits your site
Use a corner button, a full chat on a page, or both. You choose colours, size, dark mode, starter questions and the notice under the chat.
Stays under your control
Plain-English settings, a setup guide, usage figures, chat logs you can export or clear, and spam limits on every chatbot.
Built with privacy first
Privacy isn’t a setting you have to remember. It’s how Project Engine works by default.
- Your data lives on your websiteChat logs (which include visitors’ IP addresses), conversation memory and your knowledge library are kept in your own WordPress database.
- Nothing goes to MonoboxSGThe plugin sends no usage data home. Licence keys are checked on your own server, with no outside call.
- No tracking, no outside scriptsThe chat window and admin screens load from your own site. Project Engine adds no advertising trackers or analytics.
- Hidden knowledge stays hiddenAccess is checked before the search runs, so a visitor’s chat can’t reach knowledge above their level. A forged page address gets nothing extra.
- Old data deletes itselfNew chatbots delete saved chats after 90 days and unused memory after 30. You can change this for each chatbot, and the settings warn you if chats would be kept for ever.
- Private replies stay out of cachesReplies carrying a visitor’s conversation tell page caches and content delivery networks not to keep them.
- Clean technical logsThe Debug Log holds no IP addresses and no visitor messages, so fixing a fault doesn’t expose what people said.
- Messages skip the AI“Leave a message” and “Contact us” go straight to your Telegram or email. They aren’t stored on the website or sent to any AI provider.
- Consent is built inForms can’t be sent until the visitor ticks an agreement, and the wording can change but the tick can’t be removed. Security records of form use, and any blocks you add, end after 30 days.
- Contact details stay out of the AIThe Contact Menu add-on shows your official contact buttons directly, so the AI never has to know or repeat them.
- It leaves when you doUninstalling removes the plugin’s tables and settings, so nothing is left behind.
The one exception: the AI itself
A chatbot needs an AI model to write its replies, and that’s the one step where data can leave your website. You decide how that works:
| Setup | What happens | Good for |
|---|---|---|
| Cloud AI (OpenAI, Claude or Gemini) | Each visitor message, the conversation so far and the matching knowledge go to the provider so it can write a reply. Your knowledge is also sent to an AI provider when it’s indexed for search. You use your own API key, and that provider’s terms apply. | The best answers with the least setup |
| Local AI (Ollama) | The model runs on a computer you choose, for both replies and search. Run it on your own server and nothing leaves it. | Sensitive content and strict privacy needs |
Choosing local AI: you’ll need a machine powerful enough to run a model, and smaller models are more likely to make things up. Each chatbot can have its own model, so you can test both. Whichever you choose, tell visitors how their data is handled. You remain responsible for your own privacy policy.
Add-ons
Add what you need. Each add-on is licensed per site, with one key per add-on.
| Add-on | What it adds |
|---|---|
| Delivers “Leave a message” and “Contact us” to one or several inboxes | |
| Telegram | Delivers the same messages to several chats or a group |
| Contact Menu | Official contact buttons in the chat, set by you |
| Persona Voice | Speaks as or about a person, or as a character, and sets how closely it sticks to your site |
| Page Aware | The corner chat knows which post it was opened on, so “this event” just works |
| Team Room | A room of AI team members who pick up topics, hand over to each other and give a bottom line |
How it gets set up
- Install the pluginUpload it to WordPress like any other plugin.
- Connect an AIPaste your own API key, or point it at your Ollama. A test button confirms it works.
- Add your knowledgeChoose your pages and posts, or upload your documents.
- Put it on your siteTick where the corner button shows, or add the chat to a page.
What it won’t do
It’s better to know this before you start:
- It finds, it doesn’t read everythingEach reply uses the passages that best match the question, so it can’t summarise a whole library.
- It talks, it doesn’t actIt can tell a visitor how to book, but it can’t make the booking.
- It can still be wrongAnswers are grounded in your content, but AI can make mistakes, and cheaper models do so more often.
- It suits small and mid-sized librariesBuilt-in search is comfortable up to about 2,000 knowledge pieces. Larger libraries need an optional search service.
Interested in this plugin?
Tell me about your website and what you’d like a chatbot to do. Pricing and access are handled directly for now.
Please read my Privacy Policy first. © MonoboxSG. All rights reserved.
