About
Built for client sites, not for a pitch deck
ChatFlint started as a tool for the WordPress sites I build for clients. Everything in it exists because a real site needed it.
Why it exists
WordPress has a strong plugin for almost everything — except a chatbot that actually knows the site it is installed on. The options were hosted widgets that charge per conversation and keep your data, or scripts that paste your content into a prompt and hope.
So this was written the other way round: retrieval first, honest about what it does not know, self-hosted, and priced as a plugin instead of a subscription.
How it is built
It is a normal WordPress plugin. No external service, no account with us, no phoning home. It uses your database, your cron, your hosting, and an AI provider you pick and pay directly.
Every release goes through an automated test battery covering the retrieval engine, both answer transports, the admin screens and the widget, because a support chatbot that breaks quietly is worse than one that is offline.
Who is behind it
A WordPress developer working with clients in the Netherlands and beyond. The plugin runs on those clients’ sites, which is why the roadmap is driven by things that actually went wrong on a live site rather than by a feature comparison table.
Questions before buying are answered by the person who wrote the code. Get in touch.
Put it on your site this week
One plugin, your own content, and seven days on our AI before you add a key. No subscription to a chat platform, no data leaving your hosting.
- Download and install. Upload it under Plugins → Add New, like any other plugin.
- Start the trial. The setup wizard asks for an email; the answers run on our AI while you decide.
- Sync your content. One click reads your pages, posts and products. From then on it answers your visitors.
Currently at version 1.59.0 · what changed
Talk to the person who built it
Pre-sales questions, licences, agency work, or a site that needs a look. One inbox, read by the developer.
- A reply within a working day — usually much sooner.
- Support by the person who wrote the code, not a queue.
- A 14-day refund on every plan, no questions that matter.