No. ElasticPress is a search and facet layer backed by Elasticsearch, optimized for fast typed queries across many posts with weighted ranking and per-field boosts. SleekAI is a chatbot that reads the live WordPress content of a specific post and answers conversationally. Most documentation and large content sites benefit from running both side by side, with search for discovery and chat for follow-up on the landed article.

No. The Elasticsearch cluster sits behind ElasticPress's API surface and is rebuilt during re-indexes. SleekAI reads WordPress directly: post_content, postmeta, taxonomies, and any custom tables you map through the Wizard. That keeps the bot's answers fresh between re-indexes and avoids a second copy of every post traversing the network to the model on every chat-request.

Yes. ElasticPress exposes the standard WordPress search template, which you can customize for the no-results case. SleekAI exposes a JS API to open the chatbot with an initial message. Pass the visitor's query as that initial message and the model can either suggest a refined query or answer directly when an article on the topic exists but missed the search relevance threshold.

Yes. SleekAI is independent of where Elasticsearch is hosted. Whether ElasticPress points at the managed ElasticPress.io service, an AWS OpenSearch domain, or a self-hosted cluster, the chatbot's data path goes through WordPress directly. The only ElasticPress concern is your usual re-index cadence and which post types are marked indexable, neither of which affects the chat layer.

By default the rendered post_content, the title, excerpt, and any postmeta you map in the Wizard. For long articles you can add a vector store of up to one gigabyte per file using OpenAI Files retrieval, so the model pulls only the relevant section. Display conditions ensure the right scoping per post type, so docs get docs-context and editorial gets editorial-context.

Yours. SleekAI is bring-your-own-key, so message costs are billed directly by your provider with no SleekWP markup. Use OpenAI, Anthropic, Google, or OpenRouter, and pick a fast model for routine article follow-ups and a stronger one for complex synthesis under the same chatbot without changing the integration.

No. ElasticPress and SleekAI use independent data paths. ElasticPress queries Elasticsearch on the search request, SleekAI reads the WordPress database on the chat request. The chat widget itself is lazy and only initializes when the visitor opens it, so the initial page load and the search response time both stay unchanged from the ElasticPress-only baseline.

Yes. ElasticPress's related-posts module renders related links into the post output the bot reads. You can also map a related-query into a named variable that the system prompt formats, useful for editorial sites where the recommendation logic is driven by a custom taxonomy or relationship rather than purely by ElasticPress's content similarity calculation across the index.