ONE PLATFORM FOR EVERY RECOMMENDER
NSL sits between your product and the messy world of recommendation models. Understand your audience, test what works, see why recommendations happen and control what gets shown.
Train leading architectures on your own data, switch models or embedding providers without changing your integration, and safely promote better models when they prove themselves.
The control layer for recommendations
Train and compare different architectures, bring your own embeddings, inspect user interests and recommendation logic, then safely promote, roll back or override models without changing your application integration.
- Collaborativelive
- Content-basedlive
- Sequentiallive
- Graphlive
- Generativelive
Deployed across media, commerce, and publishing
- Streaming
- Marketplace
- Publishing
- Retail media
- Music
- Games
- Classifieds
- News
- Podcasts
- Grocery
- Fashion
- Learning
The control layer
Understand, test, explain, control
Audience map
3 communities- Long-form documentary
- Weeknight comedy
- Live sport
The control layer
NSL does not replace the recommender - it is what sits above it. Every leading architecture trained on your own data and compared on the same footing, the winner promoted only while it keeps winning, and one API in front of all of it that does not change when the model underneath does.
Ranking that works on behalf of catalogues
Can your recommender do this?
Not a different recommender - the layer above whichever one you run.
Content it can see
Scenes, dialogue, sound and objects read from the item itself, so a new one is rankable before it has a single view.
Model selection
Collaborative, content-based, sequential, graph and generative architectures trained on your behaviour and compared like for like, rather than one fixed model for every catalogue.
Safe releases
Shadow, then canary, then promotion - and automatic rollback the moment live performance drops.
Editorial control
Boost, suppress, pin or guarantee at request time, with the strength of the override set by you.
A traceable result
Every position decomposed into the interests, similarities and rules that produced it, with confidence attached and model disagreement shown.
Serving, not reporting
Built for the request path
Recommendations need to arrive while the experience is still happening. NSL is designed for low-latency serving, with behavioural signals continuously feeding back into what a user sees next.
One API can sit behind your homepage, feed, search, related content, product pages or any other recommendation surface - without your application needing to know which model, embedding provider or ranking pipeline is running underneath.
Respond in real time
Use live session behaviour to adjust ranking while the user is still browsing, watching or shopping.
One interface everywhere
The same recommendation contract across products, surfaces and model architectures.
Change the model, not your code
Rules resolve at request time and models sit behind the same call, so what surfaces can change with no retrain, redeploy or release on your side.
Adaptive relevance, in the open
Most engines guess.
NSL measures.
This sandbox is a real feed. A cursor hovers, adds to cart, and favourites items, emitting weak and strong signals that re-rank the grid as they land. Switch between two users to see the same catalogue resolve to two different front pages.
Operate the whole system in natural language
An MCP server over the same control surface the console uses. An AI operator can inspect analytics and catalogue data, or work with pipelines, rules and training runs directly - no separate, weaker API to fall back on.
Read the docsRecommender Performance Index · v3.1
Put your catalogue to work
23 systems, scored against a frozen field on the same datasets and the same budget. Every number below is reproducible, and the ones we did not measure ourselves say so.
- 01ItemKNN → Multi-task ranker68.8
- 02ItemKNN → MLP ranker66.9
- 03VS-KNN65.2
- 04EASEᴿ64.5
- 05SASRec62.9
- 06VS-KNN → GBDT60.8
- 07Recency-Weighted Popularity60.2
- 08LightGCN59.8
- 09ItemKNN58.1
- 10BERT4Rec57.2
Where itemknn landedQuality only · cost and latency are never mixed in23 systems measured
Find the next one
Eight histories.
One next item each.
Every clue is what somebody did. The answer is what they reached for next, hidden in the grid, and the history is enough to work it out: the rest of a director’s run, the writer behind the last three, the tool the previous purchases were building towards. Drag across a word to claim it, or mark its first letter and its last.
Watched
Breaking Bad · Better Call Saul (8)
Watched
Arrival · Blade Runner 2049 · Sicario (4)
Watched
Black Mirror · Devs · Mr. Robot (9)
Watched
Planet Earth · Blue Planet II · Frozen Planet (9)
Purchased
Espresso machine · Burr grinder · Milk jug (6)
Watched
The Wire · Generation Kill · Show Me a Hero (5)
Read
Dune · Neuromancer · Snow Crash (8)
Purchased
Cast-iron skillet · Carbon steel chef's knife · Dutch oven (9)
From the blog
Field notes
Running at scale across media, commerce, and publishing
Index frozen 06 September 2026 · 23 systems measured



