Recommendation systems
Recommendation engines
What is a recommendation engine?
The term is used loosely for three different things: a single model, a pipeline of models with business rules on top, and a whole platform that operates those pipelines. Most buying decisions go wrong at that distinction, because a product that is excellent as the first can be a poor answer if you needed the third.
Where NeuronSearchLab fits
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.
Concretely: NSL is a recommendation system in the ordinary sense - you send a catalogue and an event stream, you call an API, you get a ranked slate. What it adds on top of a single fixed recommender is the layer that decides which recommender is serving and proves it is the right one: several architectures trained on your own data and compared like for like, shadow and canary releases with automatic rollback, per-result explanations, and editorial rules applied at request time. The application integration does not change when the model underneath it does.
If you want one model chosen for you and never revisited, a simpler product in this category will serve you well and this page names several. If choosing, measuring and governing the model is part of the job, that is the gap NSL is built for.
The approaches, and what each is good at
“Recommendation engine” covers several families of model that behave very differently on different catalogues. These are the families you will meet.
Collaborative filtering
Content-based
Sequential
Graph
Generative
Multi-stage
The NSL Recommender Leaderboard measures 27 complete systems from these families on 10 public datasets, with quality, cost and latency reported separately. It is free and ungated, and the per-scenario boards show the winner changing between cold users, long-tail items and dense histories - which is the evidence behind the claim that no single architecture wins everywhere.
What to check before you choose one
Seven questions that separate products in this category. They are worth asking of every vendor, including us.
Which approaches it supports
Whether you can bring your own representations
What evaluation it gives you
How a model is promoted and rolled back
What editorial control exists
Whether a result can be explained
Where it runs and what it costs
Products in this category
A neutral summary of six products teams commonly evaluate, on four of the dimensions above. Each cell is sourced from the vendor’s own public documentation and links to it from that product’s page.
| Product | Recommendation API | Bring your own embeddings | Model selection | Experimentation | Pricing model |
|---|---|---|---|---|---|
| NeuronSearchLabRecommendation platform: build, evaluate, operate | Documented | Documented | Documented | Documented | Documented |
| RecombeeRecommendation-as-a-service API | Documented | Not documented | Partly | Documented | Documented |
| Amazon PersonalizeManaged recommendation service on AWS | Documented | Not documented | Partly | Out of scope | Documented |
| Algolia RecommendRecommendation add-on to a hosted search index | Documented | Not documented | Partly | Partly | Documented |
| Dynamic YieldPersonalisation and experimentation suite | Documented | Not documented | Partly | Documented | Out of scope |
| BloomreachCommerce search, merchandising and marketing suite | Documented | Not documented | Partly | Documented | Out of scope |
| NostoCommerce experience platform | Documented | Not documented | Partly | Documented | Out of scope |
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.
Building one yourself
Building a recommender is not the hard part. A competent team gets a collaborative filtering model beating a popularity baseline in a couple of weeks. The cost is everything after that: the event pipeline, the feature store, the retraining schedule, the offline evaluation harness, the online experiment framework, the rules engine merchandisers ask for within a month of launch, the on-call rota for a service that now sits in the request path of every page.
The honest test is whether the ranking itself is a source of advantage for your business. If it is - if you have signals nobody else has and the catalogue is the product - building is defensible. If the ranking is table stakes and the advantage is elsewhere, the build is a permanent tax on the team that could have been spending that time on the thing that does differentiate you.
By industry
What a recommendation engine has to be good at changes with the catalogue. Three common cases, each with its own page.
Streaming and OTT
Recommendation systems for streaming
News and publishing
Recommendation systems for news
E-commerce
Recommendation systems for ecommerce
Frequently asked questions
What is a recommendation engine?
What is the difference between a recommendation engine and a recommendation platform?
Which recommendation approach is best?
Do I need machine learning engineers to run a recommendation engine?
How is recommendation quality measured?
How much does a recommendation engine cost?
Related reading
See it on your own catalogue
Send a catalogue and an event stream and get ranked results back the same day. The free tier needs no card.