The Pure Chat alternative for WordPress AI without a sunset SaaS dependency
Pure Chat is a long-running free live-chat SaaS bundled into the Ruby ecosystem. SleekAI is a WordPress AI plugin: chatbots, an editor agent, and bulk alt-text on the user's own LLM key, with no SaaS dashboard.
♾️ Lifetime License available
Free live-chat widget versus a WordPress AI plugin
Pure Chat is a long-running free live-chat product, now part of the Ruby umbrella, with a WordPress plugin that injects its widget. The free tier covers a small number of operators and basic chat, paid functionality lives upstream in Ruby's broader receptionist and chat services. For very small teams that want a simple operator chat box, the price is hard to argue with, but the AI side of the product is light and the long-term roadmap belongs to Ruby rather than to Pure Chat itself.
SleekAI takes a completely different shape. The chatbot is configured inside WP Admin, trained on the site's own posts and pages, and served from the site's own domain on an OpenAI, Anthropic, Google, or OpenRouter key the merchant brings. There is no third-party widget script in the page's network panel, no SaaS dashboard to manage alongside WordPress, and no dependency on a parent company's product direction.
The plugin also ships agent mode for Bricks, Elementor, Gutenberg, Oxygen, Meta Box, and ACF, plus bulk alt-text for the WordPress media library, neither of which Pure Chat attempts. For sites that want the AI half without staffing a live-chat function, SleekAI replaces the bot side cleanly, while leaving teams who need a manned inbox free to pick a dedicated live-chat tool.
Workflow
How a Pure Chat widget becomes a SleekAI chatbot
Plug in your LLM key
Train on your own pages
Place the chatbot on the front end
Layer in agent mode and alt-text
Comparison
SleekAI vs Pure Chat at a glance
Differences
What changes when you move off Pure Chat
The Pure Chat way
- Pure Chat's product line sits under Ruby and depends on that roadmap
- Conversations live in Pure Chat's hosted dashboard, not in WordPress
- Widget loads from third-party domains, adding external requests
- AI replies are limited compared to dedicated AI chatbot products
- No editor-resident agent or bulk alt-text for WordPress
The SleekAI way
- Chatbots configured and served inside WordPress
- Bring your own key for OpenAI, Anthropic, Google, or OpenRouter
- Agent mode in Bricks, Elementor, Gutenberg, Oxygen, Meta Box, and ACF
- Bulk alt-text across the media library, written back to attachments
- No third-party widget script in the page's network panel
Features
Three things that actually change how you work
AI chat that ships in the core plugin
SleekAI's chatbot is part of the plugin, trained on WordPress content, and served from your own domain. There is no upstream SaaS to depend on for roadmap or pricing decisions the way Pure Chat depends on Ruby.
Agent mode in page builders
Inside Bricks, Elementor, Gutenberg, Oxygen, Meta Box, and ACF, SleekAI's agent reads the current page or field group and edits in place. Pure Chat's surface ends at chat, content production is not in scope.
Bulk alt-text where the images live
Scan the WordPress media library, generate descriptive alt text from the image itself, write it back into the attachment record. Pure Chat has no equivalent, it focuses on the live-chat widget.
Migration
Moving from Pure Chat to SleekAI
1. Export the Pure Chat history you want to keep
Pull transcripts and contact records out of the Pure Chat dashboard before disconnecting. Conversation history does not auto-migrate, so save what matters.
2. Install SleekAI with an LLM key
Add SleekAI to WordPress and paste in an OpenAI, Anthropic, Google, or OpenRouter API key. Pick a model and the chatbot has everything it needs to start training.
3. Train a SleekAI chatbot on your docs and pages
Point SleekAI at the WordPress posts and pages the Pure Chat widget used to back. SleekAI reads them directly from the database, no crawler step required.
4. Swap the widget and uninstall Pure Chat
Disable Pure Chat on the templates SleekAI will own, verify the new bot in production, then remove the Pure Chat plugin and SaaS account once everything checks out.
Audience
Where teams move from Pure Chat to SleekAI
Teams uncomfortable with a third-party widget
Pure Chat loads from a third-party domain and routes conversations through its servers. SleekAI keeps the AI chat inside WordPress and the chosen LLM provider, with no extra SaaS in the data path.
Sites wanting real AI, not just live chat
Pure Chat's AI capabilities are limited compared to dedicated AI chatbot products. SleekAI runs on modern OpenAI, Anthropic, or Google models with citations from actual WordPress content.
Sites planning beyond the free tier
Free tiers age, get features removed, or get folded into a parent company's bigger plans. A flat-license WordPress plugin running on the merchant's own LLM key is a more predictable budget item.
The bigger picture
Why owning the AI side of chat beats relying on a parent SaaS
Live-chat widgets that ride on someone else's roadmap have a known failure mode: at some point the parent company's pricing or product direction shifts, and the widget that worked for three years quietly stops being a good fit. Pure Chat under Ruby is not a bad product, but its trajectory is decided by a parent business whose primary line is virtual receptionist services, not WordPress chatbots. That is a fine place to be when the priorities line up, and an awkward place to be when they do not.
SleekAI takes the opposite stance by design. The chatbot is a WordPress plugin owned by the SleekWP suite, with its own roadmap focused on WordPress AI. The merchant brings their own LLM key, so the model decisions sit with whichever provider best fits the workload, not with a SaaS vendor's contract terms.
The same plugin layers in agent mode for the page builders and a bulk alt-text pass on the media library, so the AI investment covers more than just the chat panel. None of this argues that SleekAI is a better fit than a hired-receptionist service for teams that genuinely need a manned inbox. It argues that the AI side of chat should not be a passenger on a SaaS roadmap that has nothing to do with WordPress, and that consolidating it into a WordPress-native plugin is the more durable choice.
Questions
Common questions about switching from Pure Chat
For the AI chatbot piece, yes. SleekAI does not aim to replicate a staffed live-chat operator inbox, but for sites where the chatbot side is the real workload, it slots in cleanly and adds an editor agent and bulk alt-text on top. For teams that genuinely need a manned live-chat function, a dedicated live-chat tool is the better tool for that channel; SleekAI focuses on the AI work that surrounds it on the WordPress side.
Pure Chat is part of Ruby's broader receptionist and chat business, which means the roadmap and pricing decisions sit upstream. Free tiers under a parent company can change, get bundled, or be sunset over time. A WordPress plugin owned by the team using it is a more predictable long-term home for the chat workload, and SleekAI ships maintained as part of the SleekWP suite.
No. SleekAI is a flat WordPress plugin license. Conversation cost is paid directly to the chosen LLM provider at their published token rate, with no Sleek-side meter, quota, or upgrade tier triggered by traffic. A busy launch week is paid at API cost, not at a SaaS tier.
OpenAI, Anthropic, Google Gemini, and OpenRouter are pre-configured connectors. The merchant pastes an API key into SleekAI's settings, picks a model, and the bot uses that account directly. Switching providers later is a settings change, not a migration.
Inside the WordPress database. Messages flow from the visitor to WordPress to the configured LLM provider and back. There is no Sleek-hosted dashboard sitting in between, which also means no Sleek-side store of customer chats to migrate if the provider changes later.
Yes. Both plugins can run on the same site without colliding. Pure Chat keeps loading on the templates assigned to it, SleekAI is added to a single test route, and the swap happens template by template once the new bot is verified.
Inside Bricks, Elementor, Gutenberg, Oxygen, Meta Box, and ACF, SleekAI's agent reads the current layout or field group and takes natural-language instructions to edit it. It can scaffold new sections, rewrite copy, fill ACF fields, and call tools against WordPress post data. Pure Chat does not operate in this category.
SleekAI scans the WordPress media library, sends each image to the configured vision-capable model, and writes the returned description back to the attachment's alt-text field. It runs as a one-off backfill across existing uploads or as a scheduled task for new uploads, and editors can review the output before anything ships.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout