Typical lead time is 2 to 4 weeks from the scoping call, depending on your catalog size, Magento edition, and infrastructure. The flow is: short scoping call → build against your exact version → install and validate on your staging environment with your real catalog → supervised production deployment. We confirm a firm timeline in writing before any work starts. This is build-to-order — there is no instant Marketplace download.

Yes. Every build includes a post-launch warranty window to fix any defects at no charge. Beyond that we offer an optional support and maintenance plan covering Magento/Adobe Commerce version-compatibility updates, embedding-provider changes, relevance tuning, and bug fixes. You own the full source code, so you are never locked to us — but most merchants keep us on for upgrades.

Yes. The module integrates through standard extension points (plugins/interceptors, observers, service contracts) that exist in both editions. It coexists with your existing Elasticsearch/OpenSearch indexing rather than replacing your infrastructure. We confirm your exact version and search engine during scoping and build to match.

Embeddings can use a hosted provider like OpenAI (you supply the API key; ongoing cost depends on catalog size and re-index frequency) or a self-hosted open model if you have data-residency requirements that keep everything inside your own infrastructure. Indexing cost is mostly one-time per product change; per-query embedding cost is small. We size and explain the expected cost during scoping.

It's built to avoid that. There are no core-file edits — integration is via di.xml, plugins, an observer on catalog_product_save_after, and a cron job. If the embedding service is ever unreachable, search gracefully falls back to Magento's native results so the storefront never goes dark. Major-version upgrades may still need a compatibility pass, which the support plan covers.