Comparison
NeuronSearchLab vs Recombee
What is the difference between NeuronSearchLab and Recombee?
Both take a catalogue and an interaction stream and return a ranked slate over an API, so for a first integration they look alike. The documented differences are concentrated in what you can do to the model behind the endpoint: recommendation approaches, bring your own embeddings, model selection, model evaluation, explainability, deployment options.
A single recommendation model gives you one fixed way of ranking. NeuronSearchLab trains and compares several architectures on your own data, keeps the winner behind one unchanging API, and gives you evaluation, experimentation, explainability and editorial control over whatever is serving.
Side by side
The Recombee column is sourced from the pages listed at the bottom of this page. The NeuronSearchLab column is written to the same standard - where something is not a published capability, it says so.
| Dimension | NeuronSearchLab | Recombee |
|---|---|---|
| Recommendation APICan an application request a ranked slate over HTTP, without embedding the vendor's own front-end widget? | Documented HTTPS API for catalogue ingestion, event ingestion and ranked recommendation requests, with client and server SDKs and an MCP server for agents. No front-end widget is required. | Documented REST API plus SDKs for several languages. Endpoints cover item and user ingestion, interaction ingestion and recommendation requests. |
| Recommendation approachesWhich families of recommender the product documents: collaborative, content-based, sequential, graph, generative, or a fixed proprietary blend. | Documented Collaborative, content-based, sequential, graph and generative architectures, plus multi-stage retrieval-then-ranking and bounded LLM or cross-encoder reranking under a latency budget. | Partly Documented as collaborative and content-based methods combined automatically per scenario. The public documentation does not expose a list of named architectures to choose between. |
| Bring your own embeddingsCan you attach vectors produced by your own models, or by a third-party provider, and have retrieval and ranking use them? | Documented Embeddings from TwelveLabs, OpenAI, an open-weights model you host or one your own team trained can be attached to items and used for retrieval and ranking. Different parts of a catalogue can carry different embeddings. | Not documented Items carry typed properties including sets and images. The public documentation does not describe attaching your own vectors for retrieval or ranking. |
| Model selectionCan you choose which model serves, and compare candidate architectures trained on your own data before choosing? | Documented Candidate architectures are trained on your behavioural data and measured against each other on the same footing; you choose which serves, and the application integration does not change when it does. | Partly Algorithm selection is described as automatic per scenario. Scenario settings, ReQL logic and boosters give you influence over the result; picking between named model architectures is not a documented control. |
| Model evaluationDoes the product report offline ranking quality - relevance, coverage, diversity, cold start - per model version? | Documented Relevance, engagement, coverage, diversity, novelty, catalogue exposure, latency and cost are reported per model and per surface. A prospective model can be replayed against historical journeys before it serves. | Partly The admin interface reports online performance for scenarios and A/B tests. Per-model-version offline ranking metrics are not a documented output. |
| ExperimentationIs online A/B testing of recommendation variants part of the product, with results attributed to the variant? | Documented Shadow mode, canary releases and conditional promotion: a candidate ships only if it beats the incumbent on agreed metrics and stays inside diversity, latency and cost guardrails, and rolls back automatically if live performance drops. | Documented A/B testing of scenarios is built into the admin interface, with traffic split between variants and results reported per variant. |
| Editorial controlsCan a non-engineer boost, suppress, exclude, pin or guarantee items on a specific surface, at request time? | Documented Boost, suppress, exclude, pin and guarantee, scoped per context (surface), applied at request time with no retrain or redeploy, and previewable for an individual user or a segment before publishing. | Documented ReQL filters and boosters, plus scenario-level configuration, express include, exclude and boost rules at request time. These are written as query expressions rather than configured in a visual control room. |
| ExplainabilityFor one returned item in one slate, can you get back why it was placed where it was? | Documented A single result decomposes into the interests, interactions, content similarities and business rules that produced it, with confidence and model disagreement reported rather than hidden. | Not documented Recommendation responses can return item properties and a recommendation ID for attribution. A per-result breakdown of why an item was placed is not described in the public documentation. |
| Real-time updatesDo new interactions affect the next request within seconds, without a retrain? | Documented Interactions fold into the user profile within seconds of arriving, so the next request already reflects the last one. Rules and context changes take effect at request time. | Documented Interactions are sent as they happen and are documented as affecting subsequent recommendations without waiting for a retrain. |
| Deployment optionsWhere the service runs, and whether a private or self-hosted option is offered. | Partly Managed cloud service with production and staging access, tenant-scoped credentials, and consent, retention and deletion policy applied through events, profiles, embeddings and trained models. Self-hosting is not a published option - talk to us about private deployment. | Partly Managed SaaS in a choice of regional clusters. Private cloud and on-premise deployment are offered commercially on enterprise terms rather than published as a self-serve option. |
| Pricing modelWhether prices are published, and what the meter is. | Documented Published tiers from free (1,000 requests per month) to £1,200 per month, metered on recommendation requests with £0.05 per request over the included allowance, plus an enterprise tier. | Documented Published tiers metered primarily on recommendation requests and catalogue size, with an enterprise tier quoted on request. |
How to read this table
- Documented - the vendor’s own public documentation describes this as a capability.
- Partly - documented, with a material limit named in the cell.
- Not documented - we could not find it in the public documentation. That is not the same as it not existing. Ask the vendor.
- Out of scope - the documentation says it is not part of the product.
Compiled from public documentation on 19 September 2026. Products change; every claim links to the page it came from, so check the source before you rely on it. Nothing here is scored, ranked or totalled.
What the two have in common
Worth stating, because a comparison page that only lists differences misrepresents how similar these products are in daily use. Both are hosted services. Both take a catalogue and an interaction stream and return ranked items over HTTP. Both support request-time filtering and rules of some kind. Both are operated without your team running training infrastructure.
If your requirement is “personalised recommendations on a few surfaces, live this quarter, without hiring a recommendations team”, both products will do it. The dimensions below are what separates them after that point.
When Recombee is the better choice
Our view, written straight. If one of these describes you, Recombee is likely the better answer and we would rather you found that out here.
- You want the vendor to choose the algorithm and never think about it again.
- You need a very short path from a product feed to a live recommendation endpoint, and model governance is not yet a requirement.
- Your editorial requirements are expressible as filters and boosts in a query language, and you are comfortable writing them.
When NeuronSearchLab is the better choice
The mirror of the section above, held to the same standard: each of these is a capability documented in the table, not a claim about outcomes.
- You want to choose the recommender rather than have it chosen: several architectures trained on your own data and compared like for like, with the winner serving behind an unchanged endpoint.
- You already produce embeddings and want retrieval and ranking to use them, rather than having a vendor re-derive its own representation of your catalogue.
- You need per-model evaluation - relevance, coverage, diversity, novelty, cold start - rather than only a revenue chart per placement.
- You need to answer “why did this person see this” for one result in one slate, to an editor, a merchandiser or a regulator.
- You want a model change treated as a production change: shadow, canary, conditional promotion and automatic rollback.
The capability detail is on the product pages, and the public evidence for the model-comparison claim is the NSL Recommender Leaderboard, which measures complete recommender systems on ten public datasets with the methodology and results published in full.
Commonly evaluated alongside
Teams comparing these two usually have a third and fourth option open.
- Amazon Personalize, for teams already on AWS
- Algolia Recommend, for teams whose catalogue is already in Algolia
- NeuronSearchLab, for teams that want to choose and evaluate the model rather than have it chosen
The whole set is on the comparisons index, and the category itself is explained on recommendation engines.
Sources
Every Recombee claim on this page comes from these pages, read on 19 September 2026. If one of them has changed, tell us and we will update the table.
Frequently asked questions
What is the difference between NeuronSearchLab and Recombee?
Is NeuronSearchLab a Recombee alternative?
When should I choose Recombee instead?
Can I migrate from Recombee to NeuronSearchLab?
How current is this comparison?
Related reading
Settle it on your own data
The table narrows it; your catalogue decides it. Run NeuronSearchLab alongside Recombee and compare the slates.