Freemius

elyass

FindAstra is AI product search for WooCommerce. It helps your store understand what shoppers actually mean, not just the exact words they type. Someone searching for “comfortable shoes for hiking” will find your “Trail Running Sneakers” even when the title never mentions comfort or hiking.
Ordinary keyword search only matches products that literally contain the words a shopper types. So a customer who describes things in their own way lands on a “no results” page and leaves. FindAstra closes that gap. It reads the intent behind each search, puts the most relevant products first, and offers helpful suggestions instead of dead ends.
And the free version runs completely on its own. There are no API keys to paste, no account to create, and no monthly fees. The AI runs right inside the shopper’s browser, so nothing about your catalog or your customers is sent to an outside server, and you can index your entire catalog with no product limit.
<h4>What your shoppers get</h4>
<ul>
<li>Answers, not just matches. Searches are understood by meaning, so shoppers reach the right products even when their wording differs from yours.</li>
<li>Live suggestions as they type. A search-as-you-type dropdown attaches to your existing search bar, with no theme editing.</li>
<li>A results page that makes sense. Your normal WooCommerce results page is simply re-ordered by relevance, keeping your theme’s design exactly as it is.</li>
<li>No more empty pages. When nothing is a strong match, shoppers see popular products instead of a dead end.</li>
</ul>
<h4>What you get as a store owner</h4>
<ul>
<li>Set up in minutes. Activate, click index once, and AI search is live. No keys, no account, no configuration headaches.</li>
<li>Private by default. Your products and your customers’ searches stay on your own site.</li>
<li>Fits your store. Works with classic and block themes, and includes a search block, a shortcode, and a sidebar widget. Developers also get filter hooks and a REST endpoint to build on.</li>
</ul>
<h4>How it works, in plain terms</h4>
When you click index, FindAstra reads each product and builds a small understanding of what it is. When a shopper searches, it compares their wording to that understanding and lists the closest products first. The first time it runs, the browser downloads a small AI model (about 33 MB) and reuses it from then on, so searches stay fast.
<h4>FindAstra Pro (optional)</h4>
A separate paid version is available at findastra.com for stores that want more. It adds optional server-side engines for very large catalogs (using your own OpenAI or Hugging Face key), multilingual search for WPML and Polylang, and built-in search analytics. The free version here is complete on its own, and nothing in it is locked or time limited.
<h3>External services</h3>
Which external service (if any) FindAstra contacts depends on the search engine you choose during setup. Each is described below, including what data is sent and when.
<h4>Hugging Face model hub (huggingface.co)</h4>
Used by the default Local engine. The first time the Local engine runs (when you index products in wp-admin, or when a shopper performs a search), the browser downloads a roughly 33 MB open-source AI model from the Hugging Face model hub and caches it locally for later visits. Only the model files are fetched. No store, product, shopper, or site data is ever sent. After the download, all search runs entirely in the browser.
Hugging Face terms of service: https://huggingface.co/terms-of-service . Privacy policy: https://huggingface.co/privacy
<h4>OpenAI API (api.openai.com)</h4>
Used only if you select the OpenAI engine and enter your own API key. At index time, the text of each product (its title and the fields you choose to include) is sent to OpenAI to generate an embedding; at search time, the shopper’s query text is sent. Requests are authenticated with the API key you provide and are made only while the OpenAI engine is the active provider.
OpenAI terms of use: https://openai.com/policies/terms-of-use . Privacy policy: https://openai.com/policies/privacy-policy
<h4>Hugging Face Inference API (router.huggingface.co)</h4>
Used only if you select the Hugging Face engine and enter your own access token. The same data as the OpenAI engine (product text at index time, query text at search time) is sent to the Hugging Face Inference API to generate embeddings, authenticated with the token you provide, and only while the Hugging Face engine is the active provider.
Hugging Face terms of service: https://huggingface.co/terms-of-service . Privacy policy: https://huggingface.co/privacy

FindAstra — AI Semantic Search for WooCommerce

AI product search that understands what shoppers mean, not just keywords. Runs in the browser. No API keys, no signup, no cost.

Alessandro Lioce

Creator Assistant Hub is the core infrastructure plugin of the Creator Assistant ecosystem. It connects your WordPress site to OpenAI and Qdrant to automatically generate and store vector embeddings for your content, enabling semantic search and AI-powered features.
How it works
The Hub is the shared infrastructure layer for the Creator Assistant ecosystem. When a compatible add-on is active and activates a vectorizer, the plugin generates vector embeddings via the OpenAI API and stores them in your Qdrant vector database cluster whenever a post is published or updated. This makes your content available for semantic search and retrieval by Creator Assistant add-ons. Without an active add-on, the Hub runs in standby mode — no content is sent to external services.
Key features
<ul>
<li>Automatic post vectorization — when an add-on activates a vectorizer, embeddings are generated and stored whenever a post is published or updated. Without an active add-on, no vectorization takes place.</li>
<li>Chunk-based vectorization — splits post content into word-level segments and stores each chunk as a separate Qdrant point, enabling fine-grained retrieval (activated by add-ons via filter).</li>
<li>Summary-based vectorization — generates a short AI summary of each post via OpenAI Chat Completions, then embeds and stores a single point per post for high-level semantic search (activated by add-ons via filter).</li>
<li>Background batch vectorization — an hourly cron job automatically picks up any existing posts that have not yet been vectorized, so your entire content library is indexed without manual intervention.</li>
<li>OpenAI integration — uses the <code>text-embedding-3-small</code> model (1536 dimensions) via the OpenAI Embeddings API for all vectorizers; the Summary vectorizer additionally calls the OpenAI Chat Completions API (<code>gpt-4.1-nano</code>) to generate post summaries.</li>
<li>Qdrant integration — stores and retrieves vector embeddings from your Qdrant Cloud cluster. Two collections are used: <code>post_chunk</code> for chunk-level points and <code>post_summary</code> for post-level summary points.</li>
<li>Block editor panel — shows the vectorization status of each post directly in the block editor sidebar (document settings panel).</li>
<li>Post list column — adds a “Vector Status” column to the posts and pages admin list, showing the vectorization status of each entry at a glance.</li>
<li>Settings page — configure OpenAI API key, Qdrant endpoint and API key, and cache expiration from a dedicated admin page.</li>
<li>API response caching — configurable cache duration to reduce API usage and latency.</li>
<li>Site Health check — reports the Hub service status in the WordPress Site Health screen.</li>
<li>Qdrant keep-alive — sends a daily lightweight ping to prevent free-tier Qdrant Cloud clusters from being suspended.</li>
<li>WPML compatible — detects the post language via WPML hooks (when WPML is active) and includes it in the Qdrant payload for multilingual filtering.</li>
<li>Extensible — exposes actions and filters so add-ons can register additional post types, override vectorizer behaviour, customise Qdrant payloads, and add settings tabs.</li>
</ul>
Requirements
<ul>
<li>An <a href="https://platform.openai.com/" rel="nofollow ugc">OpenAI</a> account with a valid API key.</li>
<li>A <a href="https://cloud.qdrant.io/" rel="nofollow ugc">Qdrant Cloud</a> account with an active cluster (free tier is supported).</li>
<li>WordPress 6.6 or higher.</li>
<li>PHP 7.4 or higher.</li>
</ul>
External services
This plugin connects to two third-party services. By using this plugin you agree to their respective terms and privacy policies.
<ul>
<li>
OpenAI — used to generate vector embeddings from your post content via the Embeddings API. When the Summary vectorizer is active (enabled by an add-on), post content is also sent to the Chat Completions API to generate a short AI summary before embedding.
<ul>
<li>Service: <a href="https://platform.openai.com/" rel="nofollow ugc">https://platform.openai.com/</a></li>
<li>Privacy Policy: <a href="https://openai.com/policies/privacy-policy" rel="nofollow ugc">https://openai.com/policies/privacy-policy</a></li>
<li>Terms of Use: <a href="https://openai.com/policies/terms-of-use" rel="nofollow ugc">https://openai.com/policies/terms-of-use</a></li>
</ul>
</li>
<li>
Qdrant Cloud — used to store and query vector embeddings.
<ul>
<li>Service: <a href="https://cloud.qdrant.io/" rel="nofollow ugc">https://cloud.qdrant.io/</a></li>
<li>Privacy Policy: <a href="https://qdrant.tech/legal/privacy-policy/" rel="nofollow ugc">https://qdrant.tech/legal/privacy-policy/</a></li>
<li>Terms of Service: <a href="https://qdrant.tech/legal/terms_and_conditions/" rel="nofollow ugc">https://qdrant.tech/legal/terms_and_conditions/</a></li>
</ul>
</li>
</ul>
Data is only transmitted to these services after you explicitly accept the Creator Assistant Terms of Service in the plugin settings and provide your own API credentials. No data is transmitted automatically upon activation.

Creator Assistant Hub

The AI infrastructure for your WordPress content. Vectorize posts with OpenAI embeddings and store them in Qdrant for semantic search.

FindAstra — AI Semantic Search for WooCommerce vs Creator Assistant Hub